R-Migrator v1.1

User
Guide

Automated refactoring tool for Ren'Py R8. Developed by ROOTWIN PROJECT.

This guide is aimed at mod authors and translators who need to bring an old Python 2 / Ren'Py 7 mod to Ren'Py 8 / Python 3 compatibility.

R-Migrator automates the typical fixes. It doesn't guarantee a perfect port of heavily custom code — always test the mod after migration, especially anywhere the original author wrote one-off Python.
01 — What it fixes

Python 2 to Python 3 fixes

R-Migrator scans .rpy files and applies these fixes automatically.

print statement

print-statement -> print()

except / raise

except X, e -> except X as e / raise X, msg -> raise X(msg)

dict methods

has_key / iteritems / iterkeys / itervalues -> Python 3 equivalents

xrange

xrange -> range

literals

long / L-suffix, octal 0755, ur"...", `expr` -> Python 3 syntax

unicode / basestring

unicode() / basestring -> str

bytes / str

patched in poem and game scripts

ATL coordinates

float/int fixes in ATL transforms and random.randint

02 — Workflow

Step-by-step workflow

01

Launch

Open R-Migrator. The main screen lists what the tool can fix and shows the "SELECT TARGETS" button.

02

Pick the mod folder

Click "SELECT TARGETS" and choose the folder that contains your mod. R-Migrator reads the subfolders inside it as migration targets.

03

Choose targets and backup

Tick the subfolders you want processed. The "Create .bak backup before patching" checkbox is on by default — keep it on so every changed file gets a .bak copy next to it.

04

Third-party tools consent

If the selected folders contain .rpa archives or .rpyc files without a matching .rpy, R-Migrator offers to unpack/decompile them first using rpatool.py and unrpyc.py. A one-time consent dialog appears before this runs.

Only continue if you trust the source of the archive — R-Migrator did not write these third-party tools and cannot guarantee the safety of an untrusted .rpa/.rpyc.
05

Run the migration

Click "EXECUTE". The console at the bottom streams every processed file, warning, and fix category in real time.

06

Review the result

When the run finishes, the console prints the total number of patched files. Check the .bak files and the logs/ folder if you need to review or roll back anything.

03 — Safety

Backups and third-party tools

💾

.bak backup

With the backup option on, every file gets a .bak copy saved next to it before it is overwritten. Keep it enabled unless you already have your own backup.

⚠

Third-party unpacking tools

Unpacking .rpa and decompiling .rpyc uses rpatool.py and unrpyc.py — code R-Migrator did not write. Only proceed with archives from a source you trust.

📁

Full mod backup

Besides the per-file .bak option, keep a separate full copy of the mod before migrating — a safety net independent of the tool.

04 — Logs

Session logs

Every migration run writes a separate log file into the logs/ folder next to the program, named with the date and time of the run — nothing gets overwritten between sessions.

📁 R-MIGRATOR
├── 📂 logs
│   └── 📄 rmigrator_2026-05-09_14-32-07.log One file per migration run
05 — Interface

Other controls

🌓

Switches between light and dark theme.

RU / EN

Switches the interface language.

Info

Opens the about window with ROOTWIN PROJECT links and a way to support development.

06 — Support

Feedback

Bug report

What to include in a bug report

  • logs/rmigrator_{date}.log — the log file for the run that failed
  • Screenshot of the console output at the moment of the error
  • The mod's Ren'Py version (6, 7 or 8) and whether it was packed as .rpa/.rpyc
Telegram @rootWin