ggez
Rust library to create a Good Game Easily
Runssource: GitHubhomepageRustMITcommit 9c8654745040
Rust, MIT licensed. The project labels itself: crates, engine, game, game development, game engine, game frameworks, gameengine and rust.
ggez runs. An Argusic agent installed it in 18.2 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The ggez Rust library builds and runs with all default features (audio, gamepad); the example 02_hello_world launches and renders at ~180 FPS via Lavapipe Vulkan software rendering, and 44 of 45 tests pass (the sole failure is winit preventing event loop creation on cargo test's non-main thread, a known documented limitation).
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.
- Vulkan ICD missing — graphics initialization failure3 minutes
- Rust toolchain not installed2 minutes
- alsa-sys build failure: missing libasound2-dev headers/pkg-config2 minutes
- Audio initialization fails at runtime (no ALSA hardware)2 minutes
- libudev-sys build failure: missing libudev-dev1.5 minutes
- Missing libEGL.so and libGLESv2.so symlinks1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- cargo test --workspace passed 44/45 tests (22 doc_tests + 22 lib tests, 1 known-broken has_traits). cargo run --example 02_hello_world with DISPLAY=:99 VK_ICD_FILENAMES=lvp ALSA_CONFIG_PATH=null_pcm ran for 8 seconds and printed FPS: 170-182.
- Model tokens used
- 113,874
- Exact commit tested
- 9c8654745040
- 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.
6. **Graphics initialization failure** — No Vulkan ICD driver. Downloaded `mesa-vulkan-drivers`, ex… tokens used 113,874 Let me compile the final results. The project is working end-to-end. Here's a summary of errors encountered and fixes applied, then the JSON report. **Errors found and fixed:** 1. **Rust toolchain not installed** — Installed via rustup, set `stable` as default. 2. **`alsa-sys` build failure** — `libasound2-dev` not installed. Downloaded the `.deb`, extracted … 3. **`libudev-sys` build failure** — `libudev-dev` not installed. Same extraction approach: downloa… 4. **Audio initialization failure at test runtime** — No ALSA hardware device. Created a null PCM `… 5. **winit event loop on non-main thread** — `context::tests::has_traits` test fails because winit … 6. **Graphics initialization failure** — No Vulkan ICD driver. Downloaded `mesa-vulkan-drivers`, ex…
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 18.2 minutes.
- 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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)
cratesenginegamegame-developmentgame-enginegame-frameworksgameenginerust
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ggez)Questions
- Does ggez run?
- Yes. ggez runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test ggez?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9c8654745040. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ggez?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ggez take to install?
- 18.2 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 ggez need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ggez?
- 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.
- Where is the evidence for ggez?
- 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.