PrismarineJS / PrismarineJS/minecraft-data
why are the block IDs in this package different from the actual minecraft block IDs?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 25
Description
I've searched actual minecraft blocks IDs, and it differ from IDs in this package. For example: every site about it say that ID of still water is 8, but in this package it is 26. Why is this so? I'm beginner in js and, in particular, in mineflayer, and i don't understand. Sorry for the stupid question, if the question is really like that
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
No file, test, or entry point is named. Start by checking how this package represents block IDs against the Minecraft IDs cited in the issue, then determine whether the difference needs an explanation or documentation update. Done means clearly documenting why the still-water example uses different IDs, if the behavior is intentional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100