The workbench
Devlog
Sessions, crashes, and the occasional admission that last week's explanation was wrong. Written as it happened.
A bot that plays while we sleep
Finding a regression on a Friday night with a friend in the headset is the most expensive way to find a regression.
Hips cross the wire
VRIK gives you a body. Until this week your friend could not see most of it move. Three joints later, they can.
Reading a crash without a debugger
The launcher replaces the game executable, so a crash dump shows one 90 MB module with the game's code and ours inside it. Here is how we tell them apart.
The timeout that never happened
A whole night's fixes were built on a reading of a log that turned out to be wrong. The fixes stand; the story behind them does not.
What is next, and what is broken
This is the real list, in the real order. Nothing on it is marked done because it was written down; things come off it when the people playing stop reporting them.