Every change to the game goes through an automatic check before it lands. Early on, the check ran everything: all 72 test setups, for every batch of changes, however small. A one-line fix to a shadow waited for the same half hour of tests as a rebuild of the terrain.
On September 26 the first answer was to make that check faster. It now runs only the test setups a change actually reaches, compiles eight at a time on a second computer so each batch is checked about twice as fast, and lets a change land as soon as what it touched is proven. A second problem was failure that looked like slowness. The second computer sometimes hung while its results were being read, and a hang threw away the whole batch. Twice in one night that cost about 45 minutes each time, so the check now asks again, up to four times, and no longer fails a batch just because the second computer is slow to answer.
Late the same day came a different answer: stop running the tests. The reasoning was plain. The automated runs took most of the time and most of the effort, and a game is judged by playing it. So a change now lands when the game builds, and no automated test case runs on the way in. A build that fails refuses the batch, and when a build will not start the game, the first move is to go back to the last good one.
The record shows how complete the switch was. Of the 270 batches that landed between September 25 and October 3, the first 27 ran the full set of tests. The other 243, every one after that decision, ran only the build.
A green build therefore means one thing: the code compiled. It does not mean the game plays correctly, which is why each change ships with a short list of things to try and why the check that matters most is someone playing it. The trade buys pace, and the cost shows up in stories like the one about the Create World button. Nothing in this stretch changes what you see in the game; it changes how fast the next change can arrive.
A related repair landed on October 3: the game can be built as a standalone packaged copy again, which it could not since mid-September. Four calls that only work in the editor were guarded, and an editor plugin no longer pulls a second copy of its database library into the packaged program. That copy is for friends to run. It is not a public download.
