Supported engine · RPG Developer Bakin
RPG Developer Bakin translator — translate Bakin JP games end-to-end
RPG Developer Bakin (SmileBoom, the successor to SMILE GAME BUILDER) powers a growing wave of Japanese indie RPGs. RuneTranslate translates the text those games carry in their data.rbpack: the whole database (item, skill, character, class, condition, and status names + descriptions) and event / scenario command text. A bundled sidecar drives the game's own engine to read and write the data accurately, then applies your translation through Bakin's built-in localization, set as the game's default language — so the exported build boots straight into your translation, with no in-game language menu to switch. (On engine builds without that localization API, older ones included, RuneTranslate writes the translated text directly, with the same result.) 3D models, textures, and audio are untouched; text compiled into a game's C# battle/menu scripts is out of scope. Verify on a real game before you rely on it.
Bakin databases reuse the same character, item, skill, and place names across hundreds of database entries and event lines, and providers will rephrase them inconsistently from batch to batch. Glossary the protagonist and party, recurring NPCs, key locations, and any signature skill or status term up front so every database field and event message renders them identically.
How to translate RPG Developer Bakin
- STEP 1
Open the Bakin game folder
Point RuneTranslate at the game directory (the one containing data\data.rbpack and bakinplayer.exe). Engine detection recognises the BKNPAK container automatically; the bundled sidecar handles everything — no separate install.
- STEP 2
Extract database + event text
RuneTranslate reads the game's own data to list every translatable source-language string (Japanese by default; set any supported source language per project) — database names and descriptions plus event / scenario command text — grouped by type (items, skills, characters, events) so it's easy to work through.
- STEP 3
Translate via your preferred provider
DeepL is a strong default for narrative dialogue; OpenAI GPT-4o or Anthropic Claude handle stylized speech and onomatopoeia better. Free Google Translate or a local model (Ollama / LM Studio) covers menu strings and item names. Provider routing can split short strings to a cheap lane.
- STEP 4
Export a localized build
On export, RuneTranslate copies the game and writes your translation into Bakin's own localization data, set as the game's default language. Run the exported game and it opens already translated — the engine renders your text natively, no language menu needed.
Supports
- Database text — item / skill / character / class / condition / status names + descriptions
- Event & scenario command text (messages, choices, names)
- Applied through Bakin's built-in localization, forced as the game's default language (written directly on builds without it, older ones included)
- Reads/writes via the game's own engine for accurate, version-tolerant round-trips
- Per-project workspace in the app's game cache (your app data folder by default, movable to another drive in Settings)
Limitations
- 3D models, textures, and audio assets are not translated (out of scope by design)
- Text compiled into a game's C# battle / menu scripts is not covered
- Where Bakin's localization layer is used, the original text stays bundled as the fallback base language; verify the exported build on a real game

