AUTHENTICATED POST-DEPLOYMENT CONTROL
The system has boundaries. These are documented. Understanding them is required.
External binaries inside the game directory are not processed. They will not function post-protection.
Non-standard .pyd/.so modules beyond Ren'Py's included set may fail to load or execute.
Patched or recompiled Ren'Py builds with custom internals are not guaranteed to work.
Protected builds require network access for initial validation. Fully offline environments are not supported.
Games with 400+ script files experience extended first-launch times. Subsequent launches are normal.
The protection module terminates when debugging tools are detected. This is intentional.
macOS builds require valid code signatures. Modified binaries after protection will fail to launch.
These constraints are known.
They are not bugs. They are boundaries.