aob-signatures
AOB signatures
Scope
Use this for single-player or offline games, modding, interoperability, and private servers the user runs. Don't help bypass or hide from anti-cheat (EAC, BattlEye, Vanguard, VAC) or cheat in online multiplayer; say so plainly and offer the offline part if there is one.
Why addresses break
A hardcoded address like game.exe+0x2567B10 is a position. Any patch that adds or removes a single byte of code or data before it shifts everything after it. ASLR also moves the module base on every launch, so only base + RVA is meaningful, and the RVA itself moves with each build.
The code that uses the address mostly doesn't change. A signature describes that code with the build-specific bytes masked out, so you find the instruction again in the next build and read the new address out of it.
Two things come out of a signature:
- An address: the instruction holds a rel32 or RIP-relative disp32 pointing at a global (
GWorld,GNames, a manager singleton) or a function. Resolve it. - An offset: the instruction holds a struct field displacement (
[rcx+0x13C]). Read it.
Tooling
Install sigtool (Python 3.11+, offline, standard library only):