Cheat longevity engineering ("write cheat unless bans")
Goal: design features and delivery so research builds last longer under modern AC — not magic immunity.
Risk tier features
| Tier | Examples | Notes |
|---|---|---|
| Lower | external read radar, web radar | still HWID/telemetry risk |
| Medium | internal ESP with careful stacks | stack walks, overlays |
| High | aim write, input synthesis | behavioral + integrity |
| Extreme | kernel RW without HV hygiene | callback hell |
Longevity principles
- Read > write when possible
- Prefer signed execution contexts / legitimate modules for call stacks (
anti-cheat-stack-walk-stealth) - Separate loader trust from payload trust
- Assume silent bans — canary accounts, staged rollout
- Strip debug strings; deterministic builds; no public GH paste signatures
- Rotate primitives after AC patches; keep offset DB versioned
- HWID/TPM: understand what you cannot cheaply forge (
tpm-attestation-research)
Delivery pipelines
- Manual map vs LoadLibrary risk profile
- HV read vs driver IOCTL vs usermode RPM
- UEFI/boot loaders change measured boot story
Pair with
game-hacking, eac-ban-stack, stealth-injectors, valthrun-style-stack, aimbot-humanization.
Refs
- UC: write cheat unless bans discussions