• 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.

invertigo2004

Captain
90 Badges
Jan 28, 2005
429
3
  • Europa Universalis IV: Mare Nostrum
  • Cities: Skylines
  • Cities: Skylines Deluxe Edition
  • Crusader Kings II: Holy Knight (pre-order)
  • Europa Universalis IV: El Dorado
  • Crusader Kings II: Way of Life
  • Pillars of Eternity
  • Europa Universalis IV: Common Sense
  • Crusader Kings II: Horse Lords
  • Cities: Skylines - After Dark
  • Europa Universalis IV: Cossacks
  • Crusader Kings II: Conclave
  • Cities: Skylines - Snowfall
  • 500k Club
  • Stellaris
  • Stellaris: Galaxy Edition
  • Stellaris Sign-up
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Colonel
  • Crusader Kings II: Reapers Due
  • Europa Universalis IV: Rights of Man
  • Tyranny: Archon Edition
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Cities: Skylines - Natural Disasters
  • Stellaris: Necroids
  • Europa Universalis IV: Conquest of Paradise
  • Crusader Kings II: Charlemagne
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Republic
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sword of Islam
  • Europa Universalis III
  • Divine Wind
  • Europa Universalis IV
  • Europa Universalis IV: Art of War
  • Crusader Kings II
  • Europa Universalis IV: Wealth of Nations
  • Europa Universalis IV: Call to arms event
  • For the Motherland
  • Hearts of Iron III
  • Heir to the Throne
  • Europa Universalis III Complete
  • Europa Universalis IV: Res Publica
  • Rome Gold
  • Semper Fi
  • Victoria 2
Does the "persistent = yes" command mean that event can no longer be used in a trigger? I've put together an event string and in order to shorten it I made a pair of events persistent so they could be used twice during the course of the string, but for some reason a later event which was contingent on one of these persistent events having fired refused to fire.

For instance, event 400720 is persistent, and so is event 400722. I have 2 events that use these as part of their triggers, which are otherwise identical and look like this...

Trigger = {
exists = SPA
NOT = { exists = SPR }
event = 400720
}

The other event trigger is the same, except the event is 400722. But neither will fire, even though I check and double check and make absolutely sure that 400720/400722 have fired.

By contrast, there are two other events with the same trigger, only the events they are dependent on (400721/400723) are NOT persistent, and BOTH events fired in the appropriate situation. Am I right in thinking it is the "persistent = yes" command that is spoiling the other events?

Thanx in advance!

InVert
 

xtfoster

Field Marshal
57 Badges
Feb 8, 2006
5.874
2.209
  • Shadowrun Returns
  • Surviving Mars
  • Hearts of Iron IV: Death or Dishonor
  • Stellaris: Synthetic Dawn
  • Tyranny - Tales from the Tiers
  • Tyranny - Bastards Wound
  • Age of Wonders III
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Humanoids Species Pack
  • Stellaris: Apocalypse
  • BATTLETECH - Digital Deluxe Edition
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Distant Stars
  • BATTLETECH
  • Shadowrun: Dragonfall
  • Shadowrun: Hong Kong
  • BATTLETECH: Flashpoint
  • Stellaris: Megacorp
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Ancient Relics
  • BATTLETECH: Season pass
  • Age of Wonders: Planetfall Sign Up
  • Stellaris: Lithoids
  • BATTLETECH: Heavy Metal
  • Hearts of Iron IV: La Resistance
  • Hearts of Iron IV: No Step Back
  • Stellaris: Galaxy Edition
  • Deus Vult
  • Europa Universalis III
  • For the Motherland
  • Hearts of Iron III
  • Hearts of Iron III: Their Finest Hour
  • Majesty 2
  • Europa Universalis III Complete
  • Semper Fi
  • Supreme Ruler 2020
  • 500k Club
  • Hearts of Iron II: Beta
  • Stellaris
  • Hearts of Iron II: Armageddon
  • Stellaris: Galaxy Edition
  • Hearts of Iron IV Sign-up
  • Stellaris Sign-up
  • Hearts of Iron IV: Cadet
  • Tyranny: Archon Edition
  • Tyranny: Archon Edition
  • Tyranny: Gold Edition
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Hearts of Iron IV: Expansion Pass
invertigo2004 said:
Does the "persistent = yes" command mean that event can no longer be used in a trigger? I've put together an event string and in order to shorten it I made a pair of events persistent so they could be used twice during the course of the string, but for some reason a later event which was contingent on one of these persistent events having fired refused to fire.

For instance, event 400720 is persistent, and so is event 400722. I have 2 events that use these as part of their triggers, which are otherwise identical and look like this...



The other event trigger is the same, except the event is 400722. But neither will fire, even though I check and double check and make absolutely sure that 400720/400722 have fired.

By contrast, there are two other events with the same trigger, only the events they are dependent on (400721/400723) are NOT persistent, and BOTH events fired in the appropriate situation. Am I right in thinking it is the "persistent = yes" command that is spoiling the other events?

Thanx in advance!

InVert
The event ID will never be logged as having fired (because of the persistent = yes) so the trigger conditions will never be met.

What you could do is include a setflag or local_setflag command and check for that in your follow-up events.