sc2-localization-and-text

Audit StarCraft II localization files for missing keys and placeholder issues.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/KimPlaybit/Ultrasikism --skill sc2-localization-and-text
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc2-localization-and-text
Source: https://github.com/KimPlaybit/Ultrasikism/tree/main/.agents/skills/sc2-localization-and-text
Command: npx skills add https://github.com/KimPlaybit/Ultrasikism --skill sc2-localization-and-text

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

StarCraft II maps and mods rely on a set of localized text assets (GameStrings.txt, GameHotkeys.txt, ObjectStrings.txt, TriggerStrings.txt). This Skill helps maintain translation parity, catch missing translations, and validate correct formatting across xxXX.SC2Data/LocalizedData folders.

Core Features & Use Cases

  • Localization auditing: identify missing keys, placeholder issues, and duplicate entries across languages.
  • Consistency validation: ensure translations align with source strings and preserve placeholders.
  • Use Case: QA engineers or map authors audit localization before release to guarantee multilingual support and accurate tooltips.

Quick Start

Run a localization audit on enUS.SC2Data/LocalizedData to surface missing keys and misformatted entries.

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 audit StarCraft 2 localization files for missing translations?

To audit StarCraft 2 localization files, run a check across xxXX.SC2Data/LocalizedData folders to surface missing keys, duplicate entries, and misformatted text in GameStrings.txt and TriggerStrings.txt. This validates translation parity across multiple languages before release.

What is the best way to ensure placeholder consistency across SC2 GameStrings translations?

The best way to ensure placeholder consistency across SC2 GameStrings translations is to validate that translated text aligns with source strings and preserves placeholders. This catches formatting issues and maintains parity across multilingual maps and mods.

Can I check cross-language parity for ObjectStrings.txt and GameHotkeys.txt simultaneously?

Yes, you can check cross-language parity for ObjectStrings.txt and GameHotkeys.txt simultaneously. The localization audit validates keys and preserves placeholders across all four core SC2 text files within the xxXX.SC2Data/LocalizedData directory structure.

How do I fix missing keys in TriggerStrings.txt before releasing a SC2 mod?

To fix missing keys in TriggerStrings.txt before releasing a SC2 mod, run a localization audit on your enUS.SC2Data/LocalizedData folder. This identifies missing translation entries and validates correct formatting across all supported languages.

Does the SC2 localization audit support multiple languages beyond enUS?

Yes, the SC2 localization audit supports multiple languages beyond enUS. It processes xxXX.SC2Data/LocalizedData folders to perform consistency checks, translations, and cross-language parity validation across all supported StarCraft 2 locales.