GUIDE · EDITOR DE ESCENARIO
Scenario variables
Scenario variables store values or states that triggers can inspect and change. They can track mission progress, count events, and select branching outcomes across several rules. (desencadenador)
Resumen
Scenario variables store values or states that triggers can inspect and change. They can track mission progress, count events, and select branching outcomes across several rules. (desencadenador)
How this system affects decisions
Variables provide shared state for a scenario's desencadenador logic. A desencadenador can set or change a value, and another can check it before enabling an event. This supports counters, mission stages, and branching paths, but inconsistent names or values can make a cadena stop working. Plan what each variable represents and which triggers are allowed to change it. (editor de escenario)
Cómo usar esta referencia
Create a simple naming scheme and document the meaning and expected range of every variable. Set an initial value, update it through a specific desencadenador, and use conditions to branch when the value reaches the intended state. Test the smallest and largest expected values, repeated events, and paths where a player never completes an objective so the scenario cannot enter an undefined state. (desencadenador)
- Enfoque
- Editor de escenario
- Elemento distintivo / categoría
- How it works
- Edición / contexto
- Age of Empires II system
- Región
- Editor de escenario
- Clasificación
- Game systems