PrismarineJS / PrismarineJS/minecraft-data
Fix bedrock protocol entity metadata
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 25
Description
From https://github.com/PrismarineJS/minecraft-data/pull/734#discussion_r1261347563,
Entity metadata enum may be wrongly numbered on 1.19.40+,
However, there are inconsistencies between numbering in PocketMine and Gophertunnel here, so this will need to be investigated later. (PocketMine doesn't list
update_properties; andBASE_RUNTIME_IDis in a different index). But we can address this later on since there is no clear path to resolution at the moment.
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 entity metadata definitions in PocketMine's EntityMetadataProperties.php and Gophertunnel's entity_metadata.go, focusing on 1.19.40 and later. Investigate the conflicting indexes for update_properties and BASE_RUNTIME_ID, then verify the repository's corresponding Bedrock protocol data. Done means the numbering is resolved and the metadata data is corrected with supporting validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100