Overview #
Redstone Debugger is a professional suite for recording, visualizing, simulating, and analyzing redstone circuits. It captures circuit activity into a replayable timeline (25 event types via mixins — wire, lever, repeater, comparator, observer, torch, button, piston, pressure plate and more), runs diagnostics that surface wiring problems (12 analysis algorithms: signal tracing, dependency chains, root cause, SCC cycles, critical path, clock detection), shows signal states directly in the world through overlays, and can call on an optional AI provider — including local Ollama — to explain what a circuit is doing. All core diagnostics work fully offline.
Redstone is the most complex thing you can build in Minecraft, yet debugging it means staring at torches. Redstone Debugger records circuit activity, replays it, and analyzes it — turning redstone engineering into something you can inspect, not guess.
Quick start #
- Install Fabric and drop the Redstone Debugger JAR for your Minecraft version into your mods folder — best-tested on 1.21.11.
- Launch the game and open a single-player world; stand near the circuit you want to understand.
- Run /rd help to explore the command suite: recorder, timeline, clear, export and perf.
- Press R near the circuit to start recording, then R again to stop — events land in a timeline with atomic tick ranges.
- Open the timeline and step through recorded events one tick at a time; world overlays highlight the corresponding blocks.
- Run diagnostics to surface problems in the recorded activity — /rd explain or /rdebug diagnose <n>.
- Optionally configure an AI provider (including local Ollama) for AI-assisted insights — all core diagnostics work without one.
- Export a recording to share it — the recipient can replay and re-diagnose without your world.
Configuration #
Redstone Debugger tunes through its performance manager and optional AI-provider settings. Recording is client-side and single-player oriented; the recorder auto-stops at extreme event counts to protect performance.
| Setting | Default | Description |
|---|---|---|
| AI provider | None (offline) | Optional providers including local Ollama for AI-assisted insights; every core diagnostic runs offline without one. |
| Recorder auto-stop | Enabled | Recording auto-stops at extreme event counts to protect performance. |
| World overlays | On | Colour-coded signal states shown directly on blocks while recording. |
| HUD overlays | On | In-game HUD showing recording status and diagnostics. |
| Performance manager | Enabled | Profiler, metrics, caching and a memory monitor behind the recorder. |
Frequently asked questions #
Does it slow the game down?
Do I need an AI provider?
Is it server-side or client-side?
What can it record?
Is there a command interface?
Can it explain my circuit?
Which Minecraft version should I use?
Can I share a recording?
Compatibility #
| Property | Value |
|---|---|
| Loader / platform | Fabric |
| Minecraft versions | 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.2, 26.2 |
| Latest version | 1.0.0 |
Best-tested on 1.21.11; some advertised versions lack version-specific compat code — verify before relying on them.