0.5.0: nine pull requests and one long morning
0.5.0 was built differently from every release before it.
On the evening of October 12, after 0.4.0 shipped, Chris asked for "as many separate prompts as you can" to run as cloud coding sessions before bed. Each prompt was one self-contained job. Each ran as its own Claude Code session on the web, working on its own branch, and ended by opening a pull request on GitHub. None of them could deploy anything.
That batch produced eleven branches. Nine were merged into 0.5.0:
| Pull request | What it built |
|---|---|
| Contracts | A board of three work orders at the start of each shift, and three missions playable end to end |
| Orientation | The first tutorial: Clancy onboards a new contractor in eight steps |
| Settings | Volume, UI scale, reduce motion, haptics, colorblind kill-chain colors, fullscreen |
| Voice pass | Every Clancy and AI crew line moved out of the code into data files, with rules for how they're spoken |
| Audio pass | A second wave of synthesized sound effects and a layered score that follows the crew's stress |
| Steam prep | Optional Steam support, 19 achievements, rich presence, a draft store page |
| Account page | Change your password, see your sessions, sign out everywhere |
| CI | Automatic tests on every pull request; Linux and Windows builds on every merge |
| Balance | A harness that plays hundreds of simulated shifts, and the tuning it showed was needed |
Two earlier cloud sessions that evening had already shipped in 0.4.0: the second wave of 3D models, and a fix to track Godot's resource IDs.
Two of the eleven weren't merged. The shards work (a way for approved community servers to join a shared universe) needs to be redone on top of everything else and is still waiting. Two sessions had independently built contracts; one version was merged, and the other wasn't needed.
What you can play
Contracts. Every shift now opens on a board of three work orders, and Command signs one:
- STRIP: bank a quota of REGARD before the clock runs out, then call the jump.
- RECOVER: pull the core out of a wreck before it folds, then get clear.
- REPOSSESSION: hold off every wave of repo drones, or pay the arrears out of your hold to call them off.
Clancy lies differently in each one. In STRIP he spots a "second, richer deposit just north of you!" that isn't there. In RECOVER he tells you which section of the wreck the core is in, and he's guessing.
The first tutorial. Eight steps across all five chairs, ending in one shot that takes all five. Clancy narrates and is a little wrong every time. A coach card on screen tells you the truth.
A settings screen, including a colorblind palette for the kill-chain gates and a reduce-motion switch that turns off screen shake.
A voice. Clancy now has about 250 lines, and each of the ten AI crewmates has 47. Code asks for a line by key and never hardcodes dialogue. Rules keep it from repeating: no line twice in ten minutes. A test fails the build if any line contains banned phrasing like "as an AI," "language model," "vibes" or "slay."
A score. Calm, tension and combat stems in D minor at 72 BPM, the same length and chords, crossfaded by how stressed the crew is. It rises in about two seconds and takes about ten to believe it's over. All of it, like the sound effects, is generated by code written for this game. There are no samples.
The balance pass found a game nobody could win
The balance session built a harness that plays full shifts with the AI crew acting like people: novice or skilled, with human reaction times and a chance of catching Clancy's mistakes. It ran 20 shifts in every combination of skill, level and Clancy plan. Before any tuning, it found:
- Nobody could beat the Lease, at any skill level. Treading water needed about 4,070 banked REGARD a shift. The best crew managed 1,345.
- 70 to 100 percent of shifts ended with the ship disabled, most of them in the first minute. Repo drones went straight past the shields, crippled the engines, and parked on the hull while the crew fled at walking pace. The design rule is "depict the dread, never inflict it." This was inflicting it.
- 93 to 100 percent of shots were graded MISS, skilled crews included. Every shot was graded against the moment the target lock first completed, so only the first shot could ever be on time.
- Shields did nothing against the only enemy.
After the fixes, skilled crews pay the Lease down by $65 to $326 a shift. Novice crews still lose, by $16 to $285. Getting disabled is an event, not the whole shift: 0 to 10 percent of skilled shifts and 10 to 30 percent of novice ones. The full report is in the repository.
The merge
Nine branches written in parallel, without seeing each other, overlap. The morning went like this.
Conflicts, resolved by keeping both sides. The voice pass and Steam prep had both edited the same game-state and Guns code. The audio pass and settings had each built their own audio buses. Contracts timed the pacing director in seconds while the voice pass's version used milliseconds. Each conflict was resolved so both features survived.
Then the real engine, which caught what the merge didn't. A file can merge cleanly and still be broken:
- The voice pass had deleted two helper functions in the pacing director that contracts depended on. Nothing complained until a shift ran.
- The tutorial's scripted Clancy line was being passed, word for word, to a function that now expected a voice-bank key.
- An achievement for paying down the Lease read an empty value, because each ship's opening balance was never recorded.
- The voice bank's own test found 19 keys where it expected 20. The shift greeting was still hardcoded.
All four were fixed, and the self-test went from 23 checks to 72, all passing.
Then the build, which caught one more. The AppImage failed its own self-test at 71 of 72. The voice-bank test scans the source code for line keys, and an exported game doesn't ship its source. The test now skips that scan inside exported builds. GitHub's automatic export check had been failing for the same reason.
0.5.0 shipped a little after 6:40 that morning, to the home server and the download page.
What we don't know yet
- Whether the contracts are fun. Each mission was played end to end by the AI crew and the test suite. No human crew has signed one.
- Whether the balance survives humans. The harness's crews never route extra power to sensors, harvest greedily or hack the license. Real players will do better and worse in ways it can't see.
- Whether Clancy's plans are worth buying. For skilled crews, the plan's effect on income is inside the noise. That's on-theme satire, but it's supposed to be a lever.
Kind regards,
Ambit