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
1.9 Support Checklist #128
Comments
Packet IDs will supposedly be shuffled in 1.9, so they are no longer reliable for our packet associations. This shouldn't affect plugins, unless you're using IDs, in which case you should stop doing that. Addresses #128
Thanks for all of your work on this plugin! It is a necessity for server owners and plugin developers alike. Good Luck with 1.9! |
Thanks very much for this! :D |
Thank you for the good work, hope that it will get out :) |
Thank you for your awesome, continued work on this. No spam to update, just a huge thanks for working on this! |
Thanks a lot! Appreciate your good work. |
Very much appreciated, thanks for continued support. :) Looking forward to when watchable objects are done. |
Great support to continue for 1.9! You're the king! ❤️ |
I come here a couple of times a day ... waiting for that check mark next to "Release 3.7.0-BETA" :) |
@vintagedon I plan to release tomorrow barring any setbacks. |
@dmulloy2 Awesome ... thanks so much for all your hard work; and for free, too. |
Hii, I'm using an util for SignGUIs. Since the 1.9 update and the new versions, I'm sadly getting an error. As I'm just using the util, I can't really get any information out of this error. It would be really great if you could just have a look at the error and then tell me if it's caused by protocollib or by the util? |
@Litona Looks to be an issue with the Util. |
Hello @dmulloy2 i need your protocollib for my FurniturePlugin have you update the WrappedDataWatcher currently ? |
@Ste3et The data watcher wrapper has been updated, although there are a lot of changes in 1.9. |
Hello, thanks so much for the updates! Are there any plans to update TinyProtocol? I seem to be getting some errors using it in 1.9 (with code that was functional in 1.8) |
@edasaki see the end of the list. |
ETA for 4.0.0? |
@axynos Hopefully soon, it's a large structural change. |
Just a quick reminder: While publishing 4.0.0 keep the generation of javadoc + sources in mind. |
It seems your jenkins is unavailable right now. |
Really hoping for updated packet wrappers soon, will be able to update serveral plugins. Keep youre good work 😄 |
@Vinc0682 PacketWrapper has been updated: https://github.com/dmulloy2/PacketWrapper |
@Sikatsu Should be back up, thanks! |
Can't wait for the final build to test (Stable one), the beta works well 👍 |
Yup thanks :) |
Since TinyProtocol is coming up on the list of stuff to update, I was wondering if there is any chance at looking at a fix for reloading with TinyProtocol in use? I get this error when reloading with TinyProtocol: java.lang.IllegalArgumentException: Duplicate handler name: tiny-PluginName-2 I see the close() code being called, is there a step missing that's not fully removing the original handler? Note that when I reload twice the error does not appear on the second refresh. |
@edasaki That's odd, it should remove the handler when it closes. The only thing I can think of is that it removes the handler in the channel thread, which is only an issue when reloading. Problems like these are why I don't recommend reloading. |
Ah I was being silly, it only happens when I replace the plugin jar with a newer version, so the classloader can't find the old version of the class lmao. There's no issue reloading normally, only when the jar is replaced before the reload (which I know is super bad practice but I only do it on dev server anyways so whatever :P) I guess it's not a problem. |
Almost done... 👍 |
Nice work, this is awesome to see hitting 4.0.0. :) 🎊 🎆 😄 🍰 🍬 |
ProtocolLib v4.0.0 has been released!
There are development builds available on my Jenkins server: http://ci.dmulloy2.net/job/ProtocolLib/
Here's the current progress:
Pre-release:
Post-release:
Full support:
The text was updated successfully, but these errors were encountered: