Hands-On Usage
capture_operative is commonly used in intelligence system-related events or decisions to simulate scenarios where your operatives are arrested by enemy nations after mission failure, or to capture enemy operatives during counterintelligence operations. For example, in an event where an enemy spy network is uncovered, you can directly place enemy operatives into player custody:
# Capturing the operative referenced by PREV in an option of a certain nation's event
GER = {
capture_operative = {
operative = PREV
ignore_death_chance = yes
}
}
Synergy
[has_captured_operative](/wiki/trigger/has_captured_operative): Used to check whether a specific operative has been captured; can be used in subsequent event trigger conditions to verify capture status, forming a complete logic chain of "capture → check → process".
[turn_operative](/wiki/effect/turn_operative): After capturing an operative, you can attempt to turn them to your side; the sequential combination of these two is a classic workflow in intelligence events.
[kill_operative](/wiki/effect/kill_operative): If conversion fails or the narrative requires execution, you can follow up with this command after capture, providing players with different disposal branch options.
[free_operative](/wiki/effect/free_operative): The counterpart to capture, can serve as the release outcome in negotiation or operative exchange narrative events, enhancing narrative completeness.
Common Pitfalls
- Scope confusion: When using the operative themselves as scope (CHARACTER scope), you must use the
captured_by = TAG syntax to specify the holding nation; if you mistakenly use the operative = PREV form within character scope, the game will fail to recognize the target, causing the effect to silently fail.
- Target is not an operative: The
operative field or abbreviated target must point to an intelligence operative (the operative type among operatives/unit leaders); if you mistakenly pass in a regular army commander or naval officer, the effect will not error but will fail to correctly trigger the capture logic, making it difficult to detect during debugging.