-
Notifications
You must be signed in to change notification settings - Fork 144
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
Mobowner almost crashes the game when mob has an invalid UUID #306
Comments
can you send any errors in your log? (enable show logs in the minecraft launcher) |
Sorry for the late response, had to fly back. It throws a ton of the "response null" messages. Then a probably interesting bit. And then a ton of response null again. About 6 a second. Log below
|
I can +1 on this one as it happened to me today. There is a test server I use for testing different mods and I had a couple donkeys I tamed on a cracked (offline) account which basically set the mob's owner to a nonexistent account. The following error was spammed into the console: A suggested fix is to recognize cracked/offline accounts and stop the request loop to prevent the game from freezing up and/or Mojang from rate-limiting you from their APIs. |
Title kinda explains it all. Somehow the game goes to literal seconds per frame upon rendering a mob with invalid UUID with "mobowner" enabled. Normal nametags work fine. Future nametags work fine.
Disabling the mobowner thing instantly fixes it.
Server: 2b2t. Coords: available upon request for debug and not for murdering doggo. Discord: Robijntj3#1294
Screenshot of doggo:
The text was updated successfully, but these errors were encountered: