Yes. luanti runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test luanti?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit b81bb3c68ac6. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test luanti?

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 luanti take to install?

12 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 luanti need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing luanti?

3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for luanti?

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.

luanti

Luanti (formerly Minetest) is an open source voxel game-creation platform with easy modding and game creation

Runssource: GitHub homepageC++NOASSERTIONcommit b81bb3c68ac6

C++, NOASSERTION licensed. The project labels itself: c plus plus, cpp17, game engine, lua, luanti, minetest, voxel and voxel engine.

luanti runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Luanti server binary (luantiserver) builds and runs; all 161748 unit test assertions pass across 6 test cases.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.06 (measured)
recorded runs: 3
last tested: 2026-09-22
stars: 13,633
forks: 2,460
open issues: 1,508
watchers: 314
size: 138 MB
created: 2011-08-07
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

Time lost to each failure while testing luanti, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Missing -dev packages for sqlite3, zstd, zlib, png, jpeg, sdl2, freetype, luajit, ogg, vorbis, openal, curl, gmp, jsoncpp, ncurses, mesa, gettext8 minutes
find_symbol_exists(ZSTD_initCStream) failed during CMake configure because check_symbol_exists could not link against the static lib2 minutes
Missing libz.so.1.3 and libzstd.so.1.5.5 shared libraries in local sysroot (symlinks pointed to non-existent files)1 minute

Install time: 12 minutes
Cold machine to finish: 11 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: cd /work/repo && HOME=/work/repo ./bin/luantiserver --run-tests passed: all 161748 assertions in 6 test cases; ./bin/luantiserver --version returned 'Luanti 5.18.0-dev-b81bb3c-dirty (Linux)'
Model tokens used: 446,220
Exact commit tested: b81bb3c68ac6
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

1. **Missing all -dev packages** — Downloaded 16 `.deb` packages and extracted headers/libs to `/tm…
2. **FindZstd.cmake check_symbol_exists failure** — The module verified `ZSTD_initCStream` by compi…
3. **Broken .so symlinks in local sysroot** — The `.deb` extracts included `.so -> .so.X.Y` symlink…
### Verification
- **`./bin/luantiserver --version`** returned:
  ```
  Luanti 5.18.0-dev-b81bb3c-dirty (Linux)
  Using Lua 5.1.5
  Built by GCC 13.3
  ```
- **`./bin/luantiserver --run-tests`** passed: **all 161748 assertions in 6 test cases**.
### Final JSON

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 12 minutes, faster than the median of the 4 comparable projects Argusic has measured.
Recovered from all 3 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.
Measured 3 times, so the result is not a one-off.

What did not, or is not known

Its license file could not be classified automatically, so check it yourself before using it.

Of the 5 c-plus-plus projects Argusic has installed and timed, luanti was the 1st fastest to reach a running state, and 4 of 5 reached one at all.

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	3/3	Runs	100.00	0.06	2026-09-22 22:27 UTC
Argusic Runner	2/3	Runs	100.00	0.39	2026-09-15 14:12 UTC
Argusic Runner	1/3	Runs	100.00	0.14	2026-09-05 02:41 UTC

Topics (from GitHub)

c-plus-plus cpp17 game-engine lua luanti minetest voxel voxel-engine

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/luanti.svg)](https://argusic.com/subject/luanti)

Questions

Does luanti run?: Yes. luanti runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test luanti?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit b81bb3c68ac6. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test luanti?: 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 luanti take to install?: 12 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 luanti need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing luanti?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does luanti compare with the alternatives?: Of the 5 c-plus-plus projects Argusic has installed and timed, luanti was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for luanti?: 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.