-
Notifications
You must be signed in to change notification settings - Fork 380
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
ArgumentOutOfRangeException with terrain/movements #114
Comments
was /server jurassic the last command in the script file? |
Oops, forgot to respond to your issue... Seems like the issue is in the |
Initsuj it was the only command and i also tried it without a script |
Orelio yes it does but ill attempt it other ways when i get the time if you wanna test the ip is play.opticcraft.tv |
I can't reproduce with the latest version - I have terrainandmovements=true and use /server jurassic. Test with the latest version? https://ci.appveyor.com/project/ORelio/minecraft-console-client/build/artifacts |
By chance, is this a 1.7.10 server? I think I know what's causing this, and it doesn't relate to terrain here. Instead, it seems to be a result of the change in cb00c28 - since |
The first bug is that the list isn't cleared in some cases, meaning new packets get data from the previous packet if it isn't read fully. Most commonly, this happens with a plugin channel message. The second bug happens because lists don't throw IndexOutOfRangeExceptions, but instead throw ArgumentOutOfRangeExceptions. This caused the catch for ignoring message types to not occur, instead causing the client to crash. This only happens in 1.7.10, where the message type is not included. Most likely, these changes will fix the bugs seen in MCCTeam#114 and MCCTeam#117, although they may be caused by other bugs.
1.7 n 1.8 |
Sorry i havent had the time to investigate buzy with school |
Please retry with the latest development build :) |
It has been fixed :) |
Great! :) |
When i ran console client with terrain movements on this happend...
https://gyazo.com/39cc4aff1594fec21663f478bcb88c3d
The text was updated successfully, but these errors were encountered: