PrismarineJS / PrismarineJS/minecraft-data
Make bedrock entity packet fields consistent across all versions
Open
Nobody has claimed this yet.
bedrock
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
... fields should be runtime_id or unique_id in the entity packets, entity_runtime_id/entity_unique_id in the non-entity packets
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/bedrock/1.19.1/proto.yml and data/bedrock/1.19.40/proto.yml files, then inspect the other Bedrock proto.yml versions. Compare entity and non-entity packet fields across versions; done means entity packets consistently use runtime_id or unique_id and non-entity packets use entity_runtime_id or entity_unique_id.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100