sc2-localization-and-text

Audit StarCraft II localization files for missing keys and locale parity.

3|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ShadowDragonSC2/Base.SC2Data --skill sc2-localization-and-text-shadowdragonsc2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc2-localization-and-text
Source: https://github.com/ShadowDragonSC2/Base.SC2Data/tree/main/.koda/skills/sc2-localization-and-text
Command: npx skills add https://github.com/ShadowDragonSC2/Base.SC2Data --skill sc2-localization-and-text-shadowdragonsc2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

StarCraft II projects often struggle with missing, inconsistent, or outdated localized strings across multiple language folders. This Skill provides guidance and tooling concepts to audit GameStrings.txt, GameHotkeys.txt, ObjectStrings.txt, and TriggerStrings.txt across xxXX.SC2Data/LocalizedData.

Core Features & Use Cases

  • Inspect per-language LocalizedData files for missing keys, duplicates, and blank values.
  • Validate consistency of UI text, tooltips, and hotkeys across locales.
  • Use the Localization Editor SC2 KSP tool and its CLI to diagnose and repair localization issues across a map or mod.

Quick Start

Run the Localization Editor SC2 KSP to scan and align texts across all locales in your map’s LocalizedData folders.

Frequently Asked Questions about sc2-localization-and-text

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find missing translations in StarCraft II GameStrings.txt files?

To find missing translations in StarCraft II GameStrings.txt files, you can audit per-language LocalizedData folders to identify missing keys, blank values, and cross-language parity gaps using the Localization Editor SC2 KSP tool.

What is the best way to validate localization consistency across SC2 map locales?

The best way to validate localization consistency across SC2 map locales is to audit GameStrings.txt, GameHotkeys.txt, ObjectStrings.txt, and TriggerStrings.txt across xxXX.SC2Data/LocalizedData to check for duplicates, missing translations, and malformed entries.

How do I fix blank values and malformed entries in SC2 TriggerStrings.txt?

To fix blank values and malformed entries in SC2 TriggerStrings.txt, run the Localization Editor SC2 KSP CLI for structured diagnostics, validating keys and values to repair localization issues across your map or mod.

Do I need the Localization Editor SC2 KSP tool to audit SC2 GameHotkeys.txt?

Yes, auditing SC2 GameHotkeys.txt requires the Localization Editor SC2 KSP tool and its CLI, which provide the structured validation needed to diagnose key parity, missing translations, and hotkey inconsistencies across localized data.

Can I check cross-language parity for ObjectStrings.txt across all xxXX.SC2Data folders?

Yes, you can check cross-language parity for ObjectStrings.txt across all xxXX.SC2Data/LocalizedData folders by scanning for missing keys, duplicates, and blank values to ensure UI text and tooltip consistency across all supported locales.

What types of localization errors does an SC2 map text audit detect?

An SC2 map text audit detects localization gaps including missing keys, duplicate entries, blank values, malformed entries, and cross-language inconsistencies across GameStrings, GameHotkeys, ObjectStrings, and TriggerStrings files.