PrismarineJS / PrismarineJS/minecraft-data
Functional variations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 937
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
blocks.json and items.json already contain "simple variations" : only the metadata and the displayName changes (for example stones).
But there is an other kind of variation : functional variations, examples :
These variations store information based on a state stored in bits.
How to store this in minecraft data ? related to #18
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
Review blocks.json and items.json, starting with the existing simple variations such as stones, then compare them with the bit-based functional variation examples linked in the issue. Read related issue #18 for context. Done means defining and documenting how functional variations should be represented in the Minecraft data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100