
offsets.allowd.dev
offsets
Public offsets for cheat devs. Every patch is parsed, versioned and served as an API. Free.
from header to api
What happens to a patch
-
01
header
Each patch starts as the C++ header the dumper writes for that build.
-
02
parsed
Every declaration becomes a typed entry. Anything the parser can't read blocks the release.
-
03
decoded
Hidden fields ship with their decode chain, in order.
-
04
served
Poll /latest with your key and an ETag. You get a 304 until the next patch is published.
Steps run left to right on one 32-bit dword. add wraps at 32 bits, rol rotates left.
games
Pick a game
More games are added as their dumpers are ready. Every game keeps its full build history.
api
Keep your tool current
Access is free. Request a key, an admin approves it, and every call sends it as a bearer token. Keep the export's ETag: an unchanged build answers 304 with an empty body, so polling costs almost nothing.