Wiki

effect · set_mio_design_team_assign_cost

Definition

  • Supported scope:INDUSTRIAL_ORG
  • Supported target:THIS, ROOT, PREV, FROM, OWNER, CONTROLLER, OCCUPIED, CAPITAL

Description

Set the daily PP cost to assign to research in the military industrial organization in scope.
This changes the base value. Modifiers will still apply over it.
Input value cannot be negative.
ex:
mio:my_mio = {
  set_mio_design_team_assign_cost = 0.3
  set_mio_design_team_assign_cost = var:my_number_var
}

实战 · 配合 · 坑

实战内容由 AI 生成,并已对照 vanilla 命令词表校验 —— 请当作起点而非权威依据。上方的定义节才是游戏自带文档原文。

实战用法

当你希望某个军工组织的设计团队指派费用在特定事件或决议后发生永久性变化时,使用此 effect 直接覆盖基础值。典型场景包括:某国完成特定科技或达成国策后,让旗下 MIO 的每日政治点消耗降低,以体现工业成熟度提升的奖励。

# 在某个决议完成后,将指定 MIO 的指派基础费用调整为更低值
complete_national_focus = {
    mio:my_armor_mio = {
        set_mio_design_team_assign_cost = 0.1
    }
}

配合关系

  • [add_mio_design_team_assign_cost](/wiki/effect/add_mio_design_team_assign_cost):若需要在现有基础值上做相对增减而非直接覆盖,应优先考虑此命令;两者搭配可先 set 到基准值再做细粒度 add 调整。
  • [set_mio_industrial_manufacturer_assign_cost](/wiki/effect/set_mio_industrial_manufacturer_assign_cost):同类"set 指派费用"命令,针对的是工业制造商角色,两者常在同一 MIO 初始化块中并排使用,统一管理不同任务模式的费用。
  • [is_mio_assigned_to_task](/wiki/trigger/is_mio_assigned_to_task):在执行费用调整前用作条件检查,确保仅在 MIO 处于特定任务状态时才覆盖费用,避免逻辑冲突。
  • [has_mio_size](/wiki/trigger/has_mio_size):常与之配合,根据 MIO 当前规模等级决定是否触发费用覆写,实现"规模越大、指派费越低"的阶梯式设计。

常见坑

  1. 误用负值:该 effect 明确不接受负数输入,若通过变量传入一个可能为负的 var:xxx,游戏不会报错但行为未定义,务必在赋值前用 trigger 或 clamp 保证变量非负。
  2. 混淆 set 与 add 的覆盖逻辑set_mio_design_team_assign_cost 直接替换基础值,不是在原值上叠加;新手常在循环事件中反复调用,导致费用被重置而非累计降低,需要先读取当前值再决定用 set 还是 add。

Hands-On Notes

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.

Hands-On Usage

Use this effect to directly override the base assignment cost of a Military Industrial Organization's design team when you need permanent changes to occur following specific events or decisions. Typical scenarios include reducing the daily political point consumption of an MIO following a nation's completion of certain technologies or national focuses, reflecting rewards for improved industrial maturity.

# After completing a decision, adjust the assignment base cost of the specified MIO to a lower value
complete_national_focus = {
    mio:my_armor_mio = {
        set_mio_design_team_assign_cost = 0.1
    }
}

Synergy

  • [add_mio_design_team_assign_cost](/wiki/effect/add_mio_design_team_assign_cost): When you need to make relative increases or decreases to the existing base value rather than direct replacement, prioritize this command instead. The two can be combined by first setting to a baseline value and then making fine-grained adjustments with add.
  • [set_mio_industrial_manufacturer_assign_cost](/wiki/effect/set_mio_industrial_manufacturer_assign_cost): A similar "set assignment cost" command targeting the industrial manufacturer role. Both are commonly used side-by-side in the same MIO initialization block to uniformly manage costs across different task modes.
  • [is_mio_assigned_to_task](/wiki/trigger/is_mio_assigned_to_task): Use as a conditional check before executing cost adjustments to ensure the cost override only applies when the MIO is in a specific task state, avoiding logical conflicts.
  • [has_mio_size](/wiki/trigger/has_mio_size): Frequently paired with the above, determining whether to trigger cost rewriting based on the MIO's current size tier, enabling a tiered design where "larger MIOs have lower assignment costs."

Common Pitfalls

  1. Misusing negative values: This effect explicitly does not accept negative inputs. If a potentially negative var:xxx is passed through a variable, the game will not error but behavior is undefined. Always ensure the variable is non-negative using a trigger or clamp before assignment.
  2. Confusing the override logic of set versus add: set_mio_design_team_assign_cost directly replaces the base value rather than stacking on top of the original. Beginners often repeatedly call this in looping events, causing the cost to be reset rather than cumulatively reduced. You must read the current value first before deciding whether to use set or add.