PrismarineJS / PrismarineJS/minecraft-data
Packets and field names
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
Currently packets names are taken from https://github.com/aadnk/ProtocolLib/blob/master/ProtocolLib/src/main/java/com/comphenix/protocol/PacketType.java#L123
I don't know where the fields names are coming from (@roblabla ?)
These names are different from what is currently found in http://wiki.vg/Protocol
Can reasonable names be chosen to make protocol.json more standard ?
The packet name difference with wiki.vg can be seen here https://gist.github.com/rom1504/1b432d5e7efc278015dd/revisions?diff=split
I mapped the new names to the old and got that which show mainly the field names difference :
https://gist.github.com/rom1504/64535ed808327b78c72e/revisions?diff=split
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 comparing the packet names in ProtocolLib's PacketType.java with the wiki.vg Protocol page and the two linked gist revisions. Trace where minecraft-data generates or stores protocol.json, then establish consistent packet and field names and update the affected data. Done means the resulting names are standard and the mappings remain correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100