SDK reference
Lifecycle, callback contract, return codes, runtime context, ValueGuard functions, behavior reports, and engine wrapper expectations.
Read referenceRuntime documentation
Guides for shipping Korvayne in a small game team.
Start with the drop-in setup, verify local logs, tune enforcement gradually, then add cooperative features such as ValueGuard, player identity, telemetry tokens, and engine wrappers.
Config reference
Every `anticheat.ini` section and key explained: enforcement, identity, telemetry, access checks, ban guidance, and ValueGuard.
Read referenceDrop-in quickstart
Place the DLL, license, and config, load the SDK once at startup, and confirm protection with `anticheat.log`.
Read guideConfiguration and enforcement
Understand report, corroborated, terminate, handle response, module response, and the special reader override.
Read guideValueGuard
Protect health, ammo, cooldowns, and other values without freezing legitimate gameplay updates.
Read guideSaveGame protection
Protect local save payloads with signed envelopes, context binding, tamper handling, and engine wrapper examples.
Read guideUnreal integration
Use a small plugin or startup module so Blueprint-first teams do not need to call raw native functions.
Read guideUnity integration
Use the provided C# wrapper, `KorvayneManager`, and protected value classes for Windows x64 builds.
Read guideSignatures and overlays
How signed overlays, unsigned injected modules, and known-cheat hash feeds are handled in Korvayne Runtime.
Read guideSecure telemetry endpoints
Build endpoints that remain safe even when the client URL is public and every client field can be forged.
Read guideRuntime release model
What the generic runtime ZIP, per-title license, updates, and self-service signature feeds are meant to cover.
Read guideTroubleshooting
Common startup, license, overlay, endpoint, and enforcement issues with practical first checks.
Read guide