How Compuon Works
One type change. Auditable runtime integrity. Zero kernel drivers.
The Idea
Every Compuon<int> variable carries a hidden integrity state alongside the game value. Your game code uses the variable normally. But if a cheater modifies the value in memory, the integrity state no longer matches. The integrity server turns that mismatch into evidence.
Cheater finds hp = 100 in memory, changes it to 999999. Nothing detects this. Game accepts the new value.
Cheater changes hpto 999999, but can't update the integrity state. The integrity server checks it, sees the mismatch, and records proof instead of guessing.
Three Steps
Change int hp = 100; to Compuon<int> hp(100);. All operators (+=, -=, <=, etc.) work identically. No game logic changes needed.
Compuon links natively into your game binary. No separate client process. Each build gets a unique internal structure, so a cheat built against one build won't cleanly carry over to the next.
The integrity server periodically spot-checks protected variables. If a value was tampered with, the proof no longer matches. Suspicion accumulates and persistent cheaters get actioned.
Why Native C++ Integration?
This is a security requirement, not just a convenience:
If Compuon ran as a separate DLL, its interface would be visible and callable by external tools, undermining the protection. Static linking into the game binary eliminates that surface.