Skip to content
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.18+ Book editing feature #876

Merged
merged 4 commits into from
Jun 14, 2024
Merged

Conversation

unlimitedcoder2
Copy link
Contributor

In 1.18 a new book editing packet was added
PrismarineJS/mineflayer#3204

Comment on lines 240 to 248
"name": "hasEditBookPacket",
"description": "book editing is handled through a packet",
"description": "book editing is handled through a packet with the updated book item",
"versions": [
"1.13",
"1.17.1"
]
},
{
"name": "hasNonNbtEditBookPacket",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The feature naming is confusing here. Can you elaborate what exactly the difference in packet is before vs after?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old edit book packet serializes the item and uses the nbt data from that
image

New packet sends the pages and title as packet fields
image

Copy link
Member

@extremeheat extremeheat May 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding a new editBookPacketUsesNbt feature then (to match old versions)? This seems clearer than the current naming between hasEditBookPacket and hasNonNbtEditBookPacket, as there is actaully an edit book packet on both version ranges.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@extremeheat extremeheat merged commit af0ce69 into PrismarineJS:master Jun 14, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants