BUG: NEW: FIXED: Critical Error, duplicate leader ID in Sept 2004 beta.

[Mike of NW8]

Critical Error!

Hi,

Got a "Critical Error" while playing Brandenburg with the latest (September)patch.

"Attempting to create a monarch with a leader ID (30263) that is already used"

Thanks.

 

[unmerged(17489)]

do you play with any mods?

 

[Mike of NW8]

No Mods. Did a fresh installation of 1.00 then added 1.08 and then the patch, which I moved into the EU folder overwriting the old files.

The scenario I was playing was 1419, and the game was somewhere in the 1420s, so very early on.

 

[AndrewT]

I got this myself last night, with a Chinese leader. A text search revealed no such duplicate ID in the files, so I'm afraid it looks like a new bug in the Sept beta. A restart from the previous save went OK and the error did not appear that time.

Did you start this game under this new beta? Mine was started under the previous one.

 

[Mike of NW8]

I used the eu2_108b_5Sep2004.zip patch.

 

[unmerged(17489)]

I got this myself last night, with a Chinese leader. A text search revealed no such duplicate ID in the files, so I'm afraid it looks like a new bug in the Sept beta. A restart from the previous save went OK and the error did not appear that time.

Did you start this game under this new beta? Mine was started under the previous one.

You mean you serched every leader file for that ID and couldnt find it? What about in the save file?

 

[Mike of NW8]

I've replayed a couple of times, cannot replicate the problem.

 

[AndrewT]

Looks like we have two separate problems. Mike, yours is due to a bug in the monarchs.pok file which appears by the correct filename for the first time in the Sept patch. The last two monarchs in it have the same ID #, the one your message reported. I'll check tonight, but I think you'll be OK to just increment it to 30264 on the last monarch in that file. The problem would only occur if Polotsk was independent in the time covered by that last monarch.

Mine, I'm not sure about, I'll have to check in the save file if it happens again. But I suspect it was an artifact of playing a game started under a previous patch.

 

[AndrewT]

Confirmed, you can just replace the second occurrence of 30263 with 30264 and that will fix the problem. Naturally I'll include this fix in my next batch of fixes to Johan. Thanks.