AI模组制作

The artificial intelligence controlling countries in Hearts of Iron IV can be changed in many different aspects. This includes changing the focuses or technologies it pursues, changing how many units or buildings it should produce and of which type, where it should focus forces, which templates or variants it should aim for, and so on.

MTTH blocks

MTTH blocks, named in the game within /Hearts of Iron IV/common/mtth/, are a way to assign a dynamic value to some block, whether it's a country = { ... } in a focus tree to assign which countries can get it, a dynamically-changing variable value (as in /Hearts of Iron IV/common/mtth/), a mean-time-to-happen value for an event, et cetera. As MTTH blocks are spread throughout the entire game, it's incredibly important to know how one works. Its most common application, however, is assigning a base AI weight to a database entry such as a national focus or a technology.

In most cases, marked with ai_will_do, the approach taken by the game is generating a decimal number between 0 and the value of the ai_will_do block, and picking the entry with the highest value. There can be other modifiers applied after the ai_will_do value, such as the ones applied within AI strategy plans towards focuses and research or the ones that get defined within 定义文件, which'll multiply the value you get. This can include different ai_will_do values such as what's done with country leader traits and with ideas or characters that use them.
Event options, instead, use ai_chance, which uses probability-proportional-to-size sampling with a virtual roll of d00 being the final deciding factor. Due to that, in the end, an event option cannot have a probability which isn't a multiple of 1/100 to be picked, although the total sum of each option's weights can be vastly different from 100. In other words, if one option has a value of 1, while the other has a value of 999, the probability for the first option to be picked will be 1% rather than 0.1%.

A MTTH block begins with an assumed value of 1. Further manipulations are done from that value as a starting point. There are 3 value-modifying arguments that can be done, add, 基础, and factor, done like factor = 0.3, 基础=10, or add = 5. add adds the specified argument to the value, factor multiplies it, and 基础, typically done in the start before any changes, sets it to a different number entirely, akin to multiplying by 0 and adding the number.
In order for an operation to apply conditionally, a modifier = { ... } block is used. This also functions as a trigger block, with the default scope (thus also ROOT) being the country for which the MTTH block is evaluated. Depending on the MTTH block, there may be additional scopes marked with FROM or FROM.FROM other than the default. The value-modifying arguments function as regular arguments, they can be put in anywhere directly within the modifier = { ... } block with almost no difference, whether it's in the end, the beginning, or between triggers.

变量 can be used within the value-modifying arguments as well. If using a temporary variable that is defined within the modifier = { ... } trigger block, then the value-modifying argument of the modifier has to be after the definition of the variable in order for the variable to apply as defined. Variables can also be used outside of the modifier = { ... } block and directly inside of the MTTH block itself.

示例

ai_will_do = {
    base = 10.5

    # If the country is Germany, set the value to 0,
    # causing an early end of the evaluation.
    modifier = { tag = GER factor = 0 }
    modifier = { is_major = yes add = 1 }
    modifier = {
        factor = 3
        add = 2.5
        tag = FRA
    }
    factor = 2

    modifier = {
        set_temp_variable = { t = num_of_civilian_factories }
        add_to_temp_variable = { t = num_of_military_factories }
        divide_temp_variable = { t = 10 }
        round_temp_variable = t
        add = t
    }
}

Assuming that GER and FRA are major countries, the result is

• 0 for GER: 10.5· 0=0
• 74 for FRA: : ((10.5 + 1) · 3 + 2.5) · 2 = 74
• 23 for other majors: : (10.5 + 1) · 2 = 23
• 21 for minors: : 10.5 · 2 = 21

After calculating that value, the total number of civilian and military factories within the country, divided by 10 and rounded, will get added to the score. If FRA has a total of 43 civilian and military factories as it does in base game, then this will result in 4 being added to the prior 74 for a total of 78, for example.

AI strategies

AI strategies are used in order to pursue AI to do or avoid something. This includes diplomatic actions the AI will do, where and how exactly AI should focus and use its land army and the navy, the production lines for buildings and equipment, how AI should handle the intelligence system within the 抵抗运动 DLC.
A value within an AI strategy can be either positive or negative, and it being negative will make AI desire to do it less.

Regular AI strategies are stored in /Hearts of Iron IV/common/ai_strategy/*.txt files, however, AI strategies may be defined outside of that file. The add_ai_strategy effect can add a permament AI strategy within any effect block, and AI strategy plans can also include AI strategies defined within of themselves. Overall, /Hearts of Iron IV/common/ai_strategy/*.txt files describe AI strategies that would enable and disable themselves automatically.
Each entry within a /Hearts of Iron IV/common/ai_strategy/*.txt file is a block with the name of the AI strategy. This name can be anything, even allowing overlap between them: this will only appear in AI dumps and the player will never see it. If an AI strategy modifies the chance for AI to pick a diplomatic option with the player, it will be seen as COUNTRY has strategic reasons to be ... to the player when hovering over the option. This is an example of an AI strategy with the name of BHR_invade_qatar:

BHR_invade_qatar = {
    allowed = {
        original_tag = BHR
    }
    enable = {
        country_exists = QAT
    }
    abort = {
        has_war_with = QAT
    }
    abort_when_not_enabled = yes
    ai_strategy = {
        type = invade
        id = QAT
        value = 200
    }
}

参数

These in particular are arguments for /Hearts of Iron IV/common/ai_strategy/*.txt entries, rather for AI strategy entries within them.

allowed = { ... } is a trigger block that's checked only before the game's start, permamently allowing or disallowing an AI strategy. Typically, only used for country checks (such as tag = OMA) or DLC checks that can never be unfulfilled once they are met.

enable = { ... } is a trigger block that must be met in order to enable the AI strategy. By default, this being unmet will 不 cancel the AI strategy. However, abort_when_not_enabled = yes can be used as a separate argument in order to make that be no longer the case. Unlike allowed, this is checked continuously.

abort = { ... } is a trigger block that must be met in order to remove the AI strategy. It being unmet also prevents it from being added in the first place.

ai_strategy = { ... } is, itself, the AI strategy that would be applied. The only argument shared for every AI strategy is type = <AI strategy type>. The rest depends on the AI strategy.

In addition, reversed AI strategies exist. These are used with AI strategies that use id = TAG to target towards a specific country to swap it around: that strategy will be enabled for TAG towards the country which meets enable = { ... }. In order to mark the AI strategy as reversed, reversed = yes is used. enable_reverse = { ... } is an additional trigger block required to enable this AI strategy. It does not have a default scope, so scoping into a country is required.
An example of a reversed AI strategy is the following:

BHR_support_neutrals = {
    allowed = {
        NOT = { original_tag = BHR }
    }
    enable = {
        has_government = neutrality
    }
    enable_reverse = {
        BHR = { has_government = neutrality }
    }
    reversed = yes
    abort_when_not_enabled = yes
    ai_strategy = {
        type = support
        id = BHR
        value = 100
    }
}

Without reversed = yes, this would make every 中立主义 country support BHR. Due to that argument, the strategy is reversed: instead, BHR supports every 中立主义 country.

类型

This list may be outdated. A list of every AI strategy can be found within base game's /Hearts of Iron IV/common/ai_strategy/documentation.info file.

ai_strategy = {
    type = alliance
    id = USA
    value = -100
}

ai_strategy = {
    type = antagonize
    id = USA
    value = -100
}

ai_strategy = {
    type = asking_foreign_garrison
    id = USA
    value = 100
}

ai_strategy = {
    type = befriend
    id = USA
    value = 100
}

ai_strategy = {
    type = conquer
    id = USA
    value = 100
}

ai_strategy = {
    type = consider_weak
    id = USA
    value = 100
}

ai_strategy = {
    type = contain
    id = USA
    value = 100
}

ai_strategy = {
    type = declare_war
    id = USA
    value = 100
}

ai_strategy = {
    type = diplo_action_acceptance
    id = USA
    value = 100
    target = join_allies
}

ai_strategy = {
    type = diplo_action_desire
    id = USA
    value = 100
    target = call_allies
}

ai_strategy = {
    type = dont_join_wars_with
    id = USA
    value = 100
    target_country = BHR
}

ai_strategy = {
    type = ignore
    id = USA
    value = 100
}

ai_strategy = {
    type = ignore_claim
    id = USA
    value = 1
}

ai_strategy = {
    type = protect
    id = USA
    value = 100
}

ai_strategy = {
    type = support
    id = USA
    value = 100
}

ai_strategy = {
    type = send_lend_lease_desire
    id = USA
    value = 100
}

ai_strategy = {
    type = send_volunteers_desire
    id = USA
    value = 100
}

ai_strategy = {
    type = invade
    id = USA
    value = -100
}

ai_strategy = {
    type = naval_invasion_focus
    value = 100
}

ai_strategy = {
    type = prepare_for_war
    id = USA
    value = 100
}

ai_strategy = {
    type = area_priority
    id = europe
    value = 100
}

ai_strategy = {
	type = strategic_air_importance
	id = 18 #English Channel
	value = -30000
}

ai_strategy = {
    type = dont_defend_ally_borders
    id = POL
    value = 10
}

ai_strategy = {
    type = force_defend_ally_borders
    id = FRA
    value = 100
}

ai_strategy = {
    type = front_armor_score
    id = POL
    value = 100
}

ai_strategy = {
    type = front_control
    state_trigger = {
        industrial_complex > 1
        is_owned_by = ENG
    }
    ratio = 0.1
    ordertype = front
    execution_type = rush
    manual_attack = no
}

ai_strategy = {
    type = front_control
    area = suez
    priority = 1
    ratio = 0.2
    ordertype = invasion
    execute_order = yes
}

ai_strategy = {
	type = force_concentration_front_factor

	tag = CZE
	state = 9
	strategic_region = 22
	ratio = 0.2

	value = 40
}

ai_strategy = {
	type = force_concentration_factor
	value = 20
}

ai_strategy = {
# As Germany - Avoid attacking the areas behind the Maginot line
	type = force_concentration_target_weight
	state = 18 # Champagne
	state = 17 # Franche-Comte
	state = 28 # Alsace-Lorraine
	state = 27 # Bourgogne

	value = -60
}

ai_strategy = {
    type = front_unit_request
    tag = POL
    value = 100
}

ai_strategy = {
    type = front_unit_request
    country_trigger = {
        original_tag = SPR
        has_government = fascism
    }
    value = 100
}

ai_strategy = {
    type = invasion_unit_request
    state = 123
    value = 100
}

ai_strategy = {
    type = invasion_unit_request
    strategic_region = 42
    value = 100
}

ai_strategy = {
    type = garrison
    value = 10
}

ai_strategy = {
    type = garrison_reinforcement_priority
    value = 100
}

ai_strategy = {
    type = ignore_army_incompetence
    value = 100
}

ai_strategy = {
    type = put_unit_buffers
    ratio = 0.2
    states = {
        123
        124
        125
        126
    }
    subtract_fronts_from_need = yes
}

ai_strategy = {
    type = spare_unit_factor
    value = 100
}

ai_strategy = {
    type = theatre_distribution_demand_increase
    value = 10
    id = 123
}

ai_strategy = {
    type = naval_avoid_region
    id = 23
    value = 100
}

ai_strategy = {
    type = naval_convoy_raid_region
    id = 23
    value = 100
}

ai_strategy = {
    type = naval_mission_threshold
    id = MISSION_CONVOY_RAIDING
    value = -100
}

ai_strategy = {
    type = strike_force_home_base
    id = 18
    value = 70
}

ai_strategy = {
    type = agency_ai_base_num_factories_factor
    value = 70
}

ai_strategy = {
    type = agency_ai_per_upgrade_factories_factor
    value = 70
}

ai_strategy = {
    type = intelligence_agency_branch_desire_factor
    id = branch_crypto
    value = 70
}

ai_strategy = {
    type = intelligence_agency_usable_factories
    value = 8
}

ai_strategy = {
    type = operation_equipment_priority
    value = 80
}

ai_strategy = {
    type = operative_mission
    value = 80
    mission = quiet_intel_network
    state = 123
    state = 321
    mission_target = ENG
}

ai_strategy = {
    type = operative_operation
    value = 80
    operation = heavy_water_raid
    operation_target = ENG
}

ai_strategy = {
    type = become_spymaster
    value = 30
}

ai_strategy = {
    type = added_military_to_civilian_factory_ratio
    value = 50
}

ai_strategy = {
    type = air_factory_balance
    value = 50
}

ai_strategy = {
    type = dockyard_to_military_factory_ratio
    value = 50
}

ai_strategy = {
    type = railway_gun_divisions_ratio
    value = 5
}

ai_strategy = {
    type = build_building
    id = industrial_complex
    target = 803
    value = 1
}

ai_strategy = {
    type = building_target
    id = industrial_complex
    value = 30
}

ai_strategy = {
    type = factory_build_score_factor
    target = 365
    value = 1
}

ai_strategy = {
    type = equipment_production_factor
    id = armor
    value = 30
}

ai_strategy = {
    type = equipment_production_min_factories
    id = artillery
    value = 3
}

ai_strategy = {
    type = equipment_production_min_factories_archetype
    id = artillery_equipment
    value = 4
}

ai_strategy = {
    type = equipment_variant_production_factor
    id = light_tank_chassis
    value = -100
}

ai_strategy = {
    type = equipment_stockpile_surplus_ratio
    value = 30
}

ai_strategy = {
    type = build_army
    id = infantry
    value = 200
}

ai_strategy = {
    type = force_build_armies
    value = 30
}

ai_strategy = {
    type = production_upgrade_desire_offset
    id = artillery_equipment_2
    value = -50
}

ai_strategy = {
    type = role_ratio
    id = paratroopers
    value = 30
}

ai_strategy = {
    type = unit_ratio
    id = cas
    value = 30
}

ai_strategy = {
    type = min_wanted_supply_trains
    value = 300
}

ai_strategy = {
    type = min_wanted_supply_trucks
    value = 30
}

ai_strategy = {
    type = scorched_earth_prio
    value = 100
    id = ENG
    states = {
        123
        124
        125
        126
    }
}

ai_strategy = {
    type = land_xp_spend_priority
    id = division_template
    value = 30
}

ai_strategy = {
    type = pp_spend_amount
    id = idea
    value = 100
}

ai_strategy = {
    type = pp_spend_priority
    id = relation
    value = 100
}

ai_strategy = {
    type = research_weight_factor
    id = radio_detection
    value = 2000
}

AI areas

AI areas are defined within /Hearts of Iron IV/common/ai_areas/*.txt files. These are only used in a variety of previously-listed AI strategies, such as area_priority. A province may be in several AI areas and it may be in none. Hovering over a province with the debug mode turned on will provide information in which AI areas the province is, if any.

Each AI area is a separate block within the file, with the name of the block being the name of the area. Within these blocks, 2 things can be added:
continents = { ... } is a list of continents that make up the AI area. Continents are defined within /Hearts of Iron IV/map/continent.txt and assigned to provinces within their definitions in /Hearts of Iron IV/map/definition.csv. The full name of the continent should be used within the AI area's definition, rather than the ID used in the province definition.
strategic_regions = { ... } is a list of strategic regions that make up the AI area, by their ID number.

If there are multiple defined, the province has to be in 任意 of them.

An example of an AI area is the following:

my_ai_area = {
    continents = {
        europe
        africa
    }
    strategic_regions = {
        53  # Caribbean
        189 # Burma
    }
}

AI 焦点

主条目：AI 焦点

AI focuses, defined within /Hearts of Iron IV/common/ai_focuses/*.txt files, are used to tell the game which technology categories and focuses the AI should pick depending on its currently-pursued focuses.

AI peace

peace_ai_desires = {
    dont_puppet_warlord_countries = {
        peace_action_type = { puppet liberate force_government }    #all but take states
        enable = {
            FROM = {
                OR = {
                    tag = SIK
                    tag = PRC
                    tag = GXC
                    tag = YUN
                    tag = SHX
                    tag = XSM
                    tag = MAN
                    tag = MEN
                }
            }
        }
        ai_desire = -1000
    }
}

my_peace_conference = {
    enable = {
        has_government = my_ideology_group
    }
    annex = {
        base = 500
        modifier = {
            factor = 0
            any_allied_country = {
                any_state = {
                    is_owned_by = FROM
                    is_core_of = PREV
                    NOT = {
                        is_core_of = ROOT
                        is_claimed_by = ROOT
                    }
                }
            }
        }
    }
    puppet = {
        base = 100
        modifier = {
            factor = 0
            FROM = { tag = QAT }
        }
    }
    puppet_all = {
        base = 0
    }
    puppet_state = {
        base = 100
        modifier = {
            factor = 0
            FROM.FROM = { tag = QAT }
        }
        modifier = {
            factor = 0
            any_allied_country = {
                ROOT = {
                    is_core_of = PREV
                    NOT = {
                        is_core_of = FROM.FROM
                        is_claimed_by = FROM.FROM
                    }
                }
            }
        }
    }
    take_states = {
        base = 100
        modifier = {
            factor = 0
            any_allied_country = {
                FROM = {
                    is_core_of = PREV
                    NOT = {
                        is_core_of = ROOT
                        is_claimed_by = ROOT
                    }
                }
            }
        }
    }
}

AI strategy plans

AI strategy plans to tell AI what to prioritise depending on circumstances: which advisors to pick, which technologies to research, which AI strategies to apply, which focuses to pick, etc. These are more detailed than general AI strategies, primarily intended to be activated for most of the game to tell the overall plan of a country. Multiple AI strategy plans can be defined and executed at the same time for a country.

AI strategy plans are defined within /Hearts of Iron IV/common/ai_strategy_plans/*.txt files. Within these files, a new strategy plan is done as a new block, the name of which must be the same as the internal ID of the plan.

Within that plan, name = "AI plan's name"和desc = "AI plan's description" decide the name and the description of the strategy plan. This is never intended to be shown to the player, so localising it into different languages is never needed. Instead, this is used within the aiview console command, which tells info to the developer about what AI wants to prioritise.

allowed = { ... } is, similarly to decisions or ideas, is a trigger block checked only at the game's start. This is primarily used to tell which country and DLCs to restrict the strategy plan to.

enable = { ... } is checked each day if the allowed is met. If enable = { ... } is met, then the AI strategy plan will be assigned to the AI regardless of whether enable = { ... } turns false later or not. Commonly, Triggers#has_game_rule is used to make it work with custom game rules deciding what path the AI will pick. is_historical_focus_on is commonly used with the default AI game rule, and country flags can be used for randomisation, by setting up an on_startup to set a random one using random_list

abort = { ... } is checked every day in order to make the AI stop using this AI strategy plan if enable = { ... } is met. Additionally, it must be false in order for the AI strategy plan to be possible to be picked.

ai_national_focuses = { TAG_focus_name_1 TAG_focus_name_2 } is a list of national focuses, separated by whitespaces, in the order that the AI should take them. In this example, the AI will try to take TAG_focus_name_1 first if possible. If it's already taken or TAG_focus_name_1 is impossible to take, then AI will try to take TAG_focus_name_2. If both of the focuses are impossible to take due to being completed or unavailable, then it will move on to other focuses, taking ai_will_do = { ... } into consideration. While following a focus order, it ignores ai_will_do = { ... } values.

focus_factors = { ... } assigns a multiplier to ai_will_do values of the specified focus. An entry in this block looks like TAG_focus_name = 3. In this case, this will make the ai_will_do value of the focus be multiplied by 3, assuming AI strategy plan's weight of 1. If the focus has an ai_will_do value of 4 after applying modifiers, it'll become 12 if AI is following this strategy plan, and get treated as such. And, of course, a factor of 0 will make the focus be never picked without specification in ai_national_focuses. This can serve as a faster-to-write or a more randomised way to make AI follow a political path by making focuses it should never pick have a value of 0.

research = { ... } assigns a multiplier to ai_will_do values of the specified research categories. An entry in this block looks like 火炮=3. In this case, this will make the ai_will_do value of every technology within the category be multiplied by 3, assuming AI strategy plan's weight of 1. Other built-in modifiers still apply, but this will increase the likelihood.

Other blocks that also assign bonuses are ideas = { ... }和traits = { ... }, with the similar formatting. The ideas block is used for individual ideas (such as laws or designers) or advisors (using the idea_token in the entry), while traits are for country leader traits that are assigned to the ideas/advisors.

ai_strategy = { ... } allows an AI strategy to apply when the strategy plan is turned on.

weight = { ... } is a MTTH block assigning an overall weight to the plan. This multiplies each factor within the AI strategy plan by the weight before applying them. A weight of 1.25 will turn a focus factor of 4 into 5 before applying it, for instance. This can be used to make the AI follow the strategy plan more strictly in some cases and less strictly in others.

示例

BHR_historical = {
    name = "Historical plan for BHR"
    desc = "4 focuses in a specific order"
    allowed = {
        tag = BHR
    }
    enable = {
        OR = {
            AND = {
                is_historical_focus_on = yes
                has_game_rule = {
                    rule = BHR_ai_behavior
                    option = DEFAULT
                }
            }
            has_country_flag = BHR_AI_RANDOM_HISTORICAL # Randomly set in on_actions if BHR_ai_behavior is set to RANDOM. Make sure to set that up!
            has_game_rule = {
                rule = BHR_ai_behavior
                option = HISTORICAL
            }
        }
    }
    abort = {
        OMA = {
            OR = {
                has_government = fascism
                has_government = communism
            }
        }
    }
    ai_national_focuses = {
        BHR_focus_name_1
        BHR_focus_name_2
        BHR_focus_name_3
        BHR_focus_name_4
    }
    ideas = {
        BHR_advisor = 3
    }
    traits = {
        fascist_demagouge = 0
    }
    ai_strategy = {
        type = invade
        id = OMA
        value = 200
    }
}
BHR_alternate = {
    name = "Alternative plan for BHR"
    desc = "AI is just set to never do BHR_focus_name_2 and be more likely to do BHR_focus_name_5, especially if after 1937"
    enable = {
        OR = {
            has_country_flag = BHR_AI_RANDOM_ALTERNATE # Randomly set in on_actions if BHR_ai_behavior is set to RANDOM. Make sure to set that up!
            has_game_rule = {
                rule = BHR_ai_behavior
                option = ALTERNATE
            }
        }
    }
    focus_factors = {
        BHR_focus_name_2 = 0
        BHR_focus_name_5 = 2
    }
    weight = {
        modifier = {
            factor = 2
            date > 1937.1.1
        }
    }
    research = {
        artillery = 2
    }
}

AI templates

Scripters/modders are able to specify so called "target templates" that the AI try to reach when upgrading division templates.

Target templates are defined on a "role" level, and it's possible to define a number of different target templates for a specific role. The AI then chooses one of those target templates (based on scripted priorities) and aims for that.

For each role, the AI will select one target template based on the prio, enable, and replace_with parameters. This is referred to as the "currently targeted template".

The AI will then compare the existing division templates it has to find which one best matches the targeted template. This is referred to as the "best match" and the "match score"/"match" refers to how well it matches (100 % match = 1.0).

When the AI decides to upgrade a division template, it will make a copy of the best matching template and modify it so it gets a higher match score (i.e. looks more like the target template). (Note that the AI actually never does in-place modification of templates, it just makes a copy and modifies the copy instead.)

The AI strategy `role_ratio` determines how many divisions the AI wants for each role.

Role arguments:

• role = the role token that this role-level template entry targets. These tokens are defined by script and are targeted by the 'role_ratio' AI strategy.
• blocked_for = { ... } Determines which countries will use this role-level template entry. Both 'blocked_for' and 'available_for' are possible to use. Use one or the other, if you use neither or both, the resulting behavior is undefined. Generally you want to make sure that each country has max one role-level template entry targeting a role. So if you add custom AI templates for e.g. Germany you should make sure that only Germany is allowed for it, and you should also block Germany from using the generic AI templates for the same role.
• upgrade_prio = { ... } An MTTH style block used for weighted-random selection when the AI chooses which role to upgrade templates for. Set it to zero to prevent the AI from spending XP on upgrading templates for this role. Example: If three role-level templates [A, B, C] have upgrade prio [1, 2, 1] respectively, then the probabilities for upgrading each template is [25%, 50%, 25%] respectively.
• enable = { ... } Optional: Whether to evaluate this target template at all. Trigger with country scope. If false, the AI will pretend this target template doesn't exist.

Target template arguments:

• reinforce_prio = Optional: Determines the reinforcement prio of the resulting template. For example, garrison templates should use 0 (low prio) while elite templates should use 2 (high prio). Default 1 (normal prio).
• custom_icon = Optional: Determines whether to use a custom icon for resulting template.
• division_names_group = Optional: Specifies the division name group to use. By default uses the name group of the template "branched off" from.
• upgrade_prio = { ... } The priority of this target template. This is used to determine (deterministically, no randomness involved) which of the target templates is the "currently targeted template".
• enable = { ... } Optional: Whether to evaluate this target template at all. Trigger with country scope. If false, the AI will pretend this target template doesn't exist.
• can_upgrade_in_field = { ... } Optional: Whether to allow upgrading divisions in the field. Trigger with country scope. If false, the AI will not field-upgrade divisions matching this target template. If true, the AI will consider field-upgrading divisions matching this target template to the target template defined by 'replace_with' (assuming they have enough manpower and equipment for it).
• target_template = { ... } 目标模板的「核心内容」：模板的实际内容。
  • support = { ... } The desired support companies. The AI will try to add them to the template if allowed by research etc.
  • regiments = { ... } The desired line regiments. The AI will try to add them to the template if allowed by research etc.

In addition, the optional replace-with chain. If the match score is at least 'replace_at_match', then replace the currently targeted template with 'replace_with', as long as the match score between best matching template and the next target template is at least 'target_min_match':

• replace_at_match = Optional: Match score of this target template.
• replace_with = Optional: Other target template to replace currently targeted template with. Also affects fielded divisions when upgrading in the field.
• target_min_match = Optional: Match score between the best matching template and the target template defined by 'replace_with' has to be at least this high in order for the switch to happen.

示例

infantry_generic = {
    blocked_for = {
        GER
        JAP
    }

    role = infantry

    upgrade_prio = {
        factor = 1

        modifier = {
            factor = 5
        }
    }

    # In this example, the AI will first try to reach a 6-inf (+support) template, before upgrading it to a 9-inf 2-arty (+support) template.
    # Since the 'upgrade_prio' is higher for the first template, that one will be targeted. And when the match score is good enough it will use the 'replace_with' to switch over to the larger template.
    # If two target templates have the same 'upgrade_prio', the first one will be preferred (so order matters in those cases).

    # Target template 1 (the smaller infantry template)
    infantry_1 = {
        reinforce_prio = 0
        custom_icon = 7
        division_names_group = GER_MEC_01

        upgrade_prio = {
            factor = 1

            modifier = {
                factor = 1.5
            }
        }

        enable = {
            date < 1940.3.14
        }

        can_upgrade_in_field = {
            has_equipment = { infantry_equipment > 3000 }
        }

        target_template = {
            support = {
                engineer = 1
                anti_air = 1
                artillery = 1
            }
            regiments = {
                infantry = 6
            }
        }

        replace_at_match = 0.9
        replace_with = infantry_2
        target_min_match = 0.9
    }

    # Target template 2 (the larger infantry template)
    infantry_2 = {
        upgrade_prio = {
            factor = 1

            modifier = {
                factor = 1
            }
        }

        target_template = {

            support = {
                engineer = 1
                recon = 1
                field_hospital = 1
                anti_air = 1
                anti_tank = 1
            }

            regiments = {
                infantry = 9
                artillery_brigade = 2
            }
        }
    }
}

AI equipment

/Hearts of Iron IV/common/ai_equipment/*.txt files are used in order to define the equipment variants that the AI should aim for when assigning modules to tank or ship variants.

A role template is defined as a block within any file in the folder with the name of the block being the same as the name of the role template.
These arguments are used for role templates themselves:

• category = <land|naval|air> decides whether the template is used for tanks, ships or planes respectively.
• roles = { ... } is a list of roles that the templates would have. These can be anything, getting used for the role_ratio AI strategy. AI will try to have one variant for each role it has.
• available_for = { ... } restricts the countries that use this role template to the tags in the list. If unspecified, every country uses them.
• blocked_for = { ... } restricts the countries that use this role template from being the tags in the list. This is only needed if there is no available_for = { ... } block.
• priority = { ... } is a MTTH block that decides the 'importance' of the role template compared to other role templates for spending experience on improving. If there are several role templates with the same roles, the one with the highest priority gets used, otherwise this decides likelihood compared to role templates with different roles.

Additionally, within role templates each individual design is defined as a block with the name of the design being the name of the block. It may be anything, as long as there is no overlap.
These arguments are used within a design definition:

• name = angry_speedboat required to enable the equipment to be used as preset. If not defined, for example German light_tank_artillery_2 will use GER_light_tank_artillery_equipment_2_short localization if defined.
• role_icon_index = 2 is used to assign a specific role icon to a 舰船. This does not work within land equipment. The icons are defined as a part of naval_equipment_role = { ... } within /Hearts of Iron IV/gfx/army_icons/army_icons.txt.
• priority = { ... } is a MTTH block that decides the 'importance' of the design compared to other templates within the role template for spending experience on improving.
• enable = { ... } is a trigger block that decides when AI should aim towards the design.
• allowed_types = { ... } is a list of sub-units that the AI can add to the design. If one is omitted, then the AI would never add it. This can be used to make AI not put units of different varieties in the design, such as putting infantry in a mobile light tank division, slowing it down.
• target_variant = { ... } 指定 AI 应追求的变体。具体来说，以下参数放在它内部：
  • match_value = 5000 is a value that decides how much the template is worth to AI if it's matched.
  • type = light_tank_chassis_0 is the specific equipment type that must be used by the design.
  • modules = { ... } 是装备应具备的模块列表，具体包括：
    • main_armament_slot = tank_flamethrower decides requirements for a specified module slot, in first place. The requirement may be a module category, a specific module, or the word empty. If specifying a module, the greater-than or lesser-than signs can be used in order to require greater or lesser modules: this is decided by the year defined within the module. If lesser is specified, AI aims towards oldest modules, if greater is specified, AI aims towards newest modules. If specifying empty, greater than can be used to ensure it's 不 empty.
    • main_armament_slot = { ... } 允许为某个模块槽位指定更多细节：
      • module = tank_flamethrower decides a module requirement for the slot. This is the exact same formatting as previous main_armament_slot = tank_flamethrower: module categories, modules, or empty are allowed, and the equality signs can be used in the same way.
      • any_of = { ... } is a list of modules or module categories. The module slot must have at least one of them.
      • upgrade = current ensures that, when upgrading a variant to match this design, it must use the same one as on the existing equipment. If the 'greater than' sign is used (>), then it would require AI to upgrade this slot as well.
  • upgrades = { ... } 是该设计应具备的升级列表，具体包括：
    • tank_nsb_engine_upgrade = 3 decides the AI priority that the specified upgrade should have to a fixed number.
    • tank_nsb_engine_upgrade = { ... } is a MTTH block that assigns the AI priority to the specified upgrade dynamically.
• requirements = { ... } is a list of modules that the AI 必须 have. This follows the same formatting as a specified module slot within a target variant's modules block: module = tank_flamethrower, any_of = { ... }, etc. However, this is not tied to a specific slot.
• allowed_modules = { ... } is a list of modules that the AI can use after the requirements in the target variant are met. If a module isn't here, it'll never be picked. The modules specified first take priority over the later ones.

示例

BHR_light_tanks = {
    category = land

    available_for = {BHR}

    roles = {
        land_light_tank
    }

    priority = {
        factor = 1000
    }

    great_war_tank_default = {
        priority = {
            factor = 1
            modifier = {
                has_tech = basic_light_tank_chassis
                factor = 0 #let's not waste XP here
            }
        }

        target_variant = {
            match_value = 1000
            type = light_tank_chassis_0
            modules = {
                main_armament_slot = tank_heavy_machine_gun
                turret_type_slot = tank_light_one_man_tank_turret
                suspension_type_slot = tank_bogie_suspension
                armor_type_slot = tank_riveted_armor
                engine_type_slot = tank_gasoline_engine
                special_type_slot_1 = empty
                special_type_slot_2 = empty
                special_type_slot_3 = empty
                special_type_slot_4 = empty
            }
            upgrades = {
                tank_nsb_engine_upgrade = 3
                tank_nsb_armor_upgrade = {
                    base = 1
                    modifier = {
                        add = 1
                        has_war = yes
                    }
                }
            }
        }

        allowed_modules = {
            tank_heavy_machine_gun
            tank_light_one_man_tank_turret
            tank_bogie_suspension
            tank_riveted_armor
            tank_gasoline_engine
        }
    }
}