PrismarineJS / PrismarineJS/minecraft-data
Have more strict audit scripts
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 938
- Forks
- 294
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Description
Try to catch things like:
- recipe pointing to unexisting items
- items that should have recipes missing them
- decreasing block counts between 2 versions (shouldn't happen)
- anything else that could break functionalities of users of this lib and can be caught by simple rules here
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 reviewing the audit-script approach in the linked minecraft-data commit and locate the existing audit scripts in this repository. Check how recipe references, expected recipes, and block counts are represented across versions. Done means simple rules detect the listed inconsistencies and other clearly catchable data breaks without rejecting valid data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-engineering, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100