-
Notifications
You must be signed in to change notification settings - Fork 47
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
Update to 1.9? #222
Comments
We plan on supporting 1.9, but right now nobody is actively working on it. Some things that need work:
IRC log for reference:
|
interesting, It seems that you are very close to getting the first bot 1.9, The problem is the chunks. |
I have to do another release for 1.8 to fix a bug and then I will start merging in 1.9 changes tonight. |
@gamingrobot Fantastic notice! |
I have updated mcp inside spockbot to support 1.9 but its on a test branch due to being in a broken state. You can see the first pass of the update 4ba34bb. The bot joins the server then crashes due to failing to decode Chunk Data correctly. I think this is due to the new biome data that's included. |
Cool stuff. I'll take a look at that chunk issue this evening. |
|
For what is this error?
|
@gamingrobot updated the protocol but all the plugins built on top of the protocol haven't been updated yet. So plugins that have to deal with the protocol directly (such as the Interact plugin, in this case), make incorrect assumption about the protocol structure, try to encode improper packets, and then the framework crashes. |
this takes time without moving |
how's it going? |
Entity metadata needs to be updated still but chunk decoding is "working" (meaning decoding but not tested) |
Entity metadata is done now. Now to to fix various crashes and double check the chunk decoding it working as intended. |
How goes all the guys project? |
All that is left is inventory, and some testing. @Gjum wrote the inventory so he would be the best person to update it, but if I find a free weekend I might try and dig though it. |
sound good 👍 |
No description provided.
The text was updated successfully, but these errors were encountered: