Hey, so with the new automated -save in 6.54 version, all my new codes are unavalaiable, but the problem, it's that now, even my old saved codes are unavailable....
i also got a crash problem, it happenned only once so maybe it's on me, but it never did this before, i think it's good to signal aswell(no screens shots for this sorry)
If you need anothers informations tell me, 1st bug report sorry if it's not perfect...
Thx for answering, i tried many times, with all my codes, and no.. i don' t have any whitespace ^^ , i think that making the autosave an option for the player coul be a good idea(i don't know if it's hard to do or not.. )
I'm going to try with a totally blank new code, started from rank 0 but in 6.53, then coming back ino 6.54 and see if it still reproduce ^^
So, after trying to reproduce the bug, didnt work, the code load perfectly fine, i tink i just got unlucky... gonna rerank, for the third time xD
well yes obviously ^^, but i can't help you with that , i have no idea how it works so... i was only rank 12 anyway, the only thing that make me sad is that the bug happenned just after i saw all the cool new heroes xD, i'll have to wait even more lol
i tried aaaaaaall my codes(10-12) from the rank 1 to rank 12(i deelted some, but not all) and not any of these worked, so i have to start from the begining ^^
yup, you used the right words ^^, all my codes are dead :'( , the only really things that i regreat is the virus.. i don't understand how to get it, and that's a total newbie random player on eurobattle who gave it to me while he didn't even know how he got it xD
Take the code from your screen(eg. my code was -load T54X-98PQ-X08J), not from the Fortress Codes folder. Either write down the code on a piece of paper or something. Or screenshot it. When the next game starts, get your code from the piece of paper you wrote it down on and type it into the game/take the code from your screenshot folder and type in down in the game.
Quote my post if you are not sure of my explanation.
Edited by We_are_A<-- MY NAME, 06 September 2015 - 06:53 AM.
I think the chain of corrupting code-files goes somehow like this:
Say, you have the following codes in your fortress codes -folder.
Nick(Rank 4 EXP 11).txt
Nick(Rank 6 EXP 42).txt
NIck(Rank 7 EXP 29).txt
You go to the game, playing this 6.54 version with autosaves for the first time. -Load rank 7 code, everything works correctly and you keep playing. But once you make the load, game starts making these auto save-files, was it every 5 min?.. So, you prob don't get any exp during the first 5 min, and then game overwrites the most recent file you had, the "Nick(Rank 7 EXP 29).txt". After some time, you've beaten some bosses and you find more autosaves Nick(Rank 7 EXP 36).txt, Nick(Rank 7 EXP 42).txt and so on. But those are probably also corrupted.
After all, the result is that you have just lost your most recent save-file. If THIS happend, you should backup your code from the NEXT RECENT file, in this case it would be "Nick(Rank 6 EXP 42).txt", before using it in the game. Name it differently so game wont overwrite it!
I had deleted my old save-files, only had lvl50, exp 99, which was the cap on older versions. This happened to me, but We_Are_A gave a nice idea of looking up for a recent replays (contest participation, etc..) and I DID find the same code from the replay and it worked again like a charm, yey . Thanks man
If you guys have huge list of codes that you're not sure which works and which doesn't and you don't dare to try (in fear of getting that corrupted too), go to battle.net, make private custom game 6.53 (!!!) and there you can find out, which code is the most RECENT that WORKS. BACKUP THAT!! and play with that code untill next version is here
GJ fixing it btw. Wouldn't it still be nice, if the game never overwrote the most recent loadcode-file? 1 suggestion is to put 1 extra condition to check before creating new autosave-file
I have no idea how jazz works but developers probably gets the idea from the following example:
// Every 5 min timed event...
if ((playerCurrentExp > playerExpWhenLoaded) || newAchievementsSinceLastAutoSave || infectedWithVirus)
{ //progress towards creating savefile... }
else
{ //no need to create, cause no progress since -load }
endif
The idea is to not even start writing those save-files (with certain time cycle) untill player gains progress by exp or achievement, virus could also trigger that. Well, just a suggestion
// Every 5 min timed event... if((playerCurrentExp > playerExpWhenLoaded)|| newAchievementsSinceLastAutoSave || infectedWithVirus) {//progress towards creating savefile... } else {//no need to create, cause no progress since -load } endif
i am pretty sure it already does work like this(at least for the playerCurrentExp > playerExpWhenLoaded ) because when i had 50 exp codes(it's all 30secs) and then when i did another game, it started loading only after 50 exp on the same rank, i don't think that the problem is on this code part, it's more on the -load part, because, the code is perfectly saving, there is a corruption somewhere, but i honestly don't think it's in this part of the process, but just notice that my programing skills are not goods at all, i only do know some bascis, so.. ^^, anyway, thx for the "solution" to this bug, even if i already lost all xD, i pref wait for 4.55,
It's just so weird that code copied from same codefile, first works and then next round it doesn't work Would be weird if "the -load" worked so differently every round. Maybe it needs more testing
the problem is autosave. period. how come i explain this 10 times and ppl still need to make 3 threads for it..
Also, for reference KeXi-s explanation is spot on.
// Every 5 min timed event...
if ((playerCurrentExp > playerExpWhenLoaded) || newAchievementsSinceLastAutoSave || infectedWithVirus)
{ //progress towards creating savefile... }
else
{ //no need to create, cause no progress since -load }
endif
i am pretty sure it already does work like this(at least for the playerCurrentExp > playerExpWhenLoaded ) because when i had 50 exp codes(it's all 30secs) and then when i did another game, it started loading only after 50 exp on the same rank, i don't think that the problem is on this code part, it's more on the -load part, because, the code is perfectly saving, there is a corruption somewhere, but i honestly don't think it's in this part of the process, but just notice that my programing skills are not goods at all, i only do know some bascis, so.. ^^, anyway, thx for the "solution" to this bug, even if i already lost all xD, i pref wait for 4.55,
GL to programmers to fix this bug
i wish we had put that check in indeed.. for experience it would def have saved the day, however achievements are a bit tricky.. they are an arcane blob of global state with states that exclude eachother etc if done inproperly it might backfire. so given the testing found no issues we found no need for it at the time.
i guess the fix for that is to coonvince nevo to let the map go round more freely so more ppl have a chance to find the bugs..
the problem is autosave. period. how come i explain this 10 times and ppl still need to make 3 threads for it..
in this particular 2-2 last responds, i think it was more for discuss, sorry if it did bother you
i wish we had put that check in indeed.. for experience it would def have saved the day, however achievements are a bit tricky.. they are an arcane blob of global state with states that exclude eachother etc if done inproperly it might backfire. so given the testing found no issues we found no need for it at the time.
lol ok, tought it was alrezdy in, saw it fixed anyway, let's close the discuss
This topic is locked
1.png 465.15KB
4 downloads
, i have no idea how it works so... i was only rank 12 anyway, the only thing that make me sad is that the bug happenned just after i saw all the cool new heroes xD, i'll have to wait even more lol
very hard to up rank 50 !
. Thanks man 
1 suggestion is to put 1 extra condition to check before creating new autosave-file
Would be weird if "the -load" worked so differently every round. Maybe it needs more testing 
