renmori 1.1.0

1. Install & use the CLI

Install

pip install renmori
renmori --version

Requires Python 3.9+ on the developer's machine (reading a renmori.toml config needs 3.11+, or pip install tomli on older versions). cryptography is pulled in automatically. To work on the source instead:

git clone https://github.com/MewBaka/RenMori.git
cd RenMori && pip install -e .

Protect a game

1. Build your game in the Ren'Py launcher (Build Distributions). RenMori runs on that output and never touches your source.

2. Protect the build — the input is the built folder, or the .zip the launcher made (it is unzipped for you):

   renmori protect ./dist/MyGame-1.0-pc -o ./dist/MyGame-1.0-pc-protected
   # or straight from the archive:
   renmori protect ./dist/MyGame-1.0-pc.zip
   

   The first full protect downloads the closed plugin for your platform from the public release, verifies it, and caches it — no manual step. On a terminal it asks first; in CI it downloads automatically.

3. Verify the result (usable as a CI gate):

   renmori verify ./dist/MyGame-1.0-pc-protected
   

4. Ship the protected folder as your release (renmori.rmc + renmori.rpe together). Don't re-run the Ren'Py launcher on it — that rebuilds from source and drops the protection.

The command is zero-config by default, prints a machine-readable JSON result line for CI, and has clear exit codes. An optional renmori.toml controls chunk size, an exclude list, lockdown, strength, and key sources. For the open-source baseline format (no plugin, fully offline), pass --strength baseline. Full reference: the CLI docs and the renmori.toml example.

2. Documentation

The full documentation lives at renmori.mewbaka.cn — the key pages, in the order you'll need them:

Understand it

• Introduction — what RenMori is and what it protects
• Research — what already exists and why a new tool is needed
• Architecture — the full design, layer by layer
• Threat model — what it stops, and what it cannot

Protect your game

• Quick start — from a build to a protected release
• CLI reference — protect / verify, flags, and output
• Configuration — the renmori.toml file
• The plugin — baseline vs. full protection and the closed binary

Automate in CI

• CI & key management — pipelines, secrets, and a sample GitHub Actions workflow

Ship

• Steam release — overlay, DRM, and Steamworks

Internals & reference

• Container format · Loader hook · Script layer · Plugin interface

3. Licensing

RenMori — the framework and tools, the closed plugin, and the runtime that ships inside a game — is under the RenMori License 1.0: LICENSE (Chinese: LICENSE.zh-CN.md).

• Free to use. Protecting any Ren'Py game, commercial or not, is free, and the RenMori runtime may be redistributed embedded in a released game at no charge.
• No resale. Selling RenMori itself or a modified version, or running a paid "encryption-as-a-service" with it, is not permitted.
• This is a source-available license, not an OSI open-source one, because the no-resale term cannot be expressed under a permissive license.

Third-party notices are in NOTICE (note the FFmpeg LGPL/GPL terms). No warranty of unbreakability is given — see the license and the threat model.

Full terms and developer guidance are on the docs site: disclaimer, contribution terms, and notes for developers.

For licensing questions or technical help, contact: team@mewbaka.cn