Slitherine

I created a mod with an older version of the game, and it doesn't work anymore. My current version of the game is the last one, with Red Steel and Red Storm DLCs.

In the editor, countries and units appear normally, except that all units are listed as "unavailable" despite the year.

In the game, I can normally launch scenarios and everything seems fine, but I can't click the units, and their stats are all messed up.

It seems a problem within the units.csv file, but I can't see any problem within it.

If anyone can look at it:

https://www.dropbox.com/sh/1zymy12osjq4 ... _fvva?dl=0

Some of our experienced mod-guys will hopefully chime in, but...
Usually it will be safest to use the new units file (and other files you've modded) and update it with your edited stats.
I've seen several similar posts over the years with mods being 'broken' after an official update.

I tried copypasting the lines of the modded file in the updated "Units" file and deleting everything else, but nothing changed...

Even GabeKnight's mod, kind of designed to be working with all official and custom campaigns/scenarios, is having issues now.
This according to the thread below.

I took a quick look yesterday, but could not find anything obvious either.
(Erik, no problems with my mod, BTW.)

I solved the issue: there were changes in the Effects.txt and EffectSequences.txt. I fixed a couple things and everything went smoothly.

I had two scenarios already made, but they are dead now. Probably changing things in units.csv made the game not like them anymore.

I may cry a little.

To be honest I don't understand why you had to change anything inside your mod with the game's update.

You're using unique unit-IDs outside of OoB's vanilla roster. In my opinion your mod only needs updating if you need any units/stats/commanders/etc. that were introduced with the current DLC. Otherwise it should continue working after a game update...

GabeKnight wrote: ↑Wed Sep 23, 2020 1:46 pm To be honest I don't understand why you had to change anything inside your mod with the game's update.

You're using unique unit-IDs outside of OoB's vanilla roster. In my opinion your mod only needs updating if you need any units/stats/commanders/etc. that were introduced with the current DLC. Otherwise it should continue working after a game update...

It was an old version (8.1) in which I "barred off" some line in EffectSequences.txt with "//". Apparently, that method doesn't work anymore so it gave out several errors. Same with Effects.txt. At least, that's how I solved the issue, so there's that.

BTW last night everything was tits up again; this time I solved the issue by taking the vanilla units.cvs, deleting everything and copypasting the lines from my modded .csv. I have absolutely no idea what was wrong, but after a multitude of checks that's what solved the issue... I also managed to recover the scenarios I made with the old version so thumbs up!

With the mod, with each update you have to start all over again

At least not having the Steam version I can decide whetever I want to update or not.

StuccoFresco wrote: ↑Thu Sep 24, 2020 3:54 pm At least not having the Steam version I can decide whetever I want to update or not.

I still play with the latest version and I installed both Steam and Slitherine versions

terminator wrote: ↑Thu Sep 24, 2020 2:06 pm With the mod, with each update you have to start all over again

Not "all over again", but you have to implement the changes between versions.

And that's only true for "player's mods", like mine for example. Any mod that has been designed for specific scen or campaign purposes, like the Spanish Civil War mod or Korean War mod, do NOT need to be updated with new vanilla content. Unless there's some MAJOR change in the game's data file system, like the units.csv file suddenly becoming a .txt file or something...