Category
The standalone tools built to look at one system at a time, and the tests that keep them honest.
6 posts
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.
Sixty four spells were coming out as the wrong kind of magic, and nothing had gone wrong. Two pages exist to catch the bugs that look completely fine.
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.
Losing a multiplayer match to a battle your opponent never fought. This is the check that stops it, and the deliberate bug that proves the check works.
