Hands-On Usage
injure_scientist_for_days is commonly used in mods to simulate narrative effects where scientists become temporarily incapacitated after executing dangerous research projects, experiencing laboratory accidents, or suffering sabotage from operatives. This prevents the player from using that scientist in research for a set period. For example, forcing a scientist to be injured in a technology disaster event:
country_event = {
id = my_mod.42
title = "Laboratory Explosion Incident"
option = {
name = "Arrange Treatment"
# Switch into scientist character scope before calling
my_lead_scientist_character = {
injure_scientist_for_days = 30
}
}
}
Synergy
[is_scientist_injured](/wiki/trigger/is_scientist_injured) — Check whether the scientist is already in an injured state before or after applying the effect, preventing duplicate triggers or conflicting stacking logic.
[is_active_scientist](/wiki/trigger/is_active_scientist) — Confirm the character currently holds active scientist status, preventing execution on unactivated characters that would result in invalid calls.
[add_scientist_xp](/wiki/effect/add_scientist_xp) — Can be used as a compensation reward granting experience after recovery, forming a complete narrative arc of "incident → recovery → growth".
[operative_leader_event](/wiki/effect/operative_leader_event) — If the scientist also serves in an intelligence role, can trigger subsequent events simultaneously with the injury to advance the story.
Common Pitfalls
- Incorrect scope targeting: This command must be executed within a
CHARACTER scope. Beginners often call it directly under COUNTRY scope without first switching into the character scope via a character variable, causing script errors or silent failures. Always verify you have switched to the correct scientist character scope.
- Using on non-scientist characters: If the target character has not been assigned scientist functionality through
add_scientist_role, executing this command typically produces no actual effect. It is recommended to protect the call with a condition check using [is_active_scientist](/wiki/trigger/is_active_scientist) beforehand.