Overlays that never touch the game.
External ESP for the shooters you actually play. Boxes, skeletons, health and distance, drawn from outside the process — no injection, no game files, no restarts.
- Read-only physical memory
- Stream proof invisible to OBS
- Build-gated stops on patch
Cheat catalogue
digital delivery · instantVALORANT
ESP, skeleton, health, distance, stream proof, fog dimming.
Apex Legends
Boxes, skeleton, health and distance on the same external reader.
The Finals
Player boxes, health and range readout, built for the same overlay core.
Next titles
Catalogue grows with the reader core — one product per supported game.
Why read-only
The cheat lives outside the game. That is the whole design.
- No injected moduleNothing is loaded into the game, so nothing is scanned as a module.
- No game files touchedNo patched pak, no modified config, no reinstall after a patch.
- Signed driver, unmodifiedThe same published driver image, loaded once and left resident.
Shared requirements
- Windows 10 or 11, 64-bit
- Administrator rights (one UAC prompt)
- ~2 MB disk
- One licence per product
Every product is build-gated: when a patch lands the launcher blocks that product until it is updated.
Questions
Do the cheats inject?
No. Every product uses the same external reader — physical memory only.
Can one licence cover every game?
No. Licences are per product, so VALORANT time is separate from Apex time.
Can I move a licence to another PC?
Yes. Licences bind to one machine and include self-service resets.
What happens on patch day?
The product is marked incompatible, you keep the remaining time, and play resumes with the next build.