• Crusader Kings II Expansion Subscription

    Subscribe to the CK II Expansion and enjoy unlimited access to 13 major expansions and more!


  • Paradox Midsummer Sale has arrived! Up to 75% off!

    Enjoy some sun and song this Midsummer, but when the sun goes down, the fun doesn't have to stop! Paradox has a festive sale on plenty of games to keep your summer nights going!


    June 18th - June 30th
  • Crusader Kings III Available Now!

    The realm rejoices as Paradox Interactive announces the launch of Crusader Kings III, the latest entry in the publisher’s grand strategy role-playing game franchise. Advisors may now jockey for positions of influence and adversaries should save their schemes for another day, because on this day Crusader Kings III can be purchased on Steam, the Paradox Store, and other major online retailers.


    Real Strategy Requires Cunning

TheRemQc

French Canadian Imperialist
40 Badges
Aug 3, 2014
551
99
  • Victoria 2: Heart of Darkness
  • Stellaris: Leviathans Story Pack
  • Stellaris - Path to Destruction bundle
  • Europa Universalis IV: Third Rome
  • Stellaris: Synthetic Dawn
  • Victoria 2: A House Divided
  • Europa Universalis IV: Res Publica
  • Europa Universalis IV: Wealth of Nations
  • Europa Universalis IV: Conquest of Paradise
  • Europa Universalis IV: Art of War
  • Darkest Hour
  • Stellaris: Humanoids Species Pack
  • Europa Universalis IV: Rule Britannia
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Expansion Pass
  • Europa Universalis IV: Cradle of Civilization
  • Hearts of Iron IV: Death or Dishonor
  • Steel Division: Normand 44 Sign-up
  • Europa Universalis IV: Dharma
  • Europa Universalis IV: Mandate of Heaven
  • Steel Division: Normandy 44
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Together for Victory
  • Hearts of Iron IV: La Resistance
  • Stellaris: Digital Anniversary Edition
  • Europa Universalis IV: Rights of Man
  • Crusader Kings II: Reapers Due
  • Stellaris
  • Crusader Kings II: Conclave
  • Europa Universalis IV: Cossacks
  • Europa Universalis IV: Common Sense
  • Crusader Kings II: Way of Life
  • Europa Universalis IV: El Dorado
  • Victoria 2
  • Europa Universalis IV
  • Crusader Kings II
  • Europa Universalis IV: Mare Nostrum
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: Charlemagne
Looks like I will have a two-day streak this time,
I have another one.

For some reason my event using the days trigger doesn't want to work.
I wrote it down this way, thinking it was fine:

Code:
event = {
    id = 254024
    random = no
    country = IND
  
    trigger = {
        event = { id = 254022 days = 360 }
    }

    name = "EVT_254024_NAME"
    desc = "EVT_254024_DESC"
    style = 2
    picture = "indian_officer"
  
    action = {
        name = "ACTION_NAME_GREAT"
        command = { type = sleepteam which = 250032 when = 1 }
        command = { type = sleepteam which = 250031 when = 1 }
        command = { type = waketeam which = 250033 when = 1 }
        command = { type = waketeam which = 250030 when = 1 }
        command = { type = waketeam which = 250029 when = 1 }
        command = { type = waketeam which = 250034 when = 1 }
    }
}

But after 360 days, it does not fire. I made sure event 254022 had the save_date line on it:

Code:
event = {
    id = 254022
    random = no
    country = IND
    save_date = yes
  
    # Triggered by ENG 254021

    name = "EVT_254022_NAME"
    desc = "EVT_254022_DESC"
    style = 2
    picture = "indian_officer"
  
    action = {
        name = "ACTION_NAME_PERFECT"
        command = { type = dissent value = -2 }
        command = { type = money value = -150 }
        command = { type = relation which = ENG value = 5 }
        command = { type = sleepevent which = 254025 }
    }
}

Usuallly I'm using the command = { type = event which = XXXX where = TAG when = XX } line but with this one I figured since the wait was a year long I should use the trigger in the event... Was it a good idea? Performance-wise is there a better one between the two?
 
Last edited:

^_AC_^

Field Marshal
83 Badges
Feb 24, 2009
5.549
198
  • Victoria 2: A House Divided
  • Sengoku
  • Semper Fi
  • Victoria: Revolutions
  • Europa Universalis IV: Res Publica
  • Magicka
  • Leviathan: Warships
  • Knights of Pen and Paper +1 Edition
  • Victoria 2: Heart of Darkness
  • Warlock 2: The Exiled
  • Hearts of Iron IV Sign-up
  • Europa Universalis III Complete
  • The Showdown Effect
  • Stellaris
  • War of the Roses
  • 500k Club
  • Stellaris Sign-up
  • Europa Universalis IV: El Dorado
  • Imperator: Rome Sign Up
  • Crusader Kings II: Way of Life
  • Pillars of Eternity
  • Stellaris: Ancient Relics
  • Europa Universalis IV: Common Sense
  • Europa Universalis IV: Cossacks
  • Crusader Kings II: Conclave
  • Crusader Kings II: Reapers Due
  • Stellaris: Synthetic Dawn
  • Europa Universalis IV: Cradle of Civilization
  • Stellaris: Apocalypse
  • Europa Universalis IV: Rule Britannia
  • Cities: Skylines - Parklife
  • Europa Universalis IV: Dharma
  • Stellaris: Megacorp
  • Crusader Kings II: Holy Fury
  • Europa Universalis IV: Golden Century
  • Hearts of Iron IV: Cadet
  • Imperator: Rome Deluxe Edition
  • Cities: Skylines - Green Cities
  • Prison Architect
  • Europa Universalis IV: Rights of Man
  • Europa Universalis IV
  • Tyranny: Archon Edition
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Crusader Kings II: Monks and Mystics
  • Stellaris - Path to Destruction bundle
  • Europa Universalis IV: Mandate of Heaven
  • Surviving Mars
  • Imperator: Rome
  • Europa Universalis III Complete
For some reason my event using the days trigger doesn't want to work.
I wrote it down this way, thinking it was fine:


But after 360 days, it does not fire. I made sure event 254022 had the save_date line on it:
That's because the first event is missing date+offset+deathdate, so it's never checking when the trigger becomes true.

Usuallly I'm using the command = { type = event which = XXXX where = TAG when = XX } line but with this one I figured since the wait was a year long I should use the trigger in the event... Was it a good idea? Performance-wise is there a better one between the two?
Performance-wise is better to use command = { type = event which = XXXX where = TAG when = XX } since in this case the event is scheduled and the trigger is checked only when at the scheduled date (and that's why in this case it is doesn't have date+offset+deathdate).
Moreover, the trigger event = { id = 254022 days = 360 } means "at least 360 days passed", so if you want it to fire after exactly 360 days that mean that offset must be 1 so that is checked every day, but offset = 1 (and low values of offset in general) is a bad idea for the performance, since it checks the event every days until it fires.
 
  • 1
Reactions:

TheRemQc

French Canadian Imperialist
40 Badges
Aug 3, 2014
551
99
  • Victoria 2: Heart of Darkness
  • Stellaris: Leviathans Story Pack
  • Stellaris - Path to Destruction bundle
  • Europa Universalis IV: Third Rome
  • Stellaris: Synthetic Dawn
  • Victoria 2: A House Divided
  • Europa Universalis IV: Res Publica
  • Europa Universalis IV: Wealth of Nations
  • Europa Universalis IV: Conquest of Paradise
  • Europa Universalis IV: Art of War
  • Darkest Hour
  • Stellaris: Humanoids Species Pack
  • Europa Universalis IV: Rule Britannia
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Expansion Pass
  • Europa Universalis IV: Cradle of Civilization
  • Hearts of Iron IV: Death or Dishonor
  • Steel Division: Normand 44 Sign-up
  • Europa Universalis IV: Dharma
  • Europa Universalis IV: Mandate of Heaven
  • Steel Division: Normandy 44
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Together for Victory
  • Hearts of Iron IV: La Resistance
  • Stellaris: Digital Anniversary Edition
  • Europa Universalis IV: Rights of Man
  • Crusader Kings II: Reapers Due
  • Stellaris
  • Crusader Kings II: Conclave
  • Europa Universalis IV: Cossacks
  • Europa Universalis IV: Common Sense
  • Crusader Kings II: Way of Life
  • Europa Universalis IV: El Dorado
  • Victoria 2
  • Europa Universalis IV
  • Crusader Kings II
  • Europa Universalis IV: Mare Nostrum
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: Charlemagne
Performance-wise is better to use command = { type = event which = XXXX where = TAG when = XX } since in this case the event is scheduled and the trigger is checked only when at the scheduled date (and that's why in this case it is doesn't have date+offset+deathdate).
Moreover, the trigger event = { id = 254022 days = 360 } means "at least 360 days passed", so if you want it to fire after exactly 360 days that mean that offset must be 1 so that is checked every day, but offset = 1 (and low values of offset in general) is a bad idea for the performance, since it checks the event every days until it fires.
Alright, got it. Its been a long time since I have done long and paths-heavy event chains and I have found myself to be quite rusty. I'm definitely writing this down!
Thank you again