Craterfall
The artillery games I grew up with, rebuilt as a roguelike where every act arrives in a different art style.
- 3
- acts to the final boss
- 8
- visual styles, all drawn by code
- 0
- frameworks or third-party assets
- 1
- file. The whole game opens with a double-click
01Summary
Craterfall is a deck-building artillery roguelike. You aim and fire real ballistic shells across terrain that can be destroyed, spend energy on cards from your hand, read what each enemy intends to do next, and fight through three acts.
Everything is generated: terrain, enemies, art and sound. The same battle can look like neon, ink, papercraft, a blueprint or film noir.
02Why I built it
My gamertag has been JoeArmageddon for as long as I have had one. I started this as a rebuild of the turn-based tank games I played as a child, mostly to see whether I could. Then I read the history of the genre and it turned into a design of its own.
03How it works
- Step 1
Research
A written history of the genre and what made it last.
- Step 2
Rebuild
Ballistics, wind and destructible terrain first. The feel of the shot before anything else.
- Step 3
Redesign
Cards and energy. Draw five, spend three, play as many as you can afford.
- Step 4
Stylise
Visual styles as interchangeable doctrines that re-skin sky, ground, tanks, shells and interface.
- Step 5
Test
Bots that play whole runs without a screen, a combat soak, and a check that all game data cross-references.
- Step 6
Ship
One self-contained page, packaged for the web.
04Decisions
| Decision | Reason |
|---|---|
| Several shots per turn, gated by energy | It makes a turn a small puzzle. It also made a fast-forward control mandatory. |
| Two-player mode retired | Removing it took a whole mode out of the test matrix and let the enemy AI become the focus. |
| Styles dissolve between acts | One generic dissolve tinted by the incoming style, in place of a bespoke transition for every pair. |
| Desktop first | Keyboard and mouse are the release gate. Touch is best effort. |
05What broke
- Modules do not load from a file opened directly in most browsers, which is why the single-file build exists.
- Repainting terrain when the style changes is expensive, so styles change only at act boundaries.
06What is next
A public release page.