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, Wolf RPG packs scripts and map data into custom binary archives, which means standard text-injection tools fall over on it. This guide walks through translating a Wolf RPG game end-to-end with RuneTranslate, including the bits that historically gave translators the most trouble: .wolf archive handling, .dat / .mps string extraction, and V2 vs V3 archive differences.

What you need

• RuneTranslate for Windows— v0.3.4 or later.
• A Wolf RPG game folder. This is the directory containing Game.exe and one or more .wolf archive files (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 key. Free Google Translate works out of the box; DeepL has a free tier; OpenAI and Anthropic are BYOK. For Wolf RPG, DeepLis usually the best balance — the dialogue is mostly 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 with packed .wolf archives (most common), the bundled UberWolfClisidecar — an MIT-licensed Wolf RPG tool we ship inside the installer — decrypts them transparently into a per-project workspace under %APPDATA%/RuneTranslate/wolf-workspace/<projectId>/. Your original game folder is never touched.

For V2.x archives this is reliable and fast. For V3.x archives Wolf RPG's encryption changed and RuneTranslate marks the project as best-effort— the translation flow still works, but you'll want to verify the exported build runs before redistributing.

Step 2: How strings get extracted

Wolf RPG stores game text in two binary formats:

• .dat files — CommonEvent script blocks. These hold most dialogue, menu strings, and item descriptions.
• .mps files — map data. These hold map-name strings, NPC dialogue, and map-specific event scripts.

Both are length-prefixed binary formats. RuneTranslate uses a heuristic length-prefixed string scanner that walks each file, reads candidate strings, and validates them against Japanese-text patterns (ratio of CJK characters, plausible byte-length, no binary noise). The result is a clean list of translatable strings without false positives from arbitrary byte runs.

Step 3: Translate

Pick a provider and run. For a typical 5,000-line Wolf RPG game on Supporter tier:

• DeepL free tier— ~15–20 minutes, $0/month if you stay under the 500k char/month limit.
• OpenAI gpt-4o— ~25 minutes, roughly $0.30–$0.80 depending on dialogue density.
• Anthropic Claude— ~30 minutes, roughly $0.40–$1.20. Best for games with stylized speech.
• Free Google Translate— ~20 minutes, $0. Quality is noticeably lower for dialogue but fine for items + menus.

Free-tier RuneTranslate is throttled to ~3–4x slower than these numbers (concurrency = 2, half-size batches, 400ms sleep between batches). Same output quality.

Step 4: Repack and export

Click Export. RuneTranslate writes the translated strings back into the .dat / .mps files, then UberWolfCli repacks them into a .wolfarchive. There's an option called Length-preserving writeback that pads the translated strings to match the original byte length; leave it on for V3 archives where some engine versions are picky about exact file size, leave it off for V2 where it's safe to save space.

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

Known limitations

• V3.x archives may need manual review in edge cases. We're actively improving V3 support.
• Heavily-customized UberRPG plugins with non-standard string layouts may need a hand-fix pass.
• Image / texture text (logos, hand-drawn UI) is not translated — that's pixel work, outside MT scope.

Why this is easier than the old way

Before tools like RuneTranslate, Wolf RPG translation involved manual archive extraction with UberWolfCli or WolfDec, hand-running a regex scanner over the extracted binaries, pasting strings into DeepL or a spreadsheet, then putting them back without breaking byte alignment. Hours of work per game. RuneTranslate compresses the whole flow into a few clicks while keeping the editor open so you can hand-fix lines the MT got wrong.

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