trigger · num_researched_technologies
Definition
- Supported scope:
COUNTRY - Supported target:
none
Description
Number of researched technologies
num_researched_technologiesCOUNTRYnoneNumber of researched technologies
Hands-on notes are AI-generated and checked against the vanilla command vocabulary — treat them as a starting point, not authoritative reference. The definition above is the game's own documentation.
num_researched_technologies is commonly used in mods to unlock special decisions, national focuses, or advisors based on a country's technology research progress. For example, it can restrict specific events to trigger or enable advanced military industrial organizations only after a nation has researched sufficient technologies. It can also be integrated into AI weight logic, allowing the AI to make strategic decisions only after reaching a technology accumulation threshold.
# Example: Allow a decision to activate only after researching a certain number of technologies
available = {
num_researched_technologies > 20
}
[can_research](/wiki/trigger/can_research): Often used together to verify the current researchable state, providing dual validation of technology condition integrity.[amount_research_slots](/wiki/trigger/amount_research_slots): Used in conjunction with research slot quantity to distinguish between two dimensions: "has capacity for rapid research" vs. "has already researched how much," making conditions more precise.[add_tech_bonus](/wiki/effect/add_tech_bonus): When the technology count condition is met, use this effect to grant additional technology bonuses as rewards or to advance logic.[add_research_slot](/wiki/effect/add_research_slot): Commonly paired as a reward effect to unlock additional research slots after a nation accumulates a certain amount of technology, creating a snowball effect in technology design.num_researched_technologies = 20 (meaning exactly 20) instead of >= 20 or > 19, causing conditions to rarely trigger or behave unexpectedly. Always use comparison operators like >, >=, < based on actual requirements.has_doctrine) rather than relying on this trigger.