Package shape
Korvayne_Runtime_<version>.zip
anticheat.licThe ZIP can be the same for Korvayne Runtime customers. The license is customer, title, and build specific. The studio places anticheat.dll, anticheat.lic, and anticheat.ini next to the packaged game executable and makes sure the game loads the DLL.
License gates
If the license is missing, expired, malformed, or signed by the wrong key, the SDK does not arm sensors. The host game should keep running unprotected instead of crashing.
A valid license gates:
- sensor thread startup
- local termination decisions
- ValueGuard polling and restore
- studio telemetry delivery
- studio access-check requests
Commercial control, not magic DRM: feature entitlements prevent accidental or unsupported use in honest integrations. Code signing and normal release controls are still required before public distribution.
Updates
Korvayne Runtime updates are studio-controlled file updates through the game's normal patch channel:
| File | When it changes |
|---|---|
anticheat.dll | Runtime update or detection improvement. |
anticheat.ini | Config and enforcement changes. |
anticheat.sigs | Signed known-cheat hash update. |
anticheat.lic | Renewal, feature change, title/build update, or replacement. |
There is no self-updater in the Runtime tier. That keeps the product simple and keeps release timing under the studio's control.
Higher tiers
Higher tiers can add per-customer DLL builds, hosted dashboards, deeper analysis, custom feeds, or integration work. Korvayne Runtime stays intentionally simple: one generic package, one per-title license, clear docs, and conservative defaults.