Problem with a custom decision's triggering

[Rotten Venetic]

I've made a decision for Poland that lets them go on a rampage in the East and try to reclaim the old P-L Republic if they manage to beat Germany. Typically not an AI decision, as you'd imagine.

When I load as POL in 1936, I correctly don't even see the decision, but the AI sometimes manages to trigger it at the start of the game (when completely unready to fight SOV ) and I have to load as them and peace out with acceptall.

Here is the event's triggers. It's not a duplicate ID or a bracket problem, obviciously.

event = {
	id = 9123026
	random = no
	country = POL
	decision = {
		event = 9123010
		OR = {
			exists = SOV
			exists = RUS
		}
		NOT = {
			atwar = POL
			exists = U06 #Free City of Danzig
			alliance = { country = ENG country = POL }
			ispuppet = POL		
		}
	}
	decision_trigger = { 
		event = 9123010
		OR = {
			exists = SOV
			exists = RUS
		}
		NOT = {
			atwar = POL
			exists = U06 #Free City of Danzig
			alliance = { country = ENG country = POL }
			ispuppet = POL		
		}
		NOT = {
			dissent = 12
			month = 8
		}
		month = 4
		OR = {
			ai = SOV
			not = { ai = POL }
		}
		OR = {
			puppet = { country = LIT country = POL }
			alliance = { country = LIT country = POL }
			not = { exists = LIT }
		}
		policy = { type = professional_army value = 7 }	
	}

What's the problem?

 

[^_AC_^]

The AI treats decisions as events and only considers the trigger = {} clause, which you didn't post, so I can't tell you the problem (unless the problem is that you didn't make a trigger = {} section for the AI).

EDIT: take a look at Darkest Hour\Modding documentation\Guide to Darkest Hour.pdf for more info on decisions.

 

[Rotten Venetic]

Ouch. I don't have a trigger = {}

That should be it then. Thanks.

 

[Limith]

You also need a startdate and enddate for when the ai should check the triggers.

 

[Rotten Venetic]

That I had, they weren't relevant. The trigger bit fixed it.