Why does an update "destroy" the saved games?

[Sixtus]

I tried to play a game I saved yesterday and now after the update I can't play it anymore - everybody now has millions of soldiers or negative soldiers in the millions etc. Does every update destroy the saves before?

[Dragster6681]

Not every one does, just the major ones like this that have a big effect on the core game mechanics. If you want to protect saves in the future you can turn off automatic updates.

[Magnus Aurelius, Bright Lord]

iv never had an update destroy my game either so it was quite a shock (lightly speaking). I started a campaign yesterday morning and played it trough the day at a slow pace to make sure everything I did was correct and calculated.

It was a bit of a bummer but its unusual. Iv never had it happened in CK2 and this is the first time I see it happening.

[Plasmatreck]

How do we fix this bug and continue our games?

[Bordric]

Originally posted by Plasmatreck:

How do we fix this bug and continue our games?

If you saved over your old save with the new version you don't. If you didn't save over your old save revert the game to the last version.

Turn off auto updates on games and take control that will fix it in the future.

CKIII Had a major upgrade and overhaul to the systems you will need to start over.

[AshWarden]

Same for me armies in the millions and two now fighting it out.. (forever?). Also my army unused in the millions and used mercenaries and Knights Templar the same! Ruined my game in progress with hours on the clock. Can access old saves but what the point re-loading causes the same issues. A fix please Paradox.

[Bordric]

Originally posted by AshWarden:

Same for me armies in the millions and two now fighting it out.. (forever?). Also my army unused in the millions and used mercenaries and Knights Templar the same! Ruined my game in progress with hours on the clock. Can access old saves but what the point re-loading causes the same issues. A fix please Paradox.

It is not going to be fixed. Roll the game back to the last version, that is the fix if you have no corrupted your saves.

[CrUsHeR]

To be fair, the DLC was already announced some 7 months back.

Even if only occasionally seeing the Steam News when clicking on the game, everyone must have had at least the opportunity to see the release date several weeks / months prior.

And you know that updates always break the saves in this type of strategy game. Backwards compatibility has no priority. Basically you would have to write an additional savegame conversion script for every incompatible change, which would be obsolete a few days after the update for 99% of all players.

[Nakai]

not supporting legacy saves on auto-update is pretty dumb

[omaewa]

Originally posted by Bordric:

Originally posted by Plasmatreck:

How do we fix this bug and continue our games?

If you saved over your old save with the new version you don't. If you didn't save over your old save revert the game to the last version.

Turn off auto updates on games and take control that will fix it in the future.

CKIII Had a major upgrade and overhaul to the systems you will need to start over.

You are substituting concepts.

Why are you pretending that a very specific bug: an error with millions of soldiers - is a consequence of radical changes in the game mechanics?

Please explain to me, what specific changes in the mechanics of managing professional troops led to such a bug? As part of the add-on, landless characters, new mechanics of intrigue, a new form of government were added.

But professional troops remained more or less the same.

This is just the most ordinary, most banal bug. I do not see any prerequisites for such strange changes to occur when updating the game.

Why do you, as well as other people here, pretend that this is normal, and was intended this way?

[Bordric]

Originally posted by omaewa:

Originally posted by Bordric:

If you saved over your old save with the new version you don't. If you didn't save over your old save revert the game to the last version.

Turn off auto updates on games and take control that will fix it in the future.

CKIII Had a major upgrade and overhaul to the systems you will need to start over.

You are substituting concepts.

Why are you pretending that a very specific bug: an error with millions of soldiers - is a consequence of radical changes in the game mechanics?

Please explain to me, what specific changes in the mechanics of managing professional troops led to such a bug? As part of the add-on, landless characters, new mechanics of intrigue, a new form of government were added.

But professional troops remained more or less the same.

This is just the most ordinary, most banal bug. I do not see any prerequisites for such strange changes to occur when updating the game.

Why do you, as well as other people here, pretend that this is normal, and was intended this way?

Because logic and intelligent deduction. It is very normal. It is not a bug it is a redesign of the armies and mechanics. Hence using intelligence and logic.

If you use an old save with the new version it is going to be bugged. Logically.

[omaewa]

Originally posted by Bordric:

Originally posted by omaewa:

You are substituting concepts.

Why are you pretending that a very specific bug: an error with millions of soldiers - is a consequence of radical changes in the game mechanics?

Please explain to me, what specific changes in the mechanics of managing professional troops led to such a bug? As part of the add-on, landless characters, new mechanics of intrigue, a new form of government were added.

But professional troops remained more or less the same.

This is just the most ordinary, most banal bug. I do not see any prerequisites for such strange changes to occur when updating the game.

Why do you, as well as other people here, pretend that this is normal, and was intended this way?

Because logic and intelligent deduction. It is very normal. It is not a bug it is a redesign of the armies and mechanics. Hence using intelligence and logic.

If you use an old save with the new version it is going to be bugged. Logically.

Once again.

1. What exactly was changed as part of the update to the mechanics of managing professional troops?

2. If these changes were made, how did they lead to the troops turning into armies of millions? What is it, exactly? A new function in the code that calculates the number of soldiers in regiments?

3. If these changes were made, and if they affected the mechanics of managing professional troops, was the bug with a million-strong army really an inevitable consequence of the transition from the previous version to the new one, or is it a regular bug?

[jerrypocalypse]

Originally posted by Nakai:

not supporting legacy saves on auto-update is pretty dumb

Legacy saves are supported via the ability to roll back the update using Steam betas.

[VBigB]

Originally posted by omaewa:

Originally posted by Bordric:

Because logic and intelligent deduction. It is very normal. It is not a bug it is a redesign of the armies and mechanics. Hence using intelligence and logic.

If you use an old save with the new version it is going to be bugged. Logically.

Once again.

1. What exactly was changed as part of the update to the mechanics of managing professional troops?

2. If these changes were made, how did they lead to the troops turning into armies of millions? What is it, exactly? A new function in the code that calculates the number of soldiers in regiments?

3. If these changes were made, and if they affected the mechanics of managing professional troops, was the bug with a million-strong army really an inevitable consequence of the transition from the previous version to the new one, or is it a regular bug?

I’m not going to regurgitate the patch notes (you can read them yourself) but tons of things were changed that would affect troop calculation including:
- the entire way that landless troops are handled and associated cap bonuses
- cultural tradition now providing flat bonuses instead of percentage bonuses
- building bonuses changing
- many new men at arms
- changes to existing men at arms
- plus many many more
So the fact that this is bugged for existing saves is not surprising in the least and even if this were to be fixed with so many other fundamental changes to the game it would be something that would break existing saves.

[omaewa]

Originally posted by VBigB:

I’m not going to regurgitate the patch notes (you can read them yourself) but tons of things were changed that would affect troop calculation including:
- the entire way that landless troops are handled and associated cap bonuses
- cultural tradition now providing flat bonuses instead of percentage bonuses
- building bonuses changing
- many new men at arms
- changes to existing men at arms
- plus many many more
So the fact that this is bugged for existing saves is not surprising in the least and even if this were to be fixed with so many other fundamental changes to the game it would be something that would break existing saves.

I could agree with this if it was a critical issue that could not be fixed. However, the irony is that it is enough to assemble/change the number of professional regiments to fix this bug and restore the normal number.

This means only one thing - the new mechanics of managing professional troops CAN work correctly with saves from the previous version of the game.

I am a developer myself, but I am not familiar with the specifics of CK3 development. In my opinion, this problem could be solved either by a simple data migration script, or by additional checking in the function for processing the number of professional regiments and the modifiers applied to them.

[Bordric]

Originally posted by omaewa:

Originally posted by Bordric:

Because logic and intelligent deduction. It is very normal. It is not a bug it is a redesign of the armies and mechanics. Hence using intelligence and logic.

If you use an old save with the new version it is going to be bugged. Logically.

Once again.

1. What exactly was changed as part of the update to the mechanics of managing professional troops?

2. If these changes were made, how did they lead to the troops turning into armies of millions? What is it, exactly? A new function in the code that calculates the number of soldiers in regiments?

3. If these changes were made, and if they affected the mechanics of managing professional troops, was the bug with a million-strong army really an inevitable consequence of the transition from the previous version to the new one, or is it a regular bug?

And again using intelligence you can go read what changed. I am not going to write it out for you. These changes were made it is not a theory.

If you want the technical reason go ask the devs. Nothing new here for anyone who has played these games before. Major overhaul is new code. The fix is so simple I don't understand your compliant. You have no reason to have a problem with a major update. Its all on you.