What broke this week.
A build log goes out with every drop: what got made, what broke, what the actual root cause turned out to be, and what got cut. Written by the person who wrote the line that shipped it.
No posts yet.
The first build log ships with Drop 003. It won't be a changelog — the interesting half of a week is always the thing that turned out to be wrong for a reason nobody would have guessed, and that's the half most studios don't publish.
What goes in one
Every post answers the same four questions, because they're the four that are actually worth reading:
- What got built that hadn't existed before.
- What broke, and the real root cause — the mechanism, not
the symptom. "A bug in the pathfinder" tells you nothing. "The route was
re-planned every tick for every people sitting in
Preparing, and a people can wait there for weeks while its council argues" tells you something. - What got cut, and why. Usually the most-read part, because it's the part nobody else publishes.
- What was surprising — behaviour that emerged from the rules rather than being designed.
If a week ends with an open bug still unexplained, the post says so. A build log that never admits an unsolved problem isn't a build log.