Wiki

effect · add_history_entry

Definition

  • Supported scope:(none)
  • Supported target:none

Description

add_history_entry = {
key = custom_localized_key
subject = "Custom String (not localized)"
allow = yes/no (allow medal award)
}

实战 · 配合 · 坑

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

实战用法

add_history_entry 常用于记录重大外交事件、战争罪行裁决或特殊历史节点，让玩家在事件日志或人物档案中看到可追溯的行为记录。例如在一个审判类事件中，当玩家选择定罪某位将领时，可以将该决定写入历史条目：

option = {
    name = war_tribunal.1.a
    add_history_entry = {
        key = war_tribunal_convicted
        subject = "General Schmidt convicted of war crimes"
        allow = yes
    }
}

配合关系

由于当前 scope 下白名单中暂无其他已记录的配套 effect 或 trigger 命令，无法列出经过验证的交叉引用。建议在使用本 effect 时，结合事件（event）或决策（decision）框架中的常规控制流来触发它，避免引用未经证实的命令。

常见坑

  1. subject 字段填写本地化键而非字符串：subject 接受的是未经本地化的原始字符串，如果误填本地化键名，游戏会将键名本身直接显示在日志里，而不会自动翻译，导致显示异常。
  2. allow 字段用途误解：新手容易忽略 allow 字段与勋章授予（medal award）相关的含义，将其当作普通的条件开关随意填写，实际上该字段控制的是特定勋章奖励逻辑是否触发，不能替代 trigger 条件判断。

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

add_history_entry is commonly used to log significant diplomatic events, war crimes verdicts, or special historical milestones, allowing players to see traceable records of actions in event logs or character profiles. For example, in a tribunal event, when the player chooses to convict a general, that decision can be written to a history entry:

option = {
    name = war_tribunal.1.a
    add_history_entry = {
        key = war_tribunal_convicted
        subject = "General Schmidt convicted of war crimes"
        allow = yes
    }
}

Synergy

Currently, there are no other documented companion effects or triggers in the whitelist under this scope, making it impossible to provide verified cross-references. When using this effect, it is recommended to trigger it in conjunction with standard control flow within event or decision frameworks, and avoid referencing unverified commands.

Common Pitfalls

  1. Filling the subject field with localization keys instead of strings: The subject field accepts raw unlocalized strings. If you mistakenly enter a localization key name, the game will display the key name itself directly in the log without automatic translation, resulting in display errors.

  2. Misunderstanding the allow field purpose: Beginners often overlook the allow field's connection to medal award logic and treat it as a simple conditional toggle. In reality, this field controls whether specific medal reward logic triggers, and cannot replace trigger condition checks.