i365dev / i365dev/CraftDAG

Future: Add schematic-to-CraftDAG / tutorial adapter

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
1h 3m
Merged PRs (30d)
3

Description

Context

Inspired by Arnis: the most valuable Minecraft generators are often stable data pipelines, not autonomous agents.

For CraftDAG, the most relevant future input adapter is not OSM/world generation, but existing Minecraft structure files.

Idea

Add a future adapter that can read an existing .schem / .litematic file and derive useful build-planning outputs:

.schem / .litematic
→ VoxelPlan
→ material list
→ layer guide
→ optional component inference
→ simplified tutorial

Why this matters

This would let MinePilot support workflows such as:

  • upload an existing schematic
  • inspect it in 3D
  • get material list
  • get layer-by-layer guide
  • simplify or restyle later

This may be more practical than trying to generate large buildings from scratch.

Suggested phases

  1. Parse .schem into VoxelPlan.
  2. Generate material list and layer guide from imported VoxelPlan.
  3. Add basic component inference later, such as foundation / walls / roof / decoration.
  4. Expose this through MinePilot as schematic-to-tutorial.

Non-goals

  • Do not implement this before MinePilot playground MVP.
  • Do not attempt perfect semantic reconstruction in the first version.
  • Do not add OSM/geographic generation here.

Acceptance criteria for first implementation

  • A .schem file can be parsed into VoxelPlan.
  • Imported VoxelPlan round-trips through material/layer generation.
  • Tests cover at least one fixture schematic.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing VoxelPlan representation and the material and layer generation paths. Then investigate how a fixture .schem file could enter the pipeline and what parsing support is needed. Done means one .schem fixture parses into VoxelPlan, round-trips through material and layer generation, and is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.