Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnecting without Errors #3599

Open
1 task
Singhom931 opened this issue Mar 3, 2025 · 0 comments
Open
1 task

Disconnecting without Errors #3599

Singhom931 opened this issue Mar 3, 2025 · 0 comments
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f

Comments

@Singhom931
Copy link

  • The FAQ doesn't contain a resolution to my issue

Versions

  • mineflayer: 4.26.0
  • server: fabric latest, but no client mods needed( fabric 0.16.10, MC 1.21.4)
  • node: 22.14.0

Detailed description of a problem

Instantly Disconnected without errors and doesn't terminate either

Server Console:
[16:56:41] [Server thread/INFO]: com.mojang.authlib.GameProfile@2e0b0336[id=a87a5369-7811-312d-919b-33633269dcf8,name=DiabloBot,properties={}] lost connection: Disconnected
[17:19:20] [Server thread/INFO]: com.mojang.authlib.GameProfile@427bc062[id=a87a5369-7811-312d-919b-33633269dcf8,name=DiabloBot,properties={}] lost connection: Disconnected

Code:

What did you try yet?

Did you try any method from the API?
Did you try any example? Any error from those?

Your current code


const bot = mineflayer.createBot({
  host: 'myplayitggserverip', 
  username: 'DiabloBot', 
  auth: 'offline', 
  hideErrors: false,
})

bot.on('chat', (username, message) => {
  if (username === bot.username) return
  bot.chat(message)
})

bot.on('error', (er) => {console.log(er)})

// Log errors and kick reasons:
bot.on('kicked', console.log)
bot.on('error', console.log)

Expected behavior

Bot Should be Running or atleast Giving a Error About Disconnection but the Debug Console is Blank

Additional context

I am using Playit.gg tunnel for my server however i did test with other public servers and the issue was still there so that shouldnt be the problem

@Singhom931 Singhom931 added possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f
Projects
None yet
Development

No branches or pull requests

1 participant