Projects and library
Does LRPGM delete or modify the original game?
Learn when files change, how backups protect a project, and what happens when you remove it from the library.
Access conditions
There is no universal reversal through a plugin toggle. MV/MZ and Legacy have different application paths that can change data, scripts or containers. Backup is optional and disabled by default.
Add and remove from the library
Adding a game only registers its path so LRPGM can manage it. Removing a project from the library does not delete the original folder.
When the game changes
Files in the registered copy are modified when you finalize and apply a translation. Do not work on your only copy. Under Settings > Advanced, keep safety backup generation enabled before modifications.
Good practices
- keep an untouched copy outside the working folder;
- do not close LRPGM while it applies files;
- test the game after finalizing;
- do not manually edit internal translation data;
- generate a new shared package after every change.
LRPGM includes integrity checks and can stop when it finds an unsafe state. If that happens, follow the on-screen guidance or start a new preparation from an intact copy.
Related articles
Content that complements this guide and helps with the next steps.
Review text and apply the translation
Correct available output, apply through the appropriate action and check the game.
Read articleSettingsLRPGM settings: translation, performance, and backups
Learn what to change under General, Translation, Glossary, and Advanced without putting projects at risk.
Read articleProjectsHow to organize and manage your LRPGM game library
Search, filter, open properties, change paths, and remove projects without deleting the original game.
Read articleTranslationPrepare a local sharing package
Export an eligible MV/MZ translation as a folder or ZIP.
Read articleNeed help?
Didn’t find the answer in the articles? Get in touch and tell us what happened with your project.