Guide

Game circuit and power routing puzzle systems explained

Harbor Generator Station’s “Triple Bus” chamber shipped with three receivers, two generators, and a crate of rotatable AND gates. The design doc required players to route sustained power to all three doors simultaneously. Only 21% of playtesters cleared the room; the rest reset after ten minutes of rewiring. Session replays showed the same root cause: a T-junction silently overwrote one input when two wires met, and AND gates evaluated on the same frame the player toggled a switch — producing a one-frame glitch pulse that opened the middle door but not the outer two. After fixing junction merge rules, adding one-tick gate propagation delay, and surfacing remaining wire budget on the HUD, completion rose to 68% without removing any logic step.

Circuit and power-routing puzzles ask the player to connect sources to receivers through a graph of wires, splitters, and logic gates. Unlike pressure plates where the player steps on triggers, or beam puzzles where rays bounce through space, circuit puzzles emphasize topology: which nodes connect, in what order signals propagate, and how boolean logic combines inputs. This guide covers the signal graph model, component types, simulation tick rules, player placement UX, softlock detection, the Harbor Generator Station refactor, a technique decision table, pitfalls, and a production checklist.

Circuit puzzles vs adjacent puzzle families

Four puzzle families overlap in level design but differ in what the player manipulates:

Pressure plates and switches — discrete emitters fire boolean events into a logic layer; wiring is often invisible. Good when the player should stand on things, not draw lines.
Light beams — continuous rays through 3D space with mirrors and color filters. Spatial aiming matters more than graph editing.
Inventory keys and locks — permission tokens unlock doors; no live signal propagation.
Circuit routing — the player (or designer) builds an explicit graph: sources, wires, gates, receivers. The puzzle is the wiring diagram.

Many shipped rooms hybridize: a puzzle platformer might use plates to enable a generator while the player routes its output through XOR gates to three doors. The implementation still needs a coherent signal model underneath.

Signal graph fundamentals

Model every circuit room as a directed graph updated on discrete ticks (or on every player edit, for instant-feedback editors):

Nodes — generators, receivers, gates, junctions, switches, timers, capacitors.
Edges — wires with a direction (or bidirectional copper). Each edge carries a signal value: off, on, or colored/channel id.
Sources — emit sustained on, timed pulses, or player-toggle states.
Sinks — doors, elevators, lasers, or score counters that react when their input predicate is true.

Evaluation order matters. A robust pattern is topological propagation: sources first, then nodes in dependency order, one full pass per tick. Cycles (feedback loops) require explicit latch or delay components — never let undefined oscillation reach receivers without a player-visible clock.

Sustained vs pulse semantics

Pick one primary semantics and document it:

Sustained power — a receiver stays open while its input is high. Generators and switches hold state until toggled.
Pulse power — a short on-edge triggers a one-shot (open door for 2s, advance a counter). Requires edge detection on receivers.

Mixing both in one room without visual distinction causes the classic “it worked for a frame” bug Harbor hit. Color-code sustained lines (solid glow) vs pulse lines (dashed) and gate outputs that stretch pulses (monostable) vs pass level (buffer).

Component catalog

Most circuit puzzles reuse a small toolkit. Implement each as a node type with documented port count and truth table:

Component	Ports	Behavior
Wire / trace	2	Passes signal; may have max length or bend count budget.
T-junction / splitter	1 in, N out	Broadcasts input to all outputs; define priority if multiple inputs meet (OR merge vs error).
Diode / one-way valve	2	Blocks backward propagation; prevents accidental feedback.
AND / OR / NOT / XOR	2–3	Boolean combine; XOR useful for “exactly one source” puzzles.
Toggle switch	1–2	Player flips sustained state; may require line-of-sight interaction.
Timer / delay line	2	Outputs input delayed by K ticks; enables sequence puzzles.
Capacitor	2	Charges while input high; discharges over time when input drops.
Receiver / actuator	1+	Door opens when predicate true; may require AND of multiple ports.

Colored channels (red wire only powers red receivers) add a matching layer without new logic primitives. Keep channel count low (2–3) in tutorial tiers; universal copper is easier to read for first-time players.

Player interaction and placement UX

How the player edits the graph defines feel as much as the logic:

Drag-to-wire — click source, drag to target; snap to grid nodes. Show invalid targets (occupied port, wrong color) immediately.
Place-and-rotate components — pick gate from inventory, rotate with R/Q; ports must align to grid facing.
Wire budget — limit total segments or component count so brute-force spaghetti fails; display remaining budget prominently.
Undo stack — circuit puzzles demand experimentation; one-level undo is minimum; full room reset should preserve camera position.

Run a connectivity preview on hover: ghost-highlight the subgraph that would energize if this wire completed. Players solve faster when they see consequences before committing.

Feedback loops players can read

Audio and animation should encode signal state: hum pitch rises with load, gates click on rising edge, receivers pulse red when under-powered. When a junction OR-merges conflicting inputs, a brief spark VFX beats silent wrong behavior.

Simulation, validation and softlocks

Treat puzzle rooms like small programs. Before shipping a chamber:

Solvability check — offline search over switch configurations and rotatable gates (BFS with pruning) to confirm at least one solution energizes all required receivers.
Softlock detection — flag states where a consumable wire segment was spent but no receiver is reachable; offer reset pedestal.
Cycle audit — pure wire cycles without a delay node should not reach receivers; either reject placement or insert implicit delay.
Unique solution policy — decide whether multiple wirings count as success (usually yes) or whether you gate on a canonical layout (rare; frustrates creative players).

Log anonymized circuit_state_hash on abandon to find clusters of stuck players — often a single junction rule, not puzzle difficulty.

Harbor Generator Station refactor

The Triple Bus room targeted simultaneous power to three doors from two generators with one XOR teaching gate. Failures clustered into three buckets:

Junction overwrite (44% of abandons) — second wire into a T-node replaced the first instead of OR-merging. Fix: explicit merge policy per node type; document in tutorial tooltip.
Same-frame gate glitch (31%) — switch toggle and gate eval in one frame produced a pulse that fooled the middle door sensor. Fix: evaluate gates on tick t+1 after input changes.
Hidden wire budget (25%) — players ran out of segments without knowing why the last connection failed. Fix: HUD counter + red preview on over-budget drag.

A one-room micro-tutorial with a single AND gate between one generator and one door was added before Triple Bus. Completion moved from 21% to 68%; median solve time dropped from 11.4 to 6.2 minutes.

Technique decision table

Design goal	Prefer	Avoid
Teach boolean logic	Circuit graph with visible AND/OR gates	Invisible plate logic with no diagram
Spatial aiming challenge	Beam mirrors and receivers	Grid-only wiring with no 3D placement
Timed sequence (A then B)	Delay lines and pulse detectors	Sustained-only receivers with no edge semantics
Player carries tokens between rooms	Key-lock inventory gates	Persistent wire state across level loads
Co-op dual activation	Pressure plates + shared bus	Two separate circuit editors per client
Factory/automation fantasy	Splitters, diodes, conveyor coupling	Single wire with no branching
Quick readable state	Color + animation on energized edges	Binary doors with no line feedback

Common pitfalls

Ambiguous junction merge — two inputs meet; players cannot predict output.
Pulse vs sustained confusion — door opens one frame; player thinks the puzzle is broken.
Same-tick input and eval — gates see stale inputs; order-dependent bugs.
No wire budget feedback — silent failure on last segment.
Unsolvable or unique-wire traps — spent consumables brick the room.
Feedback loops without delay — flicker or undefined state on receivers.
Too many gate types at once — XOR + timer + color before AND is taught.
Invisible logic layer — plates drive doors but players never see the graph they are supposed to learn.

Production checklist

Define sustained vs pulse semantics; never mix without distinct visuals.
Document junction merge policy (OR, reject, priority port).
Evaluate gates one tick after input changes.
Expose wire or component budget on the HUD at all times.
Provide undo and a one-gate tutorial before multi-receiver rooms.
Run offline solvability search on rotatable/switch configurations.
Reject or delay pure cycles that reach receivers without a clock node.
Animate energized edges; audio-code load and rising edges.
Log circuit_state_hash on room abandon for clustering.
Hybrid rooms: share one signal bus between plates, beams, and wires.
Playtest with screen reader off — color-only channels fail accessibility.
Reset pedestal restores consumables and gate rotation defaults.

Key takeaways

Circuit puzzles are graph puzzles — topology and propagation order matter more than texture art.
Junction and tick rules must be explicit — silent merges caused nearly half of Harbor abandons.
Harbor Triple Bus went from 21% to 68% completion with merge fixes, gate delay, and wire-budget HUD.
Hybrid with plates and beams works when one signal bus feeds all actuator types.
Solvability CI catches softlocks before players do.