Events and feeds

Windows · macOS · Android · home

Everything this server notices is recorded as an event, once — a given build can raise a given event only one time. The same record feeds the API, the Atom feeds and Discord.

Recorded is not the same as announced. Every event below is in the API and the feeds. The Alerts column says whether it is also worth a Discord message by default: two of them are bookkeeping that follows another event by seconds, and announcing them buries the ones that matter. DISCORD_NOTIFY_EVENTS changes the set.

Type	Meaning	Alerts	Payload fields
`upcoming`	A build was detected ahead of production. Roblox has named it; the package may not be there yet.	yes	displayVersion, deployedAt, cdnAvailable, liveVersion, sources, offsetsTiers
`downloadable`	That build's package can actually be fetched now — from here if it is archived, from Roblox otherwise. This is the one to act on.	yes	from, stored, deployedAt, upcomingAt, sizeBytes, liveVersion, offsetsTiers
`upcoming_withdrawn`	The upcoming build was replaced before it went live.	recorded only	replacedBy, replacedByDisplayVersion
`live`	Production switched to this build.	yes	previousVersion, publishedAt, leadSeconds, offsetsTiers, source
`reverted`	Production went back to an older build.	yes	previousVersion, publishedAt, source
`archived`	A copy of the client package was stored here.	recorded only	key, sha256, sizeBytes, alreadyPresent, upcoming
`offsets`	A default offsets set appeared for a build at or ahead of production.	yes	tier, files, count, source
`offsets_verified`	A verified offsets set was published — from this point the build serves ours.	yes	files, count, replacedDefault, verifiedBy, dumper, dumperVersion, notes, lifecycle
`discovered`	Android: a new build appeared on the mirror.	yes	versionCode, kind, productionVersion
`abi_ok`	Android: the build carries the target ABI.	yes	abis, kind, sizeBytes
`abi_missing`	Android: the build ships no package for the target ABI.	yes	abis, kind

One release, end to end

The events a single Windows release produces, in the order they land. Timings are from 0.738.0.7381397, the release this was built around:

When	Event	What it means for you
T−5h 23m	`upcoming`	Roblox has named the next build. Nothing to download yet.
T−5h 23m	`downloadable`	The package is on the CDN. Dump it now.
T−4h 36m	`offsets`	theo published a dump for it. The build now serves the default tier.
any time after	`offsets_verified`	Ours is published and the build switches to it.
T	`live`	Production moved to the build. The message says how long the window was.

The window between downloadable and live is the whole reason upcoming builds are tracked: offsets published inside it are ready before most players have the build.

GET /api/v1/events

curl -s "https://rbxoffsets.com/api/v1/events?type=upcoming,live&limit=20"
curl -s "https://rbxoffsets.com/api/v1/windows/events?since=2026-09-09T00:00:00Z"

{
  "count": 1,
  "events": [
    {
      "id": 812,
      "platform": "windows",
      "type": "live",
      "version": "version-c5aecda2245e4fae",
      "displayVersion": "0.738.0.7381397",
      "at": "2026-09-09T22:30:41.000Z",
      "atEpochMs": 1788993041000,
      "payload": { "previousVersion": "version-e7d81637d42c4b23", "leadSeconds": 19395, "offsetsTiers": ["verified", "default"] },
      "page": "https://rbxoffsets.com/archive/windows/version-c5aecda2245e4fae"
    }
  ]
}

since takes ISO 8601 or epoch milliseconds, and returns strictly newer events — store the newest atEpochMs you have seen and pass it back. type takes a comma-separated list. limit is 1 to 200.

Atom feeds

https://rbxoffsets.com/feed.xml             upcoming builds, releases, reverts and offsets, every platform
https://rbxoffsets.com/windows/feed.xml     the same, one platform

Any feed reader works. Each entry links to the build's permanent page.

Discord

/subscribe takes an events option, so a channel can hear only upcoming builds and verified offsets, or only releases. /upcoming and typing upcoming windows in a watched channel answer on demand.