How to translate a Wolf RPG game to English (full walkthrough)

Wolf RPG (ウディタ, WOLF RPG Editor) is the freeware engine behind a huge chunk of Japanese indie and doujin RPGs. Unlike RPG Maker, it packs scripts and map data into custom binary archives, so standard text-injection tools fall over on it. This guide shows how to translate a Wolf RPG game to English end-to-end with RuneTranslate — .wolf archive handling, .dat / .mps string extraction, and the difference between V2 and V3 archives.

What you need

• RuneTranslate for Windows— free; every engine and provider is unlocked.
• A Wolf RPG game folder — the directory with Game.exe and one or more .wolf archives (or already-extracted .dat / .mps files).
• A target language — English, Spanish, French, German, Portuguese, Russian, Chinese, Italian, Turkish, Vietnamese, and 20+ more.
• One translation provider. Free Google Translate works out of the box; DeepL has a free tier; OpenAI and Anthropic are bring-your-own-key. For Wolf RPG, DeepL is usually a good balance — much of the text is narrative, not stylized speech.

Step 1: Open the game folder

Launch RuneTranslate, click New project, and point it at the Wolf RPG game directory. Engine detection runs automatically. If the game ships packed .wolf archives (the common case), the bundled UberWolfCli sidecar — an MIT-licensed Wolf RPG tool shipped inside the installer — decrypts them into a per-project workspace under %APPDATA%/RuneTranslate/wolf-workspace/. Your original game folder is never touched.

V2.x archives are reliable and fast. V3.x games changed both the archive crypto and the data layout, so RuneTranslate marks V3 projects best-effort: the flow still works, but verify the exported build runs before you rely on it.

Step 2: How Wolf RPG text is extracted

Wolf RPG keeps game text in two binary formats:

• .mps files — map data. This is where most in-game dialogue lives: NPC lines, choices, and map-event text, plus map names.
• .dat files — the databases (items, characters, skills, system messages) and CommonEvent.dat. These hold names, descriptions, and shared event scripts rather than the bulk of the dialogue.

For V2.x games a heuristic length-prefixed scanner walks each file, reads candidate strings, and validates them (trailing-null framing, plausible byte length, real text rather than binary noise). V3.x games (Wolf 3.x, UTF-8) store their data LZ4-compressed with a command-walked layout that the flat scanner can't read, so RuneTranslate ships a separate structural V3 parser that decompresses the blocks and walks the event-command lists to find the real dialogue.

Step 3: Translate

Pick a provider and run. DeepL is fast and clean for narration; OpenAI or Anthropic read best on stylized speech; free Google Translate covers menus and short lines. A full game costs roughly a dollar or two in API credit on a paid LLM, or $0 on the free scrapers. Glossary your recurring terms first — see Glossary 101.

On the free tier translation is modestly throttled — about 2x slower on the AI/LLM providers, less on the free scrapers (lower concurrency, smaller batches, a short pause between batches). The output quality is identical; paid tiers just run at full speed and add translation memory and provider routing.

Step 4: Repack and export

Click Export. RuneTranslate writes the translated strings back into the .dat / .mps files, then UberWolfCli repacks them into a .wolf archive. Length preservation is handled automatically, per string— there is no toggle to set. Wolf indexes its message boxes by line and reads some render parameters relative to the end of a string, so any line whose control structure or line count a translation would disturb is written back in its original Japanese to keep the game from crashing. On a heavily control-coded game that means a small share of lines (roughly a few percent) stay in the source language by design.

The output is a fresh copy of the game folder with the translated archive plus the original executable, dropped in the location you choose. Run Game.exe and you have a playable translated Wolf RPG game.

Known limitations

• V3.x support is best-effort — verify the exported build launches before you rely on it.
• A few percent of heavily control-coded lines auto-revert to Japanese rather than risk a crash; touch those up by hand only if you can keep the control bytes intact.
• Image / texture text (logos, hand-drawn UI) is pixel work and isn't translated — outside machine-translation scope.

Why this is easier than the old way

The manual route meant extracting archives with UberWolfCli or WolfDec, hand-running a scanner over the binaries, pasting strings into DeepL or a spreadsheet, then writing them back without breaking byte alignment or crashing the message engine. RuneTranslate folds that whole chain into a few clicks and keeps the editor open so you can fix any line the machine got wrong.

See the Wolf RPG engine page for the full feature list, read the RPG Maker guide for a related engine, or download RuneTranslate and try it on a real game.