-
Notifications
You must be signed in to change notification settings - Fork 100
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.17-1.21 Support #545
Comments
#518 we need this first |
currently at 1.16.3 will give $50 from https://opencollective.com/prismarinejs to anyone doing this |
increasing funding to $100 total (from prismarinejs opencollective) |
We got 1.16.5 support thanks to @Pandapip1 now! Next here is 1.17 1.18 1.19 1.20 |
Can I request that @GroobleDierne get 13% of the current bounty for this issue and that I get 7% of the current bounty for the 1.16.5 support? (I'd say that @GroobleDierne did about 65% of the work for 1.16.5 and that I did 35%) |
Sure. I'm thinking to wait for a few more versions to be supported to give the bounty for here since it seems to be moving fast. And I guess we could increase it too since this issue is pretty important |
I guess let's increase to $200 for everyone doing the work from 1.16.5 to 1.20 |
im doing at moment 1.19.2 |
This is blocked on #650 (comment) Please help fixing this first |
Remaining to do up to 1.20 (1.20.5 is going to need fixes in mcdata)
|
#650 is almost done for 1.17 |
#662 will add 1.18 and 1.18.2 support after that extremeheat#1 is in the pipeline for 1.19, 1.19.2, 1.19.3 and 1.19.4. Notably 1.19 adds chat signing functionality which isn't essential for now, but will break the tab information packet for a bit. Will come back to this later as mentioned in PR description. and for 1.20, I have it working up to 1.20.2. 1.20.3 will require some fixes to minecraft-protocol as describe in PrismarineJS/node-minecraft-protocol#1362 and also have to account for chat messages which are no longer sent as JSON but NBT format. |
We have 1.21.1 support thanks to @extremeheat now Next step here is finishing 1.21.3 support in mineflayer PrismarineJS/mineflayer#3489 |
Nothing really interesting in 21.3 btw for those wondering, there were just some fixes made to various things (that are now proper "holderSet" type / should have been this way) that need to be supported now elsewhere. Maybe the scope of PrismarineJS/minecraft-data#948 is a bit too big now but I guess it's not that bad over possibly creating merge conflicts updating many things out of sync -- a movement check block that needs to be disabled with gamemode |
Only 1.21.4 to do and then we caught up with Mojang |
This is now done @GroobleDierne and @Pandapip1 did 1.16.5 that started the process Let's grant $30 to @GroobleDierne To collect it please go over https://docs.opencollective.com/help/expenses-and-getting-paid/submitting-expenses and expense to https://opencollective.com/prismarinejs Make sure to mention the specific PRs you sent and this issue so that the expenses are accepted as valid by open collective admins. |
Add 1.18 support
The text was updated successfully, but these errors were encountered: