effect · remove_decision_on_cooldown

Hands-On Usage

When a player triggers a decision cooldown through a specific choice, and the script logic requires resetting that cooldown early (for example, upon completing a particular focus, signing an agreement, or meeting special conditions), this effect can forcibly remove the cooldown state, allowing the player to immediately activate the decision again. This is commonly used in event chain mods that require dynamic adjustment of decision availability, such as "Diplomatic Negotiation" type decisions that become immediately reusable upon achieving specific conditions.

# After a country event triggers, remove the cooldown of a diplomatic decision
country_event = {
    id = my_mod.10
    ...
    option = {
        name = my_mod.10.a
        # Upon meeting special conditions, reset the diplomatic decision cooldown
        remove_decision_on_cooldown = my_diplomatic_negotiation_decision
    }
}

Synergy

• [has_decision](/wiki/trigger/has_decision) — Use this trigger first to detect whether the target decision is currently on cooldown or active, then decide whether to execute the cooldown removal to avoid ineffective calls.
• [activate_decision](/wiki/effect/activate_decision) — Immediately reactivate the decision after removing the cooldown, forming a complete "reset + reactivate" workflow, commonly used for task chains requiring continuous progression.
• [activate_mission](/wiki/effect/activate_mission) — When the resolution of a decision cooldown is tightly bound to the activation of a mission, use both together to ensure mission and decision states remain synchronized.
• [add_days_remove](/wiki/effect/add_days_remove) — If you don't want to completely remove the cooldown but rather shorten the remaining time, compare it with this command and choose accordingly; some scenarios will first check conditions then decide which approach to use for handling decision lifecycle.

Common Pitfalls

1. The target decision name must match exactly: The decision key you enter must be identical to the token defined in the decisions folder. Spelling errors won't generate an error but will silently fail—it's recommended to directly copy and paste the key name.
2. Only works on decisions currently on cooldown: If the decision is not currently on cooldown (for example, if it has never been triggered or has been removed by other means), this effect will have no effect. Don't misuse it to "activate" a regular decision—that is the responsibility of activate_decision.