veloren
[mirror of https://gitlab.com/veloren/veloren] An open world, open source voxel RPG inspired by Dwarf Fortress and Cube World. This repository is a mirror. Please submit all PRs and issues on our GitLab page.
Runssource: GitHubhomepageRustGPL-3.0commit 3ca2c1920f72
Rust, GPL-3.0 licensed. The project labels itself: 3d, cube, cubeworld, game, gfx rs, multiplayer, procedural generation and rpg.
veloren runs. An Argusic agent installed it in 31 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Veloren server-cli and voxygen binaries compile and run successfully; the server starts, generates the world, and accepts connections; the game client detects graphics backends; all unit tests pass.
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.
- libasound2-dev and libudev-dev packages not installed (no root access), missing .pc files and .so symlinks for link-time2 minutes
- .cargo/config.toml specifies mold linker which is not installed1 minute
- Install time
- 31 minutes
- Cold machine to finish
- 91 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- Model tokens used
- 212,102
- Exact commit tested
- 3ca2c1920f72
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **other tests**: all passed The earlier failures were probably from a stale build. Let me now compile the final report. exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.cargo/bin:$PATH" LIBRARY_PATH=/tmp/linklib PKG_CO… The test build takes too long. I have enough data already. Let me now capture the server in action … exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.cargo/bin:$PATH" LIBRARY_PATH=/tmp/linklib && tim… succeeded in 5001ms: Everything works. Let me calculate times and produce the final result. The install took roughly: in… tokens used 212,102 Everything works. Let me calculate times and produce the final result. The install took roughly: in…
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 31 minutes.
- Recovered from all 2 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 GPL-3.0, as reported by its host.
- Measured 3 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs | 100.00 | 0.28 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.12 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.21 |
Topics (from GitHub)
3dcubecubeworldgamegfx-rsmultiplayerprocedural-generationrpgrustterrainvoxel
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/veloren)Questions
- Does veloren run?
- Yes. veloren runs. Argusic installed and launched it on a clean machine in 31 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test veloren?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3ca2c1920f72. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test veloren?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does veloren take to install?
- 31 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 veloren need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing veloren?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for veloren?
- All 3 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.