The six redstone wire rules nobody reasons their way to

Redstone looks like logic gates and reads like logic gates, so the instinct is to reason about it the way you would reason about a circuit diagram: signal goes in here, comes out there, therefore the lamp lights. That instinct is wrong often enough to be dangerous, and it is wrong in specific, repeatable ways. This is also, not coincidentally, the exact place large language models fail at building Minecraft redstone — on the SciCraft-Bench benchmark, every frontier model tested plateaus near 26%, and the dominant failure class is wire semantics rather than anything conceptually harder. Cubelings does not ask a model to derive redstone wiring live; it places verified circuits from a library, and this library is built on the six rules below.

1. Build order is load-bearing

Placing a block with setblock does not make an already-placed neighbour re-evaluate its redstone state. Put a lamp down next to a live power source and it stays dark, because nothing told it to check. Place the power source last and the lamp lights, because that placement is what triggers the update. The fix is not cleverer wiring — it is placing power after everything else, every time.

2. A repeater's facing points at its input, not its output

A signal travelling west to east needs a repeater facing west — pointed back at where the signal is coming from, not forward at where it is going. This is the single easiest thing to get backwards, because every instinct about "facing" reads it the other way around.

3. Dust only powers the block it points into

Redstone dust powers the specific block at the end of its run — not every block that happens to sit next to it. A block merely adjacent to a run of dust is not powered by it, even though it looks connected in the world.

4. Dust needs a solid block underneath every cell

Dust on air breaks the circuit silently. There is no error, no visual difference, nothing to see — the run simply stops carrying signal at that cell, and the only way to notice is that whatever it was supposed to drive does not turn on.

5. A repeater cannot turn a corner

A repeater only passes signal in a straight line. On a corner, its input side is facing where the wire is not, so it cannot legally sit there at all. This matters for anything circular: a rasterised circle is almost entirely corners — measured on a radius-14 ring, one stretch came out as 19 consecutive cells with no straight run anywhere in it, meaning no repeater could go there and dust simply decayed to nothing partway through. A ring built from a square with its corners cut, instead of a true circle, keeps long straight runs where repeaters can actually live.

6. A closed loop of repeaters latches itself on

Wire a ring of repeaters all the way back around to its own start and it does not need an external signal to stay lit — a transient pulse during construction circulates back into itself and holds the whole ring powered, lever or no lever. One version of a chase-ring build closed the loop with only a single missing cell as a gap, on the assumption that one cell was enough separation. It was not: a feed assembly built into that gap bridged it, and 26 of 111 cells stayed powered with the lever off. The gap has to be wide enough that nothing built near it can accidentally close the loop back up.

Why this adds up to "place from a library, don't derive it"

None of these six rules is individually exotic. What makes redstone hard to get right by reasoning alone is that a working circuit has to satisfy all six simultaneously, and a single violation anywhere in a hundred-cell ring fails silently — no error message, just a lamp that never lights or a ring that never turns off. A stray leftover block from an earlier build left inside a circuit's footprint has been enough on its own to hold part of a ring powered permanently: one build kept 17 of 109 cells lit with the lever off, because a forgotten observer clock on the site was feeding the new circuit power it was never supposed to have. The fix in every one of these cases was the same: verify the circuit against the world after building it, not just trust that the wiring plan was correct.

Read more about how that verification works on the Verification page, or see the full skill list on Capabilities.