PrismarineJS / PrismarineJS/minecraft-data
Issue with Block State (blocksB2J.json and blocksJ2B.json) Data in Version 1.20.30
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
I'm a big fan of your project and I've been using it extensively. Recently, I've encountered an issue with block state data since Minecraft version 1.20.30.
They changed some state of slab in version 1.20.30
Now uses the minecraft:vertical_half block state instead of top_slot_bit
While I understand there might be changes to the data format in newer versions, I wanted to bring this to your attention in case it's an unintended consequence of the update.
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 inspecting blocksB2J.json and blocksJ2B.json for the slab block-state mappings and compare their 1.20.30 entries with the linked Minecraft block-state changes. Done means the mappings represent minecraft:vertical_half instead of top_slot_bit for the affected slabs in both directions; no test or run command is mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100