Developer notes
-
Three features we built and took out again
Fleet Command, capturing enemy ships and a reward formula that measured the wrong thing.
-
Four bugs worth remembering
A monster that could not die, a rival who won the wrong fight, and two more.
-
Making a campaign you can follow
Players were finishing the story without knowing what it was. What we changed.
-
How we know a change did not change the game
93 scripted battles, hashed and compared on every release, and the damage steps whose order is tested.
-
Taking an engine out of a running game
Three stages of moving the clock, input, sound and 3D stage into a shared engine without changing a pixel.
-
Adding a civilization with ships we did not draw
Eleven CC0 spaceships converted to our scale and axes, and the bug no test could see.
-
Why the battles are flat
A 3D picture on a flat battlefield: why Cosmic Starship is 2.5D and what that costs and buys.
-
What a crude bot says about 57 ships
Every capital flown by the same bot in the same fight: what survived longest, and what the test cannot tell us.
-
Making a 3D Browser Game With three.js and No Build Step: How Cosmic Starship Is Organized
Plain ES modules, vendored three.js r180, one-URL-per-module and two loading bugs we shipped and fixed.