Redstone and Commands in Horizon on Android: What the Harnesses Prove

Pretty rendering is easy to fake in a screenshot; redstone is not. This guide, for players of the build from the Horizon Launcher app who build machines and run servers, explains what the Horizon project actually measured about the systems technical players care about.

Redstone, ticking and block behaviour

Block updates, random ticks and redstone were compared against vanilla across thousands of cases, with dispensers run through 6,000 cases and crafters through 4,000 crafts. Copper golem chest sorting and the sculk family, shrieker warnings and warden summoning included, passed their scenarios as well.

That is the correct way to earn a technical player trust: not with a claim that redstone works, but with counts of the exact behaviours machines depend on, published where anyone can read them.

Every command, parsed and run

The harness record for menus, HUD and chat reports every command running as vanilla: 758 commands across 39,685 parsed inputs. Scoreboards and teams matched over 81,000 operations, and menu clicks, the loom, the crafter and the recipe book were compared over thousands of sequences.

For server operators and map makers, those numbers translate plainly: command blocks, functions and scoreboard logic built for vanilla are being executed by a client and server pair that was measured doing exactly that. the multiplayer guide covers the multiplayer side of the same evidence.

The honest edges of the proof

The project is equally public about the frontier: players still find differences, parity work on 26.3 continues, and redstone is named as the first priority of that continuing work. A rewrite under active development should be judged by its trajectory and its transparency, and on both counts the record is strong.

Practically: build your machines, test your contraptions, and keep the Java client as the reference for anything truly exotic. the vanilla worlds guide explains how the shared save format makes that belt and braces approach painless.

Tested on our own Android phones with the current build, like every guide on this site. If a step behaves differently on your device, tell us through the contact page and the guide gets corrected, not defended.