PrismarineJS / PrismarineJS/node-minecraft-protocol
Bungeecord and spigot 1.12.1
Open
Nobody has claimed this yet.
non-vanilla
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
I randomly receive this error:
Error: Deserialization error for play.toClient : Read error for name : 116 is not in the mappings value ```
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 by reproducing the deserialization error with Bungeecord and Spigot 1.12.1, recording the packet and protocol version that trigger it. Inspect the play.toClient packet mappings around name value 116; done means the cause is identified and the affected version combination has a verified regression test or documented resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100