[http://sourceforge.net/p/ufoai/bugs/2521 Item 2521] imported from sourceforge.net tracker on 2013-01-28 19:39:33

Might be related to bug #2983569, though that was before the savegame_break merge.

System: Win7 Pro 64-bit. If needed, could test on debian squeeze x86_64.
Game: trunk rev 30000 windows_debug and windows builds. First ocurred May 15, don't remember the revision.

I'll upload 2 saves: one seems to be the definite starting point which leads to the condition for the bug to occur, though that save is loadable. Continuing that game has always created the situation which has occurred every time the bug did. In detail:
1. load slot6
2. play a while
3. ufo #15 appears, attacks base PHALANX HQ, saves after that unloadable.
4. sometimes the attack "just happens", no UFO appears.
5. slot4 is such an unloadable save.
===== Comments Ported from Sourceforge =====

====== tanelk (2010-05-16 09:37:18) ======

unloadable saves and ufoconsole.log
====== geever (2010-05-16 16:58:55) ======

This must be the same as #3002351. I've fixed that today.

-geever
====== edirr (2010-05-16 20:15:20) ======

Even after the fix, the savegames stay broken and you need to load an earlier one. Currently running 30011.
====== tanelk (2010-05-17 08:49:50) ======

Confirmed duplicate to 3002351. Seems that geever fixed it, attack on the base did not cause the next save to become unloadable.

And yes, once saves are corrupted, they apparently won't work. Maybe edit them?

@geever : Prompt fix, how on earth did you figure out that the savesystem wasn't helping the base attack handling anymore? Ah, the intricacies of complex coding, must've been all the mileage you've done on the project :)

Comparing the 2 saves I found an odd occurrence: all the "researchable" statuses of starting weapons (ones you get from the start) in the working save were 1, but 0 in the unloadable. Relevance?