Korvayne is not trying to sell you a fantasy.

AC-Basic is a first defensive layer for Windows games. It is built to make low-effort cheats noisier, harder to trust, and less attractive to maintain. Serious attackers still exist. The point is to stop the easy damage before it becomes your game's reputation.

Our default posture: log first, understand the evidence, tune responses gradually, and keep honest players out of the blast radius.

1. A memory editor changes health or ammo

A player uses a public memory tool during a match and edits values that should only change through gameplay.

Korvayne sees suspicious memory access or protected value drift. Your config decides whether to log, restore, warn, or terminate. Your team gets evidence instead of only angry player reports.

2. An injected DLL appears in the game

A low-tier cheat loads code into the process, or manual-maps a module so it does not look like a normal file-backed DLL.

Korvayne reports the module and context around it. Signed, known overlays can be treated differently from unknown unsigned code. You can start conservative, then tighten once false positives are understood.

3. A public playtest attracts basic tooling

The first bigger playtest brings tools you did not see in closed testing: debuggers, handle scanners, simple injectors, and old cheat templates.

Run AC-Basic in report mode first. Review what actually happens on normal player machines. Move high-confidence detections to stronger actions before launch.

4. Normal overlays need to keep working

Players use Steam, Discord, recording tools, accessibility software, and driver utilities. Blocking all injected or hooked software blindly creates support pain.

Allow common signed software where appropriate. Flag suspicious unsigned modules with stronger context. Keep anti-cheat pressure focused on cheat behavior, not normal PC life.

Where Basic fits

Use AC-Basic when you want a practical barrier against obvious client-side tampering and a clearer view of what is happening in the wild. It is a good fit for prototypes, public playtests, small live games, and indie teams that need useful protection before they can justify a larger security stack.

Good anti-cheat should buy time. It should make cheap abuse harder, give you evidence, and protect the trust of honest players while your game grows.