Minecraft Building

Minecraft building

Builds are a replayable op log (WorldEdit commands, schematic pastes, console commands) developed on a throwaway canvas seeded with a captured copy of the real site, then promoted to the target as one exact snapshot paste with an undo snapshot and journal. Everything runs through the mc-harness daemon; load the minecraft-harness skill for daemon and sandbox basics.

Targets are sandboxes only for now. Never promote without showing the user the render and getting a go-ahead when the target is a server people play on.

The loop

1. Brief. Pin down style, footprint, height, and the exact area (world + two corners). Ask if the area is unknown — never guess coordinates.

2. Init and capture the site (include ground under the build and some margin around it):

   toolkit mc build init ./builds/cottage --name cottage --world world --anchor 26,-60,26
   toolkit mc build capture ./builds/cottage --target <id> --world world 20,-61,20 40,-45,40

   Read renders/site.png before designing; note slope, water, trees.

3. Canvas: toolkit mc build canvas ./builds/cottage — a void sandbox with the site pasted at the same coordinates; it becomes the default target.

4. Author with either or both:

   • WorldEdit, recorded: toolkit mc we --target <canvas> --record <dir> --world world --pos1 x,y,z --pos2 x,y,z "//set …". Always give explicit coordinates (--pos1/--pos2 or --at); negative values need no quoting. See references/worldedit-cookbook.md.
   • Program (build.ts, precise architecture): edit it, then toolkit mc build compile <dir> (compiles, lints, and replaces the earlier program ops in the log). See references/dsl-cheatsheet.md, and references/craft.md (shape, depth, roofs), references/palettes.md (blocks, gradients, proven palettes) and references/landscape.md (terrain, water, paths, craft.tree) before designing. Start from the closest curated program: library search --tag <t>, then library use <slug> <dir>. Before writing helpers, check toolkit mc build component ls and import shared components (terrain, rocks, house, ramparts, …) — see references/components.md.
   • Import an existing design: toolkit mc build import <dir> <file> [--at x,y,z] takes .litematic or .schem; an OBJ mesh (statues, organic shapes, image→3D output) also needs --height <blocks> and optionally --solid and --palette wool|concrete|terracotta. Each import appends a paste op and renders a preview to check before run.

5. Run, look, critique:

   toolkit mc build run <dir>        # reset canvas to site, replay all ops, freeze result
   toolkit mc build render <dir>     # contact sheet PNG — open it with Read
   toolkit mc build lint <dir>

   Fix every lint error, then critique with references/rubric.md:

   • Do at least two render → critique → revise iterations (≤5 total). Each one scores all eight aspects 0–2, names the lowest, and makes one concrete change for it; re-render and look again.
   • A theme is a palette, not a design. Before promoting, the build must go beyond the defaults on massing (L-shape from two footprints, a second story, a wing or tower), roof (gable vs hip, cross gable, dormer) and one detail (chimney, porch, garden, path, flower boxes).
   • Optional second opinion: toolkit mc build judge <render> <render> runs an order-swapped vision judge (default gpt-6.1-sol; needs OPENAI_API_KEY).
   • Report the final scores and at least one remaining weakness. A clean lint is not a good-looking build; say what you actually see.

6. Replay: toolkit mc build replay <dir> replays the log on a fresh seeded sandbox. A mismatch means non-deterministic ops (random % patterns); promote is still exact because it applies the frozen result. Verify and replay ignore state the server recomputes from neighbors (pane, fence and wall connections, stair shape, leaf distance), so panes are fine.

7. Show the user the final render (and lint summary) before promoting.

8. Promote: dry run prints a planHash and how many blocks change; then confirm:

   toolkit mc build promote <dir> --target <id>
   toolkit mc build promote <dir> --target <id> --confirm <planHash>

   It refuses if the target drifted from the captured site (re-capture and rebuild). The result is verified cell by cell and journaled.

9. Undo if needed: toolkit mc build undo <applyId> (last in, first out; restores block entities such as chest contents). `toolkit mc build status

   <dir>` lists applies.