Eldiron
Create cross-platform classic RPGs in 2D and 3D with powerful built-in world editing tools.
Runssource: GitHubhomepageRustMITcommit 4b0908dc7eb3
Rust, MIT licensed. The project labels itself: classic, creator, eldiron, game development, game engine, gamedev, pixel art and procedural.
Eldiron runs. An Argusic agent installed it in 22 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Eldiron workspace compiles successfully for all 16 member crates. The test suite passes 617 tests across 6 library crates. Both GUI binaries (eldiron-creator, eldiron-client) build, link, and launch on the virtual display, reaching wgpu initialization before failing due to no GPU adapter in the container.
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 100 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.
- Missing system dev libraries: fontconfig, wayland-client, alsa .pc files and .so symlinks2 minutes
- d2builder.rs uses Widget unconditionally outside graphics feature gate2 minutes
- Missing Rust toolchain1 minute
- Test compilation: PartyProbe mock missing say() method1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --package rusterix returned 463 passed/2 failed; eldiron-ruleset 73 passed; buildergraph 9 passed; eldiron_scepter 4 passed; procedural-recipes 66 passed; xtask 2 passed. Release builds: creator and client binaries produced and execute on Xvfb display.
- Model tokens used
- 131,993
- Exact commit tested
- 4b0908dc7eb3
- 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
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
**Verified builds:** - `eldiron-creator` ✓ (release build, launches on Xvfb but panics on `AdapterNotFound` - no GPU in … - `eldiron-client` ✓ (release build, launches but same GPU issue) - `eldiron-client-terminal` ✓ (compiles, no tests) **Test results:** - `rusterix`: 463 passed, 2 failed (pre-existing) - `eldiron-ruleset`: 73 passed - `buildergraph`: 9 passed - `eldiron_scepter`: 4 passed - `procedural-recipes`: 66 passed - `xtask`: 2 passed - Total: **617 tests pass**
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 22 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
classiccreatoreldirongame-developmentgame-enginegamedevpixel-artproceduralretrorpgultima
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/eldiron)Questions
- Does Eldiron run?
- Yes. Eldiron runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Eldiron?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4b0908dc7eb3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Eldiron?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Eldiron take to install?
- 22 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 Eldiron need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Eldiron?
- 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 Eldiron?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.