Skip to content

Siglus

plugin_id: siglus_rs · Engine family: SiglusEngine

Upstream: xmoezzz/siglus_rs. Adaptation fork: Project-Shinkirou/siglus_rs, shinki-android-isolation branch.

Scene.pck groups scene chunks and package-level include properties/commands. Package offsets are relative to the package, while offsets in each decoded .ss chunk are relative to that chunk. Indexed string lengths and offsets count UTF-16 code units, not bytes; the stored strings have an index-dependent word transform. Scene, label and command-entry tables are separate inputs to VM control flow.

The fork retains the Siglus VM, renderer, text/keyboard input and native saves. Its adapter owns execution and publishes CPU frames. Native configuration supports paired original/chs resources and G01/movie selection.

Android Manager statically embeds Siglus alongside RFVP, Artemis and Musica. Siglus and RFVP use the same wgpu 30 runtime as Manager. Their native WMV decoders keep the Rust API without exporting the optional c-abi functions into Manager, preventing duplicate wmv2_decoder_* symbols.

Saves stay where the original engine writes them: <game>/savedata/ holds NNNN.sav slots and thumbnails, global.sav, config.sav, read.sav and Twitter state; captures and exports are written relative to the game directory. A recovered key goes to <game>/key.toml, as upstream does. The chs resource pair shares savedata/ with the original pair, like the patched original. The game directory must be writable.

0.1.0-beta.1 and beta.2 kept saves under %LOCALAPPDATA%\siglus_rs\saves\<hash>\siglus-<language>-<id>\ (macOS: ~/Library/Application Support/siglus_rs/saves/…; Linux: $XDG_DATA_HOME or ~/.local/share/siglus_rs/saves/…). The first launch of a game imports that folder into the game directory once: existing files are kept, and the old folder is renamed to ….imported. If you had set the retired “save directory” option, the core cannot find that folder anymore. Copy the contents of each siglus-* folder inside it (savedata/ and any capture files) into the game directory yourself, without overwriting files you want to keep.

A localized edition’s wrapper is not part of the embedded runtime: the core does not apply wrapper machine-code patches or invent missing fonts. Package decoding, resource configuration and runtime behavior must be established for the exact edition.

See the core directory for build/release status and compatibility reports for specific releases. See also Core ABI and User guide.