
Documentation written for a machine to read
A model starts every session knowing nothing about the last one, so the documentation is the memory. That changes what belongs in it, and it is rarely a diagram.
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 2 of 2

A model starts every session knowing nothing about the last one, so the documentation is the memory. That changes what belongs in it, and it is rarely a diagram.

Rewriting the pathfinder under an army of wargs meant comparing 18,000 routes against the old one. That only happens if each run starts without approval.

In April the camera stopped looking straight down. What a player got when a canvas RTS was rebuilt on three.js, and what the simulation never noticed.

The original design document describes a two-race game with two columns of stats. It shipped with nine factions, naval warfare and a review of its own weaknesses.

Wood elves fight to a fiddle reel at 145 BPM and dark elves to symphonic metal at 120. Nine factions, 171 tracks, and the difference written down first.