How to continue a save game since the 28Apr 2K patch?

sparkuss

Chieftain
Joined
Aug 9, 2003
Messages
44
Sorry, I searched for previous patch release threads and found only the one about clearing the caches that will likely break an older save.

So, when Steam auto applies a 2K patch, does that mean they have overridden the balance and UOP files? Do I need to pull out them out and reapply them over top? Will that break the save as well?

Or is the mod reapplied over any new 2K patch every time I setup a new game or load a previous save? And just wait for the 2K patch to be reviewed and incorporated into an update?

Basically, is my last save from yesterday actually playing the same rules anymore or is it totally unknown now that Thal's Combined is balancing/fixing against new data.
 
Thanks,

It's not a game breaker, I'm still just learning CIV5 from IV. More I was wondering how the process works and what the procedure should be going forward as 2K updates the game. I've never had a purely steam game before with mods, I'm used to having control over when I apply game updates along with my mods.

So basically is Thal's only overwriting the base files at each instance of a new game, and only when enabled and applied at setup, or is it making permanent changes to the base files for all future games including vanilla?
 
I continued my saved game from the 28 beta, and its still working. The game has gotten very slow though, I don't know if that is a mod conflict or the new patch has turned the game into glue again.
 
Thanks,

It's not a game breaker, I'm still just learning CIV5 from IV. More I was wondering how the process works and what the procedure should be going forward as 2K updates the game. I've never had a purely steam game before with mods, I'm used to having control over when I apply game updates along with my mods.

So basically is Thal's only overwriting the base files at each instance of a new game, and only when enabled and applied at setup, or is it making permanent changes to the base files for all future games including vanilla?

Mods overlay the game files and don't change or overwrite any of the core data of the game. When mods are enabled is at the single player/load game menu after you select which mods are enabled, so there's nothing to worry about.:)

It's probably a good idea to delete the cache and ModUserData files, but that may break your save. Look at the Bug Reporting thread in the Beta and Bugs subforum for info on how to do this if you don't know how.
 
I continued my saved game from the 28 beta, and its still working. The game has gotten very slow though, I don't know if that is a mod conflict or the new patch has turned the game into glue again.

I'm seeing the same thing. I also noticed that the Ship of the Line (English UU, correct?) shows up as an option in the city build queue; this playing as the Incas. Did the patch change some units around? I didn't see anything about that in the patch notes.
 
I've updated TBC to be compatible with the patch (download here), and to my surprise I found we can in fact continue existing savegames. I was able to load up my current game without problems (after clearing the cache as usual).

This was going from 7.0b23 before patch to 7.0b24 after patch. It probably wouldn't work if you were going from v6.9 to 7.0.
 
I've updated TBC to be compatible with the patch (download here), and to my surprise I found we can in fact continue existing savegames. I was able to load up my current game without problems (after clearing the cache as usual).

This was going from 7.0b23 before patch to 7.0b24 after patch. It probably wouldn't work if you were going from v6.9 to 7.0.

Playing with b22, the switch created no problems. I'll move on to b24 later today or tomorrow. But all in all 7.0 is looking very solid. Just because we're considering other changes (India, etc) doesn't mean a version can't be released.
 
They changed how denouncements work, it has a confirmation box now. :)

The majority of incompatibilities will be UI stuff like that which just silently fails when used with the old files, that's where the b24 updates are.
 
The diplomacy screen's actions are contained within DiscussionDialog.lua, with an xml file for layout. Combined, these handle the buttons and what they do.

In the patch the effect of the "denounce" button changed to include confirmation. Part of that was in the layout file (setting up the new confirmation box), and the layout file is not included in this mod, so it automatically updated with the patch. The other part is in the lua file, which is included in this mod and I updated manually in b24. Without that lua update, the two parts don't match.

Basically, until updated it's formatted to have the box but not told how to use it. There's dozens of similar things I updated when merging the patch changes into the mod this morning, and since save files appear to be compatible, I'd recommend testing out b24 to see if it works with your save.
 
The diplomacy screen's actions are contained within DiscussionDialog.lua, with an xml file for layout. Combined, these handle the buttons and what they do.

In the patch the effect of the "denounce" button changed to include confirmation. Part of that was in the layout file (setting up the new confirmation box), and the layout file is not included in this mod, so it automatically updated with the patch. The other part is in the lua file, which is included in this mod and I updated manually in b24. Without that lua update, the two parts don't match.

Basically, until updated it's formatted to have the box but not told how to use it. There's dozens of similar things I updated when merging the patch changes into the mod this morning, and since save files appear to be compatible, I'd recommend testing out b24 to see if it works with your save.

Thanks, Thal. I'm playing with b24, but I may not have deleted all the caches, etc. So I'll confirm this in my next game.
 
Lua files are typically what stick around in the cache, my guess is they're compiled and then stored. XML doesn't seem to have that issue since it's translated to database operations which are probably executed only on-demand.
 
Back
Top Bottom