Check before install

NovaTextVN compatibility with a Ren'Py game

This page helps you decide whether NovaTextVN is a good fit for your Ren'Py game: good signs, warning signs, when to test on a copy, and when to expect partial compatibility.

Is your Ren'Py game a good fit for NovaTextVN?

Use this page as a short pre-install checklist: good signs, warning signs, and cases where testing Base on a copy is the safer first move.

Good first-test case

Ren'Py 7 or 8, a normal game structure, and a plan to test the Base release before making the setup more complex.

Check more carefully

Heavily customized UI, unusual screens, older projects, or games where more than story text matters.

Base first, PRO later if needed

Try the public release on your own game first, then decide whether you really need PRO.

If F10 does not open

Go straight to the install guide and troubleshooting instead of guessing blindly.

How to decide for your own game

There is no fake list of “guaranteed supported games” here. Instead, this practical checklist helps you decide whether to try Base immediately, test on a copy, or expect partial limitations from the start.

Good signs

  • The game uses a normal game/ structure and a straightforward local launch flow.
  • The interface is not rebuilt far away from standard Ren'Py screens.
  • Your first goal is to test story scenes and regular gameplay text.
  • Base is usually enough for a first pass to see how F10 and the basic workflow behave.

Warning signs

  • The game depends heavily on custom menus, phone systems, maps, or other non-standard screens.
  • The project already feels far away from typical Ren'Py behavior from the first launch.
  • You need complete interface coverage immediately without a manual check first.
  • The game already contains other mods or an older NovaTextVN setup that was never cleaned up.

When to test on a copy

  • If the game is new to you and you do not want to touch the main install first.
  • If you only want to verify F10, launch behavior, and the first scenes.
  • If you want an easy rollback by restoring a clean game/ folder.
  • If the game already contains other files you do not want to mix by accident.

When to expect partial compatibility

  • Dialogue translation works, but parts of the UI or service screens stay mixed.
  • F10 opens, but rare states behave less predictably than ordinary scenes.
  • Custom UI matters almost as much as the story text in this game.
  • Base can still be useful for the first test even if a deeper follow-up is needed later.

Which limits are worth expecting upfront

Full coverage depends on the game

Some projects customize the GUI so heavily that the same result should not be expected everywhere.

Custom screens need verification

The further a game moves away from standard Ren'Py screens, the higher the chance of partial limitations.

Rare UI states can vary

This especially applies to unusual save/load screens, settings menus, and custom overlays.

Testing on a backup is safest

If the game matters to you, back up game/ before your first NovaTextVN install.

What to check when compatibility is unclear

Check the install path first

Make sure the files are really inside game/ and not duplicated in nested folders.

Review the game structure itself

Sometimes the main issue is the game's custom layout rather than NovaTextVN itself.

Verify the F10 menu

If the menu does not open, that is an important first signal during compatibility checks.

Use Issues for reproducible reports

If you can describe the game, version, and exact steps, that is the most useful format for follow-up.

What to open next about compatibility

Check compatibility first or download Base now?

If the game structure already looks familiar, go to the release. If game/, F10, or custom UI still feel unclear, start with the install guide and FAQ.