# Decisions concept:
new modifier in misc.txt (“mod” section): #Enable decisions for players. 0 - Disabled, 1 – Enabled
Basics
1. Decisions are modified events.
2. They differ from regular event only by the presence of a new section - decision
3. Decisions are treated as regular events by the AI.
4. Players have the power to choose when a decision could be applied.
5. Decisions are hidden until all triggers in decision = { } section is true.
6. Decision are available for selection when all triggers in decision_trigger = { } section in the event are true. If decision_trigger = { } section doesn't exist or is empty, it will use trigger = { } instead.
7. Once selected the decisions fire as regular event via standard event window with all the usual information and actions on it.
8. Decisions are logged in event history as regular events.
New entry in the event :
decision_desc = "....", optional decision specific text (used on tool-tips instead of event description).
decision_picture = "picture_name.bmp". Optional (there will be a generic picture loaded by default - gfx\event_pics\decisions_empty.bmp), placed on the decision plate
decision_trigger = { }. It is optional and will be used instead of trigger = { }. When it is true the decisions will be active for selection. When not present trigger = {} section will be used for that.
Limitations
1. Decisions should not use random elements in any triggers so tool-tips to be correct. EDIT No problem to use random trigger in AI only actions or commands
2. For better formatting on tool-tips NOT = { trigger1 ... triggerX } should be used for individual triggers only NOT = { trigger1 } ... NOT = { triggerX } NEW
