warzone2100
Command the forces of The Project in a battle to rebuild the world after mankind has been nearly destroyed by nuclear missiles. A 100% free and open source real-time strategy game for Windows, macOS, Linux, BSD+
Runssource: GitHubhomepageC++GPL-2.0commit 549de5860df0
C++, GPL-2.0 licensed. The project labels itself: c plus plus, campaign, cheats, cmake, freebsd, game, games and internet.
warzone2100 runs. An Argusic agent installed it in 78 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Warzone 2100 builds and runs successfully. The binary at build/src/warzone2100 can launch in headless/autogame mode and play skirmish games with AI opponents.
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 packages (no root access). Downloaded .deb packages and extracted to a local sysroot.15 minutes
- SDL3 not available on Ubuntu 24.04 (requires SDL3 >= 3.2.12)12 minutes
- Missing runtime .so versioned files for curl dependencies (brotli, nghttp2, nettle, hogweed, gmp, gnutls, unistring, gssapi_krb5, lber, ldap, ssh, psl, sasl2, ssl)10 minutes
- Git submodules not initialized (3rdparty deps + data files needed)8 minutes
- CMake configuration failures due to missing submodules (utf8proc, launchinfo, fmt, re2, fonts, ControllerImage, terrain_overrides, campaign data)5 minutes
- Static linking of libcurl.a causes endless dependency chain of private libs (needing gssapi_krb5, lber, ldap, sasl2, ssl, crypto, pq, mysql)5 minutes
- Install time
- 78 minutes
- Cold machine to finish
- 75 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- Model tokens used
- 985,671
- Exact commit tested
- 549de5860df0
- 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.
Now let me compile the final report.
exec
/bin/sh -lc '# Calculate total time from the session start
# The session started at some point, let me just check elapsed
echo "Install time estimation:"
# Check when the shell started (approximately)
ps -o pid,etime -p 1 2>/dev/null | tail -1' in /work/repo
succeeded in 0ms:
Install time estimation:
1 01:15:12
tokens used
985,671Replay 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.
- Recovered from all 7 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-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 78 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 c-plus-plus projects Argusic has installed and timed, warzone2100 was the 5th 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 | 1/3 | Runs | 100.00 | 0.64 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.20 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.32 |
Topics (from GitHub)
c-plus-pluscampaigncheatscmakefreebsdgamegamesinternetjavascriptlinuxmacmacosmultiplayeropen-sourcereal-time-strategyrtsstrategy-gamewindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/warzone2100)Questions
- Does warzone2100 run?
- Yes. warzone2100 runs. Argusic installed and launched it on a clean machine in 78 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test warzone2100?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 549de5860df0. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test warzone2100?
- The run that produced this verdict cost $0.64: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does warzone2100 take to install?
- 78 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 warzone2100 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing warzone2100?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does warzone2100 compare with the alternatives?
- Of the 5 c-plus-plus projects Argusic has installed and timed, warzone2100 was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for warzone2100?
- 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.