Log in

View Full Version : Strange traits bug



option
06-09-2009, 02:51
I recently decided to try to install the Alexander EB minimod to my comp, but I noticed it really screwed up my characters' traits (changing their races, making them all client rulers, giving them other factions' victory conditions, etc.). I had made backups of the save game files prior to attempting this installation, so I did a complete reinstall of EB and copied the backup save files into the right directory. They're a lot closer to what they were before now (e.g. my Molossos characters have changed to Chaons instead of becoming Sogdianos), but a lot of the traits are still wrong, such as Pereginesis traits for regions I haven't conquered, all my FMs having the 'client ruler' trait, and the race issue. Is there any hope of restoring my game, or is it as good as lost now?

EDIT: I also just noticed that the minimap shows me (Epeiros) as controlling Numidia and Carthage as owning Crete, when it's the other way around.

Aemilius Paulus
06-09-2009, 03:47
Exact same happened to me when I did Alexander switch, but thankfully, that only happened to the old campaign that I quit, and I waited for ALEX to start my new one. So my new one did not get messed up. Anyway, I do believe this happened to both of us because you used ALEX 1.2 whereas you have EB 1.1.

At least that was my case. And the trait problems are identical to not only mine but to the problems that arise from playing 1.1 games on 1.2. Anyway, I got the exact same ethnicity switch, the Pereginesis traits and the client ruler thing. In my romani campaign, it was even worse, with almost all the traits messed up, and new ones such as "Slain by Sabaens" or the Sweboz chieftain trait (no idea how to spell it).

option
06-09-2009, 05:41
Yeah, a lot of them have the 'Sabaen Father Avenged' trait or whatever it is, too. Oh well.

Cute Wolf
06-09-2009, 09:33
I think that "Slain" traits are gotten if u get a CTD, reload EB, and then load a different savegame file... not only by moving 1.1 to 1.2 ( repeat... you play a campaign, then it got CTD, and then you reload EB and play diffrent savegame

This was in 1.2
I once had my Baktrian FM trait "Slain by Karthadastim", and their sons, who just recently comes of age get the trait "Avanger against Karthadastim" (Their fathers is still alive!!!)... I know that was a bug, but because the game doesn't have any error except this, I teleport those kids on Africa, and start killing some unfortunate Karthadast FMs... slash and burn some of their cities... (including Karthadast and Atiqa of course...) and then teleport back to India... at least they got "Father Avenged" trait that is still ok...

bovi
06-09-2009, 17:30
The "slain" traits, and other oddities, are caused by loading an old savegame with a non-savegame compatible change to the game files. Such as adding a trait or installing certain submods.

Cute Wolf
06-09-2009, 17:59
@ bovi... what submod? wait... did u mean changing the values on export_descr_VnVs (even without messing the slain trait, could get all way wrong? (confused)

bovi
06-10-2009, 00:57
Add or remove any trait, and they all go 52 pickup in games started without that change.

Atraphoenix
06-10-2009, 08:21
Check this, my favourite. :laugh4:
This screen is taken from one campaign that I did not restart a new one after I'd changed the ancillary files.https://img7.imageshack.us/img7/8378/bugbae.jpg
Ancillaries are as sensitive as traits.
Unfortunately, I could not find the picture that Arshak/Arsaces himself was a legion Legate..

Aemilius Paulus
06-10-2009, 18:02
Wow. I never knew this bug happened to ancillaries... Better check that Romani campaign quick for more lulz!!

Tellos Athenaios
06-10-2009, 20:38
There is no bug. For an analogy: this is as if you changed the kernel (core part responsible for managing everything in the OS) of your operating system to a version which is not backwards compatible on a binary level, then expect your old hardware drivers to `just work'. They won't, they can't: they've been built against the older kernel and expect the older binaries.

That is what Save Game compatible means: your save game is `built' against the data files. Changing the way the data behaves breaks your old save games.