Interface limitations

Why not everything is translated

Partial translation does not always mean a bad install. In Ren'Py, a lot depends on the specific game: how much the author changed the UI, history, menus, and auxiliary screens.

1. What gets translated first

  • The public Base release is most useful for the main reading flow and story text first.
  • That already matters if your goal is to read the VN in Russian without a manual build.
  • Separate menus, history, custom screens, and helper UI can depend heavily on how the specific game is built.

2. When partial UI is not an install-path error

  • If F10 opens and the story flow works, but part of the interface stays incomplete, the question is often compatibility rather than file placement.
  • Heavily customized Ren'Py projects can behave very differently even with a correct install.
  • That is why it helps to compare the game against the compatibility page instead of treating every untranslated screen as a broken install.

3. When PRO is worth checking

  • PRO is better treated as a control layer for terms, profiles, and edits, not as a guarantee for every custom UI screen.
  • It becomes more valuable in long VNs where term stability, profiles, dictionary control, and in-game edits matter more.
  • If that is the friction you want to reduce, the upgrade path to PRO becomes easier to justify.

If you are unsure whether this is a limit or a bug

Check whether F10 opens, whether the core reading flow works, and whether the issue belongs to one custom screen only. That is the best filter before an issue.

Open GitHub Issues