PrismarineJS / PrismarineJS/node-minecraft-protocol
Errors reading packages when working with a recipe book
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
- The FAQ doesn't contain a resolution to my issue
Versions
- minecraft-protocol: 1.23.1
- server: ??? 1.16.5 (not-vanilla, Spigot/Paper maybe)
- node: 14.15.1
Detailed description of a problem
- Proxy all packets from server to client and vice versa.
- Open recipe book
- After opening the recipe book and it loading client disconnects from the server with an error in the console:
Chunk size is 4 but only 2 was read ; partial packet : {"name":"displayed_recipe","params":{"recipeId":""}}; buffer :1e000100 - After we ignore the packet
displayed_recipeand start flipping through the recipe book the client disconnects from the server with an error:
Chunk size is 36 but only 4 was read ; partial packet : {"name":"recipe_book","params":{"bookId":34,"bookOpen":true,"filterActive":true}}; buffer:1f226d696e6563726166743a626c75655f6479655f66726f6d5f636f726e666c6f776572
Current code
Additional context
It is not possible to catch the data via Debug, there are too many of them.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with examples/proxy/proxy.js and reproduce the recipe-book flow using the listed minecraft-protocol and Node versions. Inspect how the displayed_recipe and recipe_book packets are decoded and forwarded, then verify that opening and browsing the recipe book no longer disconnects the proxied client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100