File format · .s2qh
StarCraft II Localization Header and Localization File Repair
A broken MPQ header or damaged GameStrings.txt table can hide a StarCraft II map's text or stop it loading. See what is recoverable and how we repair it.
StarCraft II keeps its text in a layer of its own. Unit names, tooltips, campaign dialogue, and menu labels all live in string tables that sit apart from the game logic. When that layer breaks, a map may still load while its text collapses into raw token IDs, or the archive may refuse to open at all. Either way the damage is usually fixable, and we repair these files regularly.
The localization layer inside StarCraft II files
Blizzard Entertainment shipped StarCraft II: Wings of Liberty in 2010 as a multilingual game. Rather than hard-code its text, the engine resolves every visible string through a token. A string table maps each token to the wording for one locale, such as enUS, koKR, or ruRU.
These tables are plain text files, most notably GameStrings.txt, organized in locale-specific folders. The StarCraft II Editor exposes them through its Text module, where map and mod authors manage strings for each language in one place.
Maps, mods, and replays are all Mo'PaQ, or MPQ, archives. When people refer to a localization header, they usually mean the archive header at the front of a localized map or mod. Locale data stored beside it tells the game which string tables to load. Blizzard has never published a formal public specification for these internals, so community MPQ documentation and the editor itself are the practical references.
How is the header structured?
Community MPQ format documentation describes the container precisely. An archive begins with the signature bytes 4D 50 51 1A, readable as the letters MPQ followed by a trailing byte. The header records the archive size, the format version, and the position and size of two tables.
Those two tables matter most for recovery. The hash table maps file names to archive slots, and the block table records where each file's data sits along with its flags. Files inside are found by hashed names rather than plain directory entries. That is why a damaged table makes the contents invisible even when the data itself is intact.
GameStrings.txt is simple by comparison: lines of the form Token=Value, one string per line. A missing or duplicated token breaks only that entry, while a broken archive header can hide every file at once. Newer game installs keep Blizzard's own data in the company's CASC storage system, but files you create or import in the editor remain MPQ archives.
Why do localization files stop loading?
Most damage traces back to an interrupted write. If the editor crashes or the machine loses power mid-save, the archive header or block table can be left half-written, and the game refuses the whole file.
Truncation is the other common cause. A map cut short by a failed download, a full disk, or an aggressive cloud-sync tool no longer matches its own recorded sizes. Bad sectors on an aging drive produce the same result.
Two softer failures mimic corruption. A map published without a locale table for the player's language shows raw token IDs instead of words. Dropping a dependency mod also strands every token that mod supplied, so the text vanishes even though nothing is technically broken.
What can be recovered from a damaged archive?
Header damage with intact payload blocks is the good case. Terrain, triggers, imported assets, and complete string tables can usually be extracted and repacked into a clean archive.
When the block table is destroyed, we scan the raw stream and carve files out individually. Success then depends on how much of the data region survived. String-level recovery adds another option: if one locale's table is lost, a complete sibling locale can be rebuilt and its tokens mapped back.
Replays respond to the same approach. Even when playback fails, the version and player details stored early in the file are often still readable.
How does the recovery process work?
We always work on a copy, never the original. A failed attempt then costs nothing, because the damaged file stays untouched.
- Verify the header. We check the signature and header fields, then measure the recorded sizes against the actual file. This tells us whether the archive is truncated or merely has a broken table.
- Rebuild the tables. We repair or reconstruct the hash and block tables so the contents become addressable again. Where a table cannot be salvaged, we carve the payload directly from the raw stream instead.
- Extract and audit the string tables. We pull out GameStrings.txt for every locale and check it token by token. One missing token resurfaces later as raw text in game, so the audit is thorough.
- Fill the gaps. Missing tokens are restored from dependency data or mapped across from a sibling locale that survived intact.
- Repack and test. We rebuild a valid archive and open it in the editor to confirm it loads and the text resolves before returning it.
FAQ
Where are StarCraft II localized strings stored?
In files you create, strings live in GameStrings.txt tables inside the MPQ archive of the map or mod. The installed game keeps its own copies in Blizzard's CASC storage, which is best left untouched.
Why does my map show token IDs instead of text?
The game could not resolve those tokens. Either the locale table for the player's language is missing, or a dependency that supplied the strings was removed. Both are repairable without rebuilding the map.
Can a corrupt map, mod, or replay be saved?
Usually, if the data region survived. A broken header often just hides intact content, and the tables it points to can be rebuilt from the file itself.
Does Blizzard publish the header specification?
Not in full. Community MPQ documentation has filled most of the gap over many years. Blizzard's own documentation is authoritative wherever it speaks, and we verify everything against real files.
Is it safe to keep working after recovery?
Yes. Treat the recovered file as your new master, keep the damaged original as a backup, and let the editor save normally from that point on.
If a StarCraft II file is refusing to open, or showing token IDs where words should be, send it to us for a free evaluation. Our engineers will inspect the archive, tell you what is recoverable, and quote the repair before any work begins.
Send us your .s2qh file for a free evaluation
Our recovery engineers will tell you exactly what can be recovered — at no cost. There is no charge if we cannot recover your data.
Start a free evaluation