-
-
Notifications
You must be signed in to change notification settings - Fork 238
Make pc protocol entity metadata consistent across all versions #985
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
base: master
Are you sure you want to change the base?
Make pc protocol entity metadata consistent across all versions #985
Conversation
|
Thanks, have you checked to make sure this is correct on all versions? |
|
Everything looks correct, and tests are passing on nmp and mineflayer. |
|
I checked again and tests are actually not passing, will fix. |
8fbf47f to
76a0dd4
Compare
76a0dd4 to
fbc6e60
Compare
|
Is this ready? |
|
Almost. 1.7/1.8 is failing and I haven't been able to fix it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.8 is failing because entityMetadata type is wrong (missing bitfield). There could be more errors, all the versions need to be reviewed
|
Same error even with the bitfield. Is there something else I'm missing? |
|
Please open a PR on nmp so we see the error
…On Thu, Feb 27, 2025, 10:38 SuperGamerTron ***@***.***> wrote:
Same error even with the bitfield. Is there something else I'm missing?
—
Reply to this email directly, view it on GitHub
<#985 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR437XTSFYG3VJYGIUZNDL2R3MIBAVCNFSM6AAAAABXNWFYIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBXGQYDEMJVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: SuperGamerTron]*SuperGamerTron* left a comment
(PrismarineJS/minecraft-data#985)
<#985 (comment)>
Same error even with the bitfield. Is there something else I'm missing?
—
Reply to this email directly, view it on GitHub
<#985 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR437XTSFYG3VJYGIUZNDL2R3MIBAVCNFSM6AAAAABXNWFYIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBXGQYDEMJVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hey what's blocking here ? |
|
The issue seems to be that in 1.7/1.8 the type is unable to be read by the mapper due to already being read by the bitfield. |
|
Ok what about reverting the changes for these versions so at least we move
forward for every other versions?
…On Sun, Mar 16, 2025, 15:30 SuperGamerTron ***@***.***> wrote:
The issue seems to be that in 1.7/1.8 the type is unable to be read by the
mapper due to already being read by the bitfield.
—
Reply to this email directly, view it on GitHub
<#985 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR437QOKXX7R7XQFWFD2ZT2UWDHVAVCNFSM6AAAAABXNWFYIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXGQ3TCNBXGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: SuperGamerTron]*SuperGamerTron* left a comment
(PrismarineJS/minecraft-data#985)
<#985 (comment)>
The issue seems to be that in 1.7/1.8 the type is unable to be read by the
mapper due to already being read by the bitfield.
—
Reply to this email directly, view it on GitHub
<#985 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR437QOKXX7R7XQFWFD2ZT2UWDHVAVCNFSM6AAAAABXNWFYIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXGQ3TCNBXGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Can you open a node-minecraft-protocol and mineflayer PR so we can check this works ? |
Closes #958