
The tech stack behind a browser RTS
Five stack choices and what each one charged: a physics engine never allowed near the simulation, a renderer whose failure mode is a blank white map, and 1,266 files with no upstream maintainer.
Tag
Development posts tagged working-practice. Tags cut across the categories, so this pulls together work on the same subject from different parts of the game.
17 posts · page 1 of 2

Five stack choices and what each one charged: a physics engine never allowed near the simulation, a renderer whose failure mode is a blank white map, and 1,266 files with no upstream maintainer.

A nine faction RTS with a campaign, built in 140 days by one human who has never read the code and one model that wrote all of it. How that actually works.

Capability pays where a change can be wrong in a way nothing would notice. Sort a week of your own work by what would catch it, and the answer is usually the effort setting rather than the model.

642,530 lines directed by someone who has never opened a file. The plan is the interface, and this is what a plan has to contain to be arguable by a reader who cannot check the code.

The whole map rendered flat white and nothing crashed. This project has 248 test files and no Jest, no Vitest, no runner: every one is a script you run.

Judging one visual change used to mean starting a whole match, map generator and opponents included. A lab loads one thing and holds everything else still.

Three.js reports a broken shader by printing to the console and carrying on, so the map went white with nothing recorded anywhere. This is what changed.

Parallel agents work well on separate files and fail on shared decisions. Three collisions from building this blog, and the brief shape that prevents them.

An eighty second trailer cut from eighteen generated clips, each one seeded with the game's own splash art so the dwarves stayed the game's dwarves.

A dwarf army, a goblin fortress and the ground under both were built the same afternoon by different sessions. What that buys, and the one rule it cost to learn.

Twenty three cheat codes you type into the chat box, a commander who insults you for using them, and a hidden one that exists purely to film the game.

Warships, gyrocopters and steam tanks came back from image-to-3D finished. Anything with legs came back needing every joint placed by hand. One question sorts them before you spend a credit.