Tyranor Next recognises games by archive signature, then picks a runtime
A multi-engine visual novel simulator mainly for Android, with built-in Kirikiri, ONScripter, Tyrano, Artemis and Siglus engines, support for external Ren'Py and RPG Maker RGSS APK engine modules, and jump-to launching of external PSP/Nintendo Switch emulators (PPSSPP/Eden). Recognizes and launches many game types, with library management, cover art fetching, save mirroring and engine parameter tuning.
At a glance
- What is it?
- An Android launcher that reverse-rewrote the Tyranor emulator and now recognises visual novels across nine built-in engines, several external APK engine modules and two console emulators. Detection is by file signature, so a game is identified by its archive format rather than by a manifest, and the platform floor is 64-bit ARM on Android 8.
- Who is it for?
- Tyranor Next is for someone with a shelf of Android visual novels spread across half a dozen engines who wants one library instead of six launchers, and the signature table is the part worth reading even if you never install it, since it explains exactly how each format is recognised.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- Weiss-UltimateSavior/Tyranor-Next860 ★ · +374
| Repository | 2026-09-21 | 2026-11-14 |
|---|---|---|
| Weiss-UltimateSavior/Tyranor-Next | 486 | 860 |
374 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Nine native runtimes, plus modules and emulators
The scope is stated as a table of game types, and the count is larger than the repository description first suggests. Nine engines run natively inside the app: Kirikiri and Kirikiri2 through Kirikiroid2 and krkrsdl3, ONScripter, Artemis, Siglus through a native runtime called `siglus_rs`, RealLive, AVG32 and UK2 through a shared built-in runtime called `game_launcher`, FVP through `rfvp`, and Tyrano through its own Web runtime. Four more are handled by an external RPG Maker APK module, covering XP, VX, VX Ace and mkxp-z, and Ren'Py runs as its own external APK module. Two Windows engines, YU-RIS and CatSystem2, are delegated to an external Winlator, and any arbitrary Windows program can be added the same way. Console titles go to external emulators: PSP through PPSSPP and Nintendo Switch through Eden. RPG Maker MV and MZ are not native at all, since both are Web games, and a generic `index.html` entry catches whatever else is a browser game.
Detection is signature matching, not a manifest check
How a game is identified is the interesting engineering detail, because there is no standard format to read. Kirikiri titles are recognised by `.xp3` archives or a `startup.tjs`. ONScripter by `nscript.dat` or `.nsa`. Artemis by `system.ini` or `.pfs`. Siglus by `Gameexe.dat` with `Gameexe.ini`, or by `Scene.pck` in the root or in `Data/`. The three that share one runtime are distinguished by the contents of a `SEEN` table: RealLive expects a 10000-entry TOC or `SEEN####.TXT`, AVG32 looks for a `PACL` marker or `TPC32`, and the PC-98 UK2 engine is keyed on `UK2.CFG` plus `*.MES` files carrying the `<< UK2 TEXT Ver1.00 >>` header. FVP looks for `*.hcb` or `*.bch` scripts alongside `graph.bin` and `voice.bin`. RPG Maker is the cleanest case, since `.rgssad`, `.rgss2a` and `.rgss3a` each map to one editor version. CatSystem2 is scored on combinations of `config/startup.xml` and the `.int`, `.cst`, `.hg3` and `.kcs` extensions, with `cs2.exe` used only as a supporting hint and never as the sole test.
Ren'Py picks 8.5 or 7.7.1 from script_version
The Ren'Py path is the most detailed of the external module integrations, and it explains a choice that would otherwise be arbitrary. Two engine versions are supported, 8.5 and 7.7.1, and the version can be chosen either globally or per game in settings. On top of that there is an automatic mode, and the logic it uses is specific: it reads the `script_version` recorded by the game plus fingerprints of the Python 2 runtime library, then matches against the available modules. The main application enables the whole capability by default and, on the engine page, does only one check, whether the target module is installed. If it is not, the engine entry is marked with a cross and the app prompts you to download and install it. Ren'Py is recognised by `.rpa` archives plus `game/script.rpy`, `game/options.rpy` and a `renpy/` directory containing `.rpy` or `.rpyc` files. RPG Maker MV and MZ deliberately stay on the internal Web runtime instead of the external module.
Winlator runs the Windows engines and owns the save handling
Two Windows engines are delegated rather than reimplemented, and the boundary is drawn explicitly. YU-RIS is identified by `yscfg.dat`, `pac/*.ypf` archives, the `YS*.DLL` engine library and `.ymv` video, and it launches through the external Winlator using a game directory plus a main executable. Winlator allocates a free drive letter and mounts the directory temporarily, with `save=false` so the launch does not write back into the container configuration. The main executable is chosen automatically and can be overridden from a launch-file field in the game details. CatSystem2 works the same way, with the extra detail that the runtime allows a `.bin` and prefers `cs2.exe` when one is present. The general-purpose PC entry point is manual rather than scanned: a button in the top bar of the game page lets you pick a directory, search it for executables and nominate a launch target. Those games are deliberately excluded from save management and from engine parameter configuration, because Winlator handles both.
PSP and Switch are recognised by extension and nothing else
Console support is the thinnest part of the recognition work and the cleanest to describe. PSP titles are filed by extension, `.pbp`, `.cso`, `.iso` and `.chd`, and Switch titles by `.nsp`, `.xci`, `.nca` and `.nro`, with each file added to the library individually rather than through any content inspection. Launching pulls up an already installed PPSSPP or Eden, using an explicit component reference plus a read permission, taking the SAF content URI, and converting the file fallback path through FileProvider. Saves and settings for both stay inside the emulator, and the main application does not touch them. The engine page has an entry for external-jump support that shows installation status and links to the download pages. The same page can switch on categorised display, paginating engine entries into GAL, RPG Maker, console and web groups, which is how a single list stays navigable with this many engines in it.
One dependency direction across three layers
The architecture is two Gradle modules and a strict layering rule. `engine/` is the low-level runtime core: SDL2 and SDL3, the Kirikiri TVP interpreter, krkrsdl3, ONScripter, Artemis, Siglus, FVP, Tyrano, native and JNI glue, plus the Activity that hosts an engine. `app/` is the Android shell, and inside it the separation is explicit:
界面 UI 交互层 -> 功能抽象层 -> 底层引擎层The arrow direction is fixed and never reversed. The UI layer under `app/src/main/java/com/tyranor/next/ui/` holds Compose pages, the Activity shell, dialogs, navigation, the top bar, the search box and the loading and error states. The feature abstraction layer under `core/` holds everything domain shaped, and is itself split: `core/game` for scanning, model and saves, `core/engine` for engine types and the launch and install protocol of both built-in plugins and external APK modules, `core/cover` for cover fetching and batch jobs, `core/patch` for KRKR online patches, `core/settings` for the three levels of configuration, `core/auth` for Hikarinagi OAuth and token handling, and `core/updater` for background update checks.
arm64-v8a only, API 26, and every release tagged beta
The platform requirements are short and non-negotiable. Android 8.0, API 26, is the floor. Native engine libraries are provided only for `arm64-v8a`, so a 32-bit device is out regardless of its Android version. Game directories have to live in local storage Android can reach and be authorised through the system file picker, and at launch the directory must be mappable to a real file path; on external storage some engines additionally need the all-files permission. The documentation is candid that real compatibility depends on the engine version, the packing or encryption method and the script features a given game uses, and that specially modified releases may need engine settings adjusted or patches applied. Every visible release tag carries a beta prefix, `beta-1.51`, `beta-1.52` and `beta-1.53` on consecutive days in late September 2026, and the last push to `main` was 2026-09-29. One more signal about how the project runs its own review: the root carries both `AGENT.md` and `.coderabbit.yaml`, and contributors are told to run the review procedure in that file before submitting.
Editorial conclusion
Tyranor Next is for someone with a shelf of Android visual novels spread across half a dozen engines who wants one library instead of six launchers, and the signature table is the part worth reading even if you never install it, since it explains exactly how each format is recognised. It is not the right tool for PC-first collections, because every Windows engine routes through an external Winlator install that this project does not control, or for anything outside 64-bit ARM Android, since only `arm64-v8a` engine builds are provided. Before you commit, check the two things the documentation flags as variable: the engine version and packing method of the specific games you own, since modified releases are explicitly called out as possibly needing engine settings or patches, and whether the SAF path your game directory lives on maps to a real file path at launch, since the app requires that rather than a cloud or virtual location.
Frequently asked questions
Which visual novel engines does Tyranor Next run natively?
Nine: Kirikiri and Kirikiri2 through Kirikiroid2 and krkrsdl3, ONScripter, Artemis, Siglus through siglus_rs, RealLive, AVG32 and UK2 through the shared game_launcher runtime, FVP through rfvp, and Tyrano through its Web runtime. Ren'Py and RPG Maker XP, VX, VX Ace and mkxp-z run as external APK modules instead.
How does Tyranor Next decide which engine a game needs?
By file signature rather than a manifest. Kirikiri is matched on .xp3 or startup.tjs, ONScripter on nscript.dat, Artemis on system.ini, Siglus on Gameexe.dat with Scene.pck, and CatSystem2 is scored on combinations of config/startup.xml with .int, .cst, .hg3 and .kcs files, with cs2.exe used only as a supporting hint.
What are the Android requirements for Tyranor Next?
Android 8.0, API 26, or later, and a 64-bit ARM device because the native engine libraries are only provided for arm64-v8a. Game directories must be on local storage reachable by Android and authorised through the system file picker, and the directory must map to a real file path at launch.
Does Tyranor Next manage saves for Windows or console games?
No. YU-RIS, CatSystem2 and manually added PC games are launched through an external Winlator, which handles their saves and run parameters, and PSP and Switch titles are handed to PPSSPP and Eden, which manage their own saves and settings. PC games added manually are also excluded from save management and engine parameter configuration.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/weiss-ultimatesavior-tyranor-next)Star history chart for your README
[](https://hysenlabs.com/projects/weiss-ultimatesavior-tyranor-next)Was this useful?