Something definitely went wrong - we're still trying to figure out what as we haven't found the cause yet, but it's unfortunately easy to see how it slipped through: . I imagine that nobody at QA caught it (nb over 4 different companies) because they rarely overwrite their savegames and always work in a circular fashion (svg1,svg2...svg20,svg1 etc...) to be able to backtrack. Since it isn't always a problem, loading a previous savegame won't necessarily have flagged the bug, and that way it would've passed through. No excuse of course and there's been a lot of cursing going on over here
