LRPGM · Translator++ · MTool
To choose an alternative, consider what you want to do after automatic translation. Playing, correcting dialogue, maintaining terminology or reviewing story branches call for different tools. For RPG Maker projects, LRPGM brings these steps together in a library with integrated translation and review.
| Your task | LRPGMBuilt for RPG Maker | Translator++ | MTool |
|---|---|---|---|
| Start without translation experience | Add the executable. Simplified mode guides content, language and translation choices in the same app. A guided path with advanced options when you need them. | Create a project to edit text in a grid. Preparation uses extracted data in a staging folder. In practice: The staging folder is needed for export or injection; losing it requires rebuilding the project. View at source · Translator++ · Staging Files | Drop the executable into MTool, wait for loading and choose languages to begin. In practice: Loading can take time and temporarily leave the game and tool unresponsive. View at source · MTool · Tutorial |
| Review with story context | Original and translation side by side, source file and event, neighbouring text, map filters, chronology and choice flowchart. See the scene sequence and branches while refining the translation. | An editing grid with translation columns and context identifying each text location. In practice: Context format and scope vary by parser and engine. View at source · Translator++ · Context | Load a translation file, export original text and open the result-editing option. In practice: The presented workflow centres review on loaded results; LRPGM also provides visual event navigation. View at source · MTool · Tutorial |
| Apply translation to the game | Translation is kept in separate data. In MV/MZ, the plugin integrates text at runtime; the app handles installation and reversal. Integration adds the runtime and updates its registration; MV/MZ text databases are not rewritten as a patch. | In the RPG Maker patch workflow, export files and apply them to the game’s Data folder. In practice: This workflow replaces data files and, for games with an RGSS archive, requires handling the archive before applying. View at source · Translator++ · Patching | The game is opened through MTool’s workflow and can load translation data in the tool. In practice: MTool also offers offline use of completed translations. LRPGM runtime conditions depend on mode and plan. View at source · MTool · Engines & offline |
| Prepare a translation to share | A sharing action prepares the local MV/MZ package with integrity checks and a choice of protected distribution or review data. Plus adds custom credits and icon. Requires an eligible project and a paid online account; hosting is not included. | The exported patch can be applied by the translation recipient. In practice: Recipients need to apply files and account for the game’s structure and archive layout. View at source · Translator++ · Patching | The workflow includes loading a translation file and exporting original text for translation. In practice: Loading a translation file differs from preparing a distribution package with credits and editing rules. View at source · MTool · Tutorial |
| Choose a tool for RPG Maker | A workflow specialised in RPG Maker: reading JSON, Ruby Marshal and recognised packaged structures, with map and event review. The focus is RPG Maker. Compatibility and access depend on format and plan. | An environment for different engines with format-specific parsers and integrations. In practice: Some engines require an add-on. Project creation may launch third-party tools to extract and import text. View at source · Translator++ · Starting a project | Supports RPG Maker and other families such as Wolf RPG, Ren’Py and Kirikiri. In practice: The range of engines suits players across platforms; available features depend on engine and access. View at source · MTool · Engines & offline |
The reviewer brings together original text, translation, file, map, event and neighbouring text. Follow blocks in order or open the choice flowchart to understand what comes before and after each answer.
Read guideIn MV/MZ, analysis follows text references and uses, separates candidates from technical values and shows a confidence score. High-confidence candidates can be preselected; inspect their origin, adjust filters and decide what to translate.
Read guideRecognised variables, formatting codes and markers are protected before text reaches the translation service. LRPGM validates and restores these elements in the result, reducing manual command repairs.
Read guideA plugin may use the same name for a button and an image or audio file. In MV/MZ, the resource corrector can recover the original name during loading using the file index and translation pairs. Images and audio retain their original file names.
Read guideCreate a local package from an eligible MV/MZ project. Choose protected distribution, which blocks editing in LRPGM, or preserve review data for teamwork. Integrity checks detect changes to protected content; Plus lets you customise package credits and its icon.
Read guideThe MV/MZ runtime provides a translation menu with font, size and line-wrapping options. In eligible modes, switch between original and translated text and adjust reading without returning to the editor. Free Runtime restricts these options.
Read guideCoverage depends on the engine, plugins and plan. Resource reference correction needs a file index and a translation match; it does not recreate missing files. Local sharing requires a translated, intact MV/MZ project, an unprotected source and an online base paid Basic or Plus account. Editing protection does not prevent copying the package or replace the game author’s rights.
RPG Maker structure guides the whole workflow: extraction, configuration, translation, review and application. Simplified mode helps beginners; maps, events, glossaries and plugin analysis support careful review in the same app.
For RPG Maker games, with a guided workflow that lets you start simple and continue reviewing maps, events and plugin text.
LRPGM × Translator++Another option to consider if you play titles across different engine families. Check your game’s workflow and compatibility before choosing.
LRPGM × MToolThe considerations above concern the linked workflows, not every mode of each tool. Translator++ also offers code protection and context features; MTool allows offline use of completed translations. Features, plans and requirements may change. Check the version you will use.
LRPGM combines a guided start with map, event, neighbouring text, chronology and flowchart review. MV/MZ plugin analysis presents classified candidates and confidence scores, while translation protects recognised commands.
Eligible MV/MZ projects can generate a local package through LRPGM sharing. An online base paid Basic or Plus account and an intact, unprotected source are required. Plus allows custom credits and icon. Protected distribution blocks LRPGM editing and checks integrity, but does not prevent package copying.
Check the game engine, plan features and translation service requirements. LRPGM MV/MZ Free Runtime requires the app open and an online session. Custom plugins and packaged formats depend on recognised structures; confidence scores do not guarantee coverage of every text.
