max-mapper / max-mapper/voxel-server
No world is generated using node 0.12.x
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I haven't tracked this down to exactly where the problem lies yet, but I believe that there is a problem with either voxel-server, or possibly voxel-crunch using node 0.12.x. It seems that the world generates, but the entire voxel-crunch data arrays are filled with 0's instead of blocks.
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
Reproduce world generation with Node 0.12.x in voxel-server and inspect whether voxel-crunch data arrays contain blocks or only zeroes. First determine whether the failure belongs to voxel-server or voxel-crunch; done means identifying the responsible component and restoring nonzero generated block data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100