-
-
Notifications
You must be signed in to change notification settings - Fork 256
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
ERROR IN Protocol1_20_3To1_20_2 IN REMAP OF COMBAT_KILL (0x3A) #3640
Comments
This sounds like a third-party plugin or something else is sending a faulty resource pack to the server which viaversion does not like and therefore complains about it, Could you perform a binary search to see what causes it to happen? |
Sorry, on what should i perform a binary search and what should i search for? |
Start by checking if server can recover with just viaversion active, if it doesn't then check the configs next to see if a server resource pack was ever deployed. |
We don't force resourcce packs from the server and there is nothing alike in our plugins. |
Sorry, but did this error cause some kind of spam? I'm having a similar problem, but it causes absurd spam on the server (log with 147k lines in 1 hour of active server, I barely reach 10k, imagine 147K) https://dump.viaversion.com/42c7d5c34c2cd14f62c8a951026ffee334916acd35a8cf01b2886cbc797599fa |
Please try the latest build(s) from https://ci.viaversion.com/. In case the issue still persists send the new dump |
4.9.3 fixed the disconnection issue I ended up forgetting to put the log in the previous message: https://mclo.gs/CFDQY28 |
This sounds like a third-party plugin is causing viaversion to complain so much that the server has a chance to explode which is something unexpected, Please perform a binary search to see what's causing all of that mess. |
/viaversion dump
Outputhttps://dump.viaversion.com/5e172c9a4c0ed6b0c51c9bac7d4da83cccb23519eeb81c7a0e8740af66813720
Console Error
https://pastebin.com/RXT0BgZN
Bug Description
This exception randomly appeared in logs. Seems to be triggered by some 1.20.3 players.
Steps to Reproduce
Not quite sure as i couldn't reproduce it myself. But it definitely only occurs since the 1.20.3 update.
Expected Behavior
To not error?
Additional Server Info
Running behind a waterfall proxy.
Checklist
The text was updated successfully, but these errors were encountered: