Best starting case
Ren'Py 7 or 8, a normal game structure, and a plan to test the Base release before making the setup more complex.
Before installing, it helps to look not only at the Ren'Py version but also at how heavily the game changes the standard interface and scripting flow.
Use this page for a quick reality check before install: it helps you see whether the game is a good candidate for the Base workflow.
Ren'Py 7 or 8, a normal game structure, and a plan to test the Base release before making the setup more complex.
Heavily customized UI, unusual screens, older projects, or games where more than story text matters.
Try the public release on your own game first, then decide whether you really need PRO.
Go straight to the install guide and troubleshooting instead of guessing blindly.
Projects that stay close to standard Ren'Py behavior are usually the safest first-install scenario.
Translation often works, but some interface pieces and edge states should still be checked manually.
If the game rewrites major screens or flows, some functions may be limited or need separate verification.
For very old or strongly modified projects, it is safest to test on a backup copy of the game first.
These are not hard guarantees for named games, but signals that a project is closer to a safe install scenario.
Full support
Core scenarios and key features work without notable limitations.
Partial support
The base workflow usually works, but some functions may be limited or inconsistent.
Not supported
The version is too old or the game structure does not fit the public release.
Some projects customize the GUI so heavily that the same result should not be expected everywhere.
The further a game moves away from standard Ren'Py screens, the higher the chance of partial limitations.
This especially applies to unusual save/load screens, settings menus, and custom overlays.
If the game matters to you, back up game/ before your first NovaTextVN install.
Make sure the files are really inside game/ and not duplicated in nested folders.
Sometimes the main issue is the game's custom layout rather than NovaTextVN itself.
If the menu does not open, that is an important first signal during compatibility checks.
If you can describe the game, version, and exact steps, that is the most useful format for follow-up.
Compatibility gives the broad picture, while these pages handle the narrower scenarios: F10, file placement, partial UI, removal, and updates.
A short checklist for install path, game restart, and compatibility before you open an issue.
The exact answer on what to copy from the archive and where it belongs inside the game.
A short rollback guide: which files to delete and when a clean reinstall is the better choice.
Why some interface parts can stay partial and how to tell game limits apart from install mistakes.
How to do a clean reinstall safely and avoid mixing older files with newer ones.
If you already understand your game structure, go to the release. If not, start with the install guide and FAQ.