Translator++ Ver. 8.3.25 - Stable SRPG Studio & Bakin Parsers, MO File Support, and more! 🚀

Hello fellow translators! 👋

This month, I am absolutely thrilled to announce a massive update for Translator++. I’ve been hard at work, and this month’s release brings major overhauls and quality-of-life improvements to three different engines/formats!

Here are the highlights of what’s new:

⚔️ SRPG Studio Alternative Parser

For those who might not know, SRPG Studio is a fantastic 2D engine designed specifically for creating grid-based, turn-based tactical RPGs (think Fire Emblem style games).

While we already had a parser for SRPG Studio, I knew it could be better. So, I’ve built a brand-new Alternative Parser from the ground up!

With this new parser, you can expect:

• Blazing Speed: It is significantly faster and more stable than the previous parser.

• Up-to-Date Support: Fully supports the latest SRPG Studio games (up to v1.317).

• Zero Hassle: The entire process from project creation to translation injection is completely seamless. No manual decrypting or decompiling required!

🎥 Check out the new SRPG workflow in action here:

🏰 RPG Developer Bakin Alternative Parser

RPG Developer Bakin is the spiritual successor to the RPG Maker engine, allowing developers to create beautiful 3D RPGs.

Previously, translating Bakin games required you to own and use the Bakin Editor to manually extract the localization texts. I’m happy to announce that this is no longer the case!

With the new Bakin Alternative Parser:

• No Bakin Editor Required: You can translate games directly, even if you don’t own the engine!

• Streamlined Proxy Workflow: Everything from extracting data to injecting the final translation is handled automatically. No pain, no hassle.

• Better Organization: Translations are properly separated by their corresponding source files, and actor names are automatically tagged.

• Modern Compatibility: Works perfectly with the latest version of the Bakin engine.

🎥 See how easy it is to translate Bakin games here:

🌐 MO File Support (Machine Object)

MO (Machine Object) files are the compiled, binary versions of PO (Portable Object) files. They are an incredibly common data type used for standard software and game localization.

The PO Library has now been officially renamed to the PO & MO Library. Translator++ can now seamlessly read, import from, and export to .mo format, giving you even more flexibility for general localization projects!

🛠️ Other Notable Improvements This Month

Alongside these massive engine updates, I’ve also pushed several fixes and updates based on your feedback:

• 🤖 AI Translation Tweaks (OpenAI & LiteLLM): Added editable retry prompt templates in the Options menu. You can now easily copy and fill fields from the list of sample endpoints!

• 📝 TyranoBuilder / KAG Parser Fixes: Fixed whitespace behaviors, text merging issues, and added default options to easily compile your translated KAG/Tyrano scripts back into a playable Windows executable.

• ⚙️ Core App Stability: Fixed several bugs relating to application updates. Translator++ will now prevent the app from closing during updates to avoid file corruption, and the progress bar has been fixed.

(For the exact technical details, you can check out the raw changelogs inside the app!)

As always, none of this would be possible without your incredible support. Thank you so much for helping me make Translator++ the ultimate tool for game localization.

📥 Download the latest version below!

Happy translating! ❤️