horizon
Minecraft: Java Edition 26.3 rewritten from scratch in Rust, checked against vanilla with 281 differential harnesses. Get it with the Horizon launcher.
Runs with mockssource: GitHubhomepageRustMITcommit 4a675206b1cf
Rust, MIT licensed. The project labels itself: differential testing, game engine, gamedev, linux, minecraft, minecraft java, reimplementation and rust.
horizon runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Horizon builds and all Rust crate tests pass (1074 client lib, 159 world, 104 core, 84 protocol, 50 server, 257 Python), launcher builds and tests (117/1 flaky), dedicated server binary responds to commands; GUI client requires a GPU with Vulkan to render, which this container lacks.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- horizon-dualsense cannot build without libudev-dev headers (no root access)2 minutes
- horizon-telemetry test this_machine_is_described fails: assertion cores(4) > threads(192) due to container CPU topology reporting 192 processors from /proc/cpuinfo1 minute
- Launcher test a_replaced_binary_is_replaced_again_at_its_path fails: binary size assertion 509 != 493, likely build-toolchain-dependent self-size check
- No Vulkan/GPU available in headless container: client fails to create surface on DISPLAY=:99
- Install time
- 16 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --no-default-features -p horizon-client --lib: 1074 passed, 0 failed; python3 -m unittest discover -s tests: 257 passed, 0 failed; cargo test --no-default-features -p horizon-server: 50 passed, 0 failed; horizon-client --help exited 0; horizon-client --dedicated --initSettings exited 0; horizon-server --help exited 0
- Model tokens used
- 358,421
- Exact commit tested
- 4a675206b1cf
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `horizon-client --help` ✓ (shows all options)
- `horizon-client --dedicated --help` ✓ (shows dedicated server options)
- `horizon-server --help` ✓ (shows server CLI options)
- `horizon-client --dedicated --initSettings` ✓ (creates server.properties and eula.txt, exits 0)
- `horizon-client --frames 1` exited with "Failed to create surface" (expected - no Vulkan in conta…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
succeeded in 0ms:
Already output the result.
tokens used
358,421
Already output the result.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 16 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.06 |
Topics (from GitHub)
differential-testinggame-enginegamedevlinuxminecraftminecraft-javareimplementationrustvoxelvulkanwgpu
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/horizon)Questions
- Does horizon run?
- horizon runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test horizon?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4a675206b1cf. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test horizon?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does horizon take to install?
- 16 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does horizon need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing horizon?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for horizon?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.