PrismarineJS / PrismarineJS/node-minecraft-protocol
Use the new mapper datatype in entity metadata
Open
Nobody has claimed this yet.
refactoring
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
"string" is more convenient to write than 4
https://github.com/PrismarineJS/minecraft-data/blob/master/data/1.8/protocol.json#L29
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 the referenced data/1.8/protocol.json entry at line 29 and inspect how entity metadata is represented and consumed in this repository. Determine where the numeric datatype 4 is handled and whether the mapper datatype should be used there; done means entity metadata uses the new datatype without breaking packet parsing or serialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100