• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Schnee0

Duke
20 Badges
Sep 12, 2003
620
0
  • 500k Club
  • Crusader Kings III
  • Crusader Kings II: Holy Fury
  • Crusader Kings II: Jade Dragon
  • Crusader Kings II: Monks and Mystics
  • Crusader Kings II: Reapers Due
  • Crusader Kings II: Conclave
  • Crusader Kings II: Horse Lords
  • Crusader Kings II: Way of Life
  • Hearts of Iron II: Beta
  • Crusader Kings II
  • Europa Universalis III Complete
  • Crusader Kings II: Sword of Islam
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Republic
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: Charlemagne
Using the -2 value for the "which" variable for rebel creation makes the game crash if the game is saved while the rebels are still alive.

Example:
command = { type = revolt which = -2 where = -1 }

If that is activated you have guranteed game crashing during either autosaves or manual saves.

Here are some events that can cause this problem:
The political_events.txt event 22010
"Minority Insurrection" - it uses the -2 value

Spain.txt event 7706
"Nationalism in the Philippines" - option B has 3 revolt spawns with the value of -2, I trigged the event as Spain, and kaboom it crashes on save.
 
Upvote 0
Schmeeß said:
Using the -2 value for the "which" variable for rebel creation makes the game crash if the game is saved while the rebels are still alive.

Example:
command = { type = revolt which = -2 where = -1 }

Also happened in a VIP event.

Good finding Schmeeß! Thumbs Up.