effect · remove_claim_by
Definition
- Supported scope:
STATE - Supported target:
THIS,ROOT,PREV,FROM,OWNER,CONTROLLER,OCCUPIED,CAPITAL
Description
Removes state claim by country.
remove_claim_bySTATETHIS, ROOT, PREV, FROM, OWNER, CONTROLLER, OCCUPIED, CAPITALRemoves state claim by country.
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.
remove_claim_by is commonly used in diplomacy, peace negotiations, territorial transfers, and post-war reorganization scenarios in mods. It is invoked when a nation relinquishes its territorial claim on a state, keeping map sovereignty relationships clean and organized. For example, in a peace agreement option, remove the claimant's claim while transferring the state:
# Remove Germany's claim on the state within STATE scope
state_event = {
id = my_peace.1
option = {
name = my_peace.1.a
# transfer_state_to has already transferred the state to the new owner
remove_claim_by = GER
}
}
[is_claimed_by](/wiki/trigger/is_claimed_by): Use this trigger before executing the removal to verify that the target nation actually holds the claim, avoiding ineffective calls or logical gaps.[add_claim_by](/wiki/effect/add_claim_by): The counterpart command, commonly paired in "territorial exchange" scenarios where you first add a claim to the beneficiary, then remove the original claimant's claim.[remove_core_of](/wiki/effect/remove_core_of): Claims and cores are typically handled in tandem; when transferring territory, you often need to remove that nation's core simultaneously to ensure the map state is completely cleaned up.[transfer_state_to](/wiki/effect/transfer_state_to): Actual territorial transfer is invariably accompanied by claim cleanup. These two commands almost always appear in the same option block.remove_claim_by must be executed within STATE scope. Beginners often mistakenly write it in country scope (COUNTRY), causing script errors or silent failures. Confirm you are in state scope first using commands like set_state_owner_to, or enter the correct scope within the event via state_scope before calling it.[is_claimed_by](/wiki/trigger/is_claimed_by) in trigger conditions or hidden_trigger to ensure logic is accurate and traceable.