trigger · has_navy_experience

Hands-On Usage

has_navy_experience is commonly used to determine whether a player or AI nation has accumulated sufficient naval experience to unlock specific focuses, decisions, or advisors. For example, in mods centered around naval powers, it can serve as an available prerequisite for a decision focused on fleet expansion, preventing players from directly triggering advanced naval content without any naval foundation.

available = {
    has_navy_experience > 50
}

Synergy

• [has_army_experience](/wiki/trigger/has_army_experience) / [has_air_experience](/wiki/trigger/has_air_experience) — The three experience triggers typically appear together to comprehensively assess a nation's military accumulation, suitable for designing multiple prerequisites for "comprehensive military reform" type decisions.
• [has_navy_leader](/wiki/trigger/has_navy_leader) — When sufficient naval experience is present, it is often necessary to confirm the existence of an available naval commander. Using both together ensures naval content is logically consistent.
• [add_ideas](/wiki/effect/add_ideas) — Once experience conditions are met, use effect blocks to grant corresponding naval doctrines or advisors, forming a complete decision/focus flow with "meeting targets yields rewards."
• [command_power](/wiki/trigger/command_power) — Used alongside command point checks to construct a "dual-threshold system," allowing high-value naval operations to consume both experience and command points.

Common Pitfalls

1. Reversed comparison operator direction: Beginners often mistakenly write logic for "disable when experience is insufficient" as has_navy_experience > 50, forgetting that this returns true when the condition is met. To express "unavailable when experience is lacking," wrap the entire condition in NOT = { has_navy_experience > 50 }, or directly adjust the threshold direction. Confusing the intended logic is the most common mistake.
2. Using outside COUNTRY scope: This trigger is only valid within COUNTRY scope. If accidentally nested inside other scopes like any_owned_state or any_unit_leader, the script will not report an obvious error but the condition will always evaluate to false, causing the condition to never trigger.