PrismarineJS / PrismarineJS/minecraft-data
Block variations
Open
Nobody has claimed this yet.
blocks
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
May be instead of adding "(no decay)" in block displayName, create new field with description? Like this:
{
"metadata": 4,
"displayName": "Oak Leaves",
"description": "No decay"
},
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 data/pc/1.12/blocks.json around lines 413-416 and inspect how the block variations are represented. Compare the existing displayName values with the proposed description field, then check nearby block data for consistency. Done means the variation information is represented as a separate field without relying on displayName text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100