max-mapper / max-mapper/mca2js
configurable chunk output dimensions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
this module currently outputs voxel chunks that are 16 x 16 x 16.
in order to support other sized chunks some more logic needs to be added. the reason it uses 16 is that minecraft chunk are 16 x 16 x 256 so its pretty easy + efficient from a streaming parser standpoint to split each minecraft chunk up in to 8 chunks and emit them.
in order to support, for instance, 32 x 32 x 32 this module would have to buffer a bunch of minecraft chunks before it could emit the chunk and gc the minecraft chunk.
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
Locate the module that emits 16 x 16 x 16 voxel chunks and trace how Minecraft chunks are buffered, split, emitted, and released. Determine the buffering and emission behavior needed for configurable dimensions such as 32 x 32 x 32, then verify that the module still produces correctly sized typed-array chunks without retaining unnecessary Minecraft chunks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100