No anticheat.log
- Confirm
anticheat.dllis next to the executable that actually runs. - Confirm the game loads the DLL at startup.
- Confirm the build is Windows x64.
- Check engine logs for a missing DLL or startup wrapper error.
Copying a DLL next to an executable is not enough if the game never loads it.
License errors
| Log shape | Likely fix |
|---|---|
| No license provided | Place anticheat.lic next to the game executable. |
| Signature invalid | Use the license issued for this title/build. |
| Expired | Renew or re-issue the license. |
| Malformed | Re-issue the license with required fields. |
Game closes immediately
- Temporarily set
eject = 0. - Use
module_response = reportandhandle_response = corroborated. - Run again and inspect the log.
- Re-enable stricter categories one at a time.
Do not tune blind: if the game closes during integration, reduce enforcement first, collect logs, then raise policy after the cause is clear.
Overlay false positives
Steam and Discord overlays are expected to load signed DLLs into some games. The module sensor should not block a valid signed overlay just because it is present. If strict config produces problems, collect:
- the loaded module name and path
- signature status and signer
- the Korvayne log lines around the event
- the enforcement config used for the run
Endpoint spam or forged requests
Do not depend on hiding the endpoint URL. Use short-lived session tokens, strict schemas, replay protection, and rate limits. If the endpoint is not ready, keep telemetry and access checks disabled in anticheat.ini.
Support bundle
When asking for support, include:
- Korvayne package version
- game engine and platform
anticheat.loganticheat.iniwith secrets removed- license ID fingerprint from the log, not the raw license token
- steps to reproduce