offsets request access
allowd

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

  1. 01

    header

    Each patch starts as the C++ header the dumper writes for that build.

  2. 02

    parsed

    Every declaration becomes a typed entry. Anything the parser can't read blocks the release.

  3. 03

    decoded

    Hidden fields ship with their decode chain, in order.

  4. 04

    served

    Poll /latest with your key and an ETag. You get a 304 until the next patch is published.

offsets.hpp

        
parsed entries
decode chain

Steps run left to right on one 32-bit dword. add wraps at 32 bits, rol rotates left.

httpconditional request

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.

request api accessapi docsRequests without a key get 401.

    

offsets

api access

Request API access

The API is free. Tell us what you're building and an admin reviews the request by hand. Browsing offsets on this site stays open to everyone.

What you get
A key per project, the full build history, ETag polling and the JSON export.
What we ask
What the project is, whether it's a public P2C, roughly how many users it has and how it will call the API.
How it works
Sign in with Discord and send the form. Your panel shows the decision, and keys work as soon as you create them.
Without a key
The API answers 401. The website keeps working for manual lookups.

developer panel

Your API

admin

Admin

Review API applications, publish builds and edit the feature lists.

404

Nothing here

This page doesn't exist, or the build hasn't been published.