订阅以下载
Localization Extractor

Extracts translation files for the selected mod and saves them inside the mod folder.
The result is written to `[selectedMod]/Languages/[selectedLang]`.
Warning: the tool clears that target language folder and writes fresh files — make a backup if you want to keep existing translations.
If you notice any missing entries, please let me know.

---

It operates differently from RimWorld’s original extractor, so the order of strings may differ; required entries should still be present.
The extractor includes strings that are available at runtime — if an optional mod is not enabled, its strings will not be extracted.

• Optional (recommended): create a new language folder beforehand to avoid overwriting: `Mods/[SelectedMod]/Languages/<new-lang-folder>`.
  
• Enable this extractor mod together with the mod whose strings you want to extract. Also enable any possible dependencies (mods referenced with `IfModActive`) for a more complete extraction.
  
• Start RimWorld with those mods enabled. An extra button appears in the main menu to choose the target mod.
  
• After confirmation, the extractor writes files to `[selectedMod]/Languages/[selectedLang]`. It clears that folder and writes fresh files.

This shows an *optional* mod reference — not a required dependency. The extractor includes those extra strings only when the referenced mod is enabled.


Explanation:

• `IfModActive="VanillaExpanded.VPsycastsE"` means "if *Vanilla Psycasts Expanded* is present".
  
• When that mod is present, the target mod may load extra content from `1.5/Mods/VanillaPsycastsExpanded` which can add translation keys.
  
• The extractor only includes those keys if the optional mod is enabled at runtime.

Some mods apply patches to another mod’s defs (for example, rename an item or replace a label). Current extractor does not copy those patched strings into the language folder when you extract the patching mod itself.

How it behaves now:

• If Mod B contains a patch that changes strings in Mod A, extracting Mod B will NOT produce the new/changed strings for Mod A.
  
• If you extract Mod A, the patched strings will appear in Mod A’s extracted language files (because the changes are present at runtime in Mod A’s final data).

This behavior is suboptimal because extracting Mod B does not include the strings it injects into other mods. Planned improvement: add support so that extracting a mod will also gather strings it injects via patches (so Mod B’s extraction would include its patch-provided strings).