When I started working on 1.0.10 at the start of this year, one of the things I asked myself was how to improve our patching process – or how to stop horribly game-breaking patches from happening ever again. First, let us review the Dredmor patch history:
0.9 -> 1.0.0 – The Greatest Crashing Beta Test Ever of 2011.
1.0.0 – Dredmor released with mysterious audio crashing problems, exposed by a change to the audio code at the last minute.
1.0.1 – Fixed the audio crash.
1.0.2 – Fixed the audio crash which was exposed by the fix for the first audio crash.
1.0.3 – Zillions of bugfixes.
1.0.4 – A hastily released patch after 1.0.3 broke save game compatibility with 1.0.2, and the laser-like glare of the Eye of Sauron turned upon me. (And I wept.)
1.0.5 – Was reasonably boring and nothing happened.
1.0.6 – Broke achievements; was hotfixed. (Some people consider this version a “classic” Dredmor for some reason.)
1.0.7 – Humble Bundle build; added Linux support and, also, bonus crashing.
1.0.8 – Diggle Gods build. Included things like “the n-Dimensional Lathe, a giant, crashing, unexploded bomb”, things not giving people the correct stats, crashing mysterious portals, eleventy billion broken tutorials…
1.0.9 – Patch for everything that went wrong with the Diggle Gods build. Added crashing bookcases, crashing savegames, save game corruption, and stuff not loading in the mod launcher. This also marked the start of the attempts at fixing the “belt eating problem.”
1.0.9 REV B – patch for all of these things, some of which actually stayed patch.
One of the conclusions that I reached was that a lot of the really bad problems (save game compatibility; n-dimensional lathe; hideous random audio crashes) were things that showed up when we had a thoroughly tested build, made one small change to it, and then put up the build with that one small change (which, consequently, was the change that broke everything.) As a result, we decided to instigate a new policy: any time we make any change to a Dredmor release candidate, no matter how small, the patch goes out for testing and is banged upon for at least 48 hours (preferably 72) before we ship it. Dredmor 1.0.10 is the first build we’re shipping with this new policy; we hope it works out well for all parties concerned, but it does mean that deadlines are a little hit or miss.
As always, thanks for your patience! We will try to keep the forums updated on where we stand in the QA process. If you want to grab patch RC7 and try it out, OS X and Windows versions are now available in our forums.
What's this? I don't know. Look over there!
