Permissions¶

The rule is short: a player renames only their own country's things. There are two exceptions: the host, through a game rule set in the lobby, and an overlord whose subject is another player. This page explains how each rule is checked and how far each one is built.

Your own country¶

The pencils and editors appear only for objects of your own country. That is a convenience, not a guard: when a player clicks, the game runs the button's effect without evaluating its visible and enabled triggers again. Every effect therefore checks authority again inside its own body. Rename Anything does this today. The CAPIE SDK provides two scripted triggers for it: capie_v1_actor_ok (the acting country, ROOT, is played by a human) and capie_v1_may_edit_country (in the scope of the target country, see below).

In multiplayer the acting country inside the effect is expected to be the country of the player who issued the command. That is a design assumption until the two-machine test.

The host In the SDK¶

HOI4 has no script trigger that says "this is the host", and reading the game's code found no such flag either: a command carries the country it acts for, not a verified player or machine. The documented triggers mention a host only for governments in exile. So the host's exception works through the one thing only the host controls, the game rules chosen in the lobby. A mod game rule decides what players may rename beyond their own country and its subjects:

Setting the rule in the lobby is the host's consent, and the script reads it with has_game_rule. There is no option that gives the host's own country extra powers during the game, because the script cannot tell which country belongs to the host. CAPIE is not anti-cheat: a modified client can send arbitrary commands in vanilla multiplayer too.

capie_v1_edit_rights = {
    name = "CAPIE_V1_RULE_EDIT_RIGHTS"
    group = "RULE_GROUP_GAMEPLAY"
    default = { name = "CAPIE_V1_OWN" text = "CAPIE_V1_RULE_OWN" desc = "CAPIE_V1_RULE_OWN_DESC" }
    option = { name = "CAPIE_V1_OPEN" text = "CAPIE_V1_RULE_OPEN" desc = "CAPIE_V1_RULE_OPEN_DESC" allow_achievements = yes }
}

The rule applies to every mod built on the SDK, so players set it once per game.

The overlord of a player subject In the SDK¶

An overlord may rename the things of a subject, including a subject that another player controls. The decision is the simplest variant: no veto for the subject and no extra screens. The check is the documented trigger is_subject_of = ROOT on the target country.

# In the scope of the target country; ROOT is the acting country.
capie_v1_may_edit_country = {
    OR = {
        tag = ROOT                      # own country
        is_subject_of = ROOT            # overlord over this subject, AI or player
        has_game_rule = { rule = capie_v1_edit_rights option = CAPIE_V1_OPEN }
    }
}

Inside your Apply effect, a failed check sets capie_err = 20 ("You may not change this.") and changes nothing:

if = {
    limit = {
        capie_v1_ok = yes
        NOT = { AND = { capie_v1_actor_ok = yes capie_v1_may_edit_country = yes } }
    }
    set_temp_variable = { capie_err = 20 }
}

Rename Anything has its own lobby rule, rn_edit_rights, with three options: own country and subjects (default), the host renames every country, or own country only. It does not read the SDK's rule. Its overlord renaming of subjects works in single player. Until CAPIE can tell who the host is, the host option works in single player only.