Hands-On Usage
amount_taken_ideas is commonly used to check whether a nation has configured a sufficient number of advisor or staff slots, thereby unlocking specific decisions or national focuses. For example, in military reform mods, you can require players to fill a certain number of military staff positions before triggering subsequent events, or use it as a prerequisite in a decision's available condition to prevent players from skipping the development phase.
# This decision is only available once the nation has selected at least 2 military advisors
available = {
amount_taken_ideas = {
amount > 2
categories = { military_staff }
}
}
Synergy
[has_available_idea_with_traits](/wiki/trigger/has_available_idea_with_traits): First use this trigger to check whether suitable advisor candidates exist, then combine with amount_taken_ideas to confirm the current number already selected. Together they form a complete logic chain verifying "talent is available AND sufficiently deployed."
[add_ideas](/wiki/effect/add_ideas): Once the amount_taken_ideas condition is met, use this effect to grant the nation a spirit bonus, creating a gameplay loop of "assemble a complete advisor team → receive bonuses."
[has_allowed_idea_with_traits](/wiki/trigger/has_allowed_idea_with_traits): Combined with amount_taken_ideas, this distinguishes between "the nation is theoretically allowed to hire a certain type of advisor" and "how many are actually hired," useful for designing phased unlock quest chains.
[activate_decision](/wiki/effect/activate_decision): Trigger decision activation once amount_taken_ideas is met, ideal for designs like "fill the general staff to unlock strategic commands."
Common Pitfalls
- Mistakenly assuming it counts national spirits and hidden ideas: This trigger explicitly excludes
national_spirit, hidden, and law = yes type ideas. If your counting target happens to be national spirits or hidden buffs, this trigger will never count them and you'll need to use alternative detection methods.
- The
amount field is mandatory and comparison operators are easily mistyped: amount is a required field; omitting it causes script errors. Additionally, pay attention to the semantics when using > / < operators ("greater than" rather than "greater than or equal to"). If you want "at least 2," write amount > 1 instead of amount > 2, otherwise the actual threshold will be one notch higher than intended.