Wiki

effect · add_mio_size_up_requirement_factor

Definition

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

Description

Add to the factor applied to funds required to size up in the military industrial organization in scope.
This changes the base value. Modifiers will still apply over it.
Value can be negative to reduce assign cost but final value cannot be negative (capped at 0, no error raised)
ex:
mio:my_mio = {
  add_mio_size_up_requirement_factor = 0.2
  add_mio_size_up_requirement_factor = -0.1
  add_mio_size_up_requirement_factor = var:my_number_var
}

实战 · 配合 · 坑

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

实战用法

当你希望通过剧本事件或国策奖励某个军工组织,使其升级所需资金的倍率永久降低(或临时提高)时,可使用此 effect。典型场景是:玩家完成某项科研后,触发事件让指定 MIO 的扩编成本减少,从而鼓励玩家持续投入。

# 某国策完成后,降低特定 MIO 的升级资金需求
complete_national_focus = {
    ...
    mio:ger_krupp_mio = {
        add_mio_size_up_requirement_factor = -0.15
    }
}

配合关系

  • [set_mio_size_up_requirement_factor](/wiki/effect/set_mio_size_up_requirement_factor) — 若需要将倍率重置为绝对值而非相对叠加,应先用 set 覆盖基准值,再用 add 做微调,两者配合控制精度。
  • [add_mio_funds](/wiki/effect/add_mio_funds) — 同时补充 MIO 的当前资金,确保在降低升级门槛的同时,组织有足够资金立即执行升级动作。
  • [has_mio_size](/wiki/trigger/has_mio_size) — 在执行 add 之前用此 trigger 判断 MIO 当前规模,避免对已达上限或尚未解锁的组织浪费执行。
  • [has_mio_flag](/wiki/trigger/has_mio_flag) — 搭配 flag 做去重保护,防止同一奖励被多次触发导致倍率因子无限叠加。

常见坑

  1. 误以为最终值可以无限为负:此 effect 只改变基础因子,游戏会将最终计算结果下限钳制到 0,不会报错也不会给出任何提示,导致玩家以为多次叠加负值能无限压低成本,实际上超过下限后的叠加完全无效。
  2. 在非 INDUSTRIAL_ORG scope 下调用:该 effect 仅在 MIO scope 内有效,若在 country 或 state scope 下直接书写(忘记用 mio:xxx = { } 包裹),脚本会静默失败或报 scope 错误,调试时难以定位。

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

When you want to permanently reduce (or temporarily increase) the funding multiplier required for a military industrial organization to upgrade through scripted events or national focus rewards, this effect is your tool. A typical scenario involves: after the player completes a research project, triggering an event that reduces the expansion cost of a specified MIO, thereby encouraging continued investment.

# After a national focus completes, reduce the upgrade funding requirement for a specific MIO
complete_national_focus = {
    ...
    mio:ger_krupp_mio = {
        add_mio_size_up_requirement_factor = -0.15
    }
}

Synergy

  • [set_mio_size_up_requirement_factor](/wiki/effect/set_mio_size_up_requirement_factor) — If you need to reset the multiplier to an absolute value rather than stacking additively, first use set to establish a baseline, then use add for fine-tuning; combining both allows precise control.
  • [add_mio_funds](/wiki/effect/add_mio_funds) — Simultaneously supplement the MIO's current funds to ensure that while lowering the upgrade threshold, the organization has sufficient capital to execute the upgrade action immediately.
  • [has_mio_size](/wiki/trigger/has_mio_size) — Before executing add, use this trigger to check the MIO's current scale, avoiding wasted execution on organizations that have already reached their cap or haven't been unlocked yet.
  • [has_mio_flag](/wiki/trigger/has_mio_flag) — Pair with flags for deduplication protection, preventing the same reward from being triggered multiple times and causing the multiplier factor to stack infinitely.

Common Pitfalls

  1. Assuming the final value can be negative without limit: This effect only modifies the base factor; the game clamps the final calculated result to a minimum of 0, produces no error, and offers no feedback, leading players to believe that stacking negative values multiple times can infinitely suppress costs when in reality, any stacking beyond the floor has no effect whatsoever.
  2. Calling outside an INDUSTRIAL_ORG scope: This effect is only valid within an MIO scope; if written directly in a country or state scope (forgetting to wrap it with mio:xxx = { }), the script fails silently or throws a scope error, making it difficult to locate during debugging.