-
Notifications
You must be signed in to change notification settings - Fork 129
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.20.6 update checklist #755
Comments
Goodluck on the packetevents switch! |
Small update for anyone who doesn't pay attention to the discord. |
Oh and the 1.21 new mobs, which I forgot to add and forgot to mention here. It has a basic level of support, so hopefully it's just a case of adding the accessors to the flagwatchers |
@libraryaddict I seem to be getting an unstable issue with tests while compiling the latest: Any idea what could be going on here, it is not an issue on md-5's jenkins however. Am confused... |
Best guess atm on mobile, is outdated code or dependencies |
Hm, I'm compiling master for LibsDisguises, and 2.0 for PacketEvents. |
Alright, fixed. Glad it's an issue I had seen before or this would've stumped me. |
Confirmed fixed, thanks! |
Added a few TODO's and removed older TODO's that were cluttering & obsolete. |
The other feature that we will be waiting for is retrooper/packetevents#866 |
WIP list of things to do before release
Optional
|
The reason behind this update taking so long is that ProtocolLib hasn't been working as well as it had in the past (Not just for this update), and although it is an option to create PRs and whatnot, I've decided to instead switch to PacketEvents as per #752.
You can check that issue to read some discussion that has happened there.
This is a checklist of tasks needing doing before this is complete.
This checklist does not promise a timeline of when things will be complete, as some tasks in this may be missing.
I would expect perhaps, 15th of June?
The earliest builds are probably going to be ones you have to go out of the way for, I have little intention to roll out this update until I'm sastified with it. It promises to break plugins and if there's a bad enough bug, it'd break servers for no reason. After all, this is a massive switch to PacketEvents, and requires internals rewritten.
https://github.com/retrooper/packetevents
Issues
Painting now wants a direction set when it's spawned in, need to check how it worked in earlier versions and handle appropiately. Either by automatically rotating (respawning), or by making it a rotation in the FlagWatcher. Probs the formerRotating would involve a lot of respawning the painting/frame, not really worth itFix entity look/body rotation being sent incorrectly, spawning in with the wrong direction for exampleMay not be an issue anymoreThe text was updated successfully, but these errors were encountered: