[1.07][bug]"remembered"/carriedover units

when starting a new game, I often have the ability to build units I haven't yet researched... and which have the appearance appropriate for a faction i am not leading (but was in a previous game).

 

Most recently however, this took a curious turn.  I had wedded My sovereign to the wandering npc Arussa.  Some time later, in the same game, i found her clone: another npc named Arussa.  The computer apparently didn't know how to deal with this, and assigned clone-arussa the image of a baby in a cradle.

 

Then, in the very next game, using the same custom sovereign, I came across arussa again.  She still had the baby-cradle picture.

 

She also had 135 essence.  as far as i am aware, all wandering recruitable units have 0 essence.  In my previous game, my sovereign had imbued spouse-arussa, so she had a large amount of essence.  It seems for some reason, this had bled over into the new game.

 

screenshots available.

4,434 views 4 replies
Reply #1 Top

Then, in the very next game, using the same custom sovereign, I came across arussa again.  She still had the baby-cradle picture.

She also had 135 essence. as far as i am aware, all wandering recruitable units have 0 essence. In my previous game, my sovereign had imbued spouse-arussa, so she had a large amount of essence. It seems for some reason, this had bled over into the new game.
End of quote

I had something similiar happen.

I played the same custom sovereign in a new game but in my case, the "carried over" character was one of my sovereign's kids.
I think that kid hadn't grown up, yet, in the previous game but not entirely sure.
The name was identical for sure and the fact that she had essence.

She ended up as a wandering, recruitable champion with 15 essence.

 

I hadn't been able to reproduce it, yet, so I was holding off on a report because it might have been bad voodoo, a corrupt sector/pointer on the HDD, or whatever.

Reply #2 Top

Did this happen in a second game in the same session, or had you exited and restarted the program?

Reply #3 Top

Hmm.  I can see that would be useful information; as i recall, the issue with cloning, I believe is same session. However, the error does persist, once it has occurred, through separate sessions.

 

The issue with carryover is separate session (exit and restarted).  it also persists.

 

subsequent new games using different sovereigns will not have the carriedover/bugged npc as before, although a new one may develop.

 

That is, using my OP, in a new game with a different sovereign, arussa is totally normal.  However, under the same situation (clone of the wife), an npc can become bugged - and presumably carried over if i were to start a new game with the second sovereign.

Reply #4 Top

I've had the same thing happen with Sovs as well, Start a new game with a pregen sovereign (magnar a think). Didn't like the starting locale so I exited to main menu and started a new game. Now in the Sov Select screen the is a new custom sovereign with the same stats and description, but a different face. I have replicated this error several times. Also any units you had before starting a new game carry over. Start a game using a custom faction that has the master archer trait, create an archer unit, then start a new game with a non archer faction. You can still build that archer unit from the previous game. Once again I replicated this several times.

In both cases, quitting and restarting the program cleared these "ghosts".