Offset tiers

Windows · macOS · Android · home

A build can have up to two offsets sets, and they are recorded separately because they come from different people with different guarantees.

Tier	What it is	How it arrives
`verified`	Dumped and checked by rbxoffsets. These are the production offsets.	Uploaded by hand — never pulled from anyone else.
`default`	A real, usable dump produced by somebody else and mirrored here. Not verified by us.	Mirrored automatically from theo's offsets.

Default is not a spare kept in case verified breaks. It is a genuine dump, usually published within the hour of a build appearing, that has simply not been checked by this project.

Which one you get

You ask for	You get
nothing, or `?tier=best`	Verified when the build has it, otherwise default.
`?tier=verified`	Verified, or `404 offsets_not_verified`. Never a substitute.
`?tier=default`	Default, even when a verified set exists.
`/offsets/{version}/{tier}/{file}`	That exact file in that exact tier, or a 404.

For a single file under best, the preferred tier that has that file is used: a verified set need not carry FFlags, and asking for fflags.hpp then serves the default set's copy rather than failing.

latest follows the tier. latest?tier=verified is the newest build with a verified set, which can be older than the newest build with any set — and the response names the version, so nothing is mistaken.

Every response says which tier it served

curl -sI "https://rbxoffsets.com/api/v1/windows/offsets/latest/hpp"

HTTP/1.1 302 Found
x-roblox-version: version-c5aecda2245e4fae
x-offsets-tier: verified
x-offsets-file: offsets.hpp
x-offsets-source: upload
x-offsets-verified-at: 2026-09-09T18:20:00.000Z
x-offsets-sha256: 4c1e…

JSON responses carry tier and availableTiers. Log the tier. If your integration misbehaves on one build, it is the first thing worth knowing.

What a set records

{
  "platform": "windows",
  "version": "version-c5aecda2245e4fae",
  "displayVersion": "0.738.0.7381397",
  "tier": "verified",
  "availableTiers": ["verified", "default"],
  "source": "upload",
  "dumper": "rbxoffsets-dumper",
  "dumperVersion": "1.0.0",
  "verifiedBy": "jude",
  "verifiedAt": "2026-09-09T18:20:00.000Z",
  "notes": "checked in game before LIVE",
  "count": 392,
  "dumpedAt": "2026-09-09T18:02:00.000Z",
  "storedAt": "2026-09-09T18:05:11.000Z",
  "credit": { "label": "rbxoffsets", "url": null },
  "files": [ { "file": "offsets.hpp", "kind": "offsets", "format": "hpp", "sizeBytes": 25930, "sha256": "…", "url": "https://rbxoffsets.com/api/v1/windows/offsets/version-c5aecda2245e4fae/verified/offsets.hpp" } ]
}

Withdrawn sets

If a verified set turns out to be wrong, the operator withdraws it. Reads stop serving it at once and fall back to default; nothing is deleted, and it can be restored. A withdrawn set never appears in availableTiers.

Per platform, on this deployment

Platform	verified	default
Windows	yes — uploaded by hand	yes — mirrored from theo's offsets
macOS	yes — uploaded by hand	no upstream publishes one
Android	yes — uploaded by hand	no upstream publishes one