FFlags and dump files

Windows · macOS · Android · home

A dump is more than the offsets header. Every file below can exist in either tier; which ones a particular build has depends on what its dumper produced, and the files list says exactly.

FileKindWhat is in it
offsets.hppoffsetsThe offsets as a C++ header — the format most externals include directly.
offsets.jsonoffsetsThe structured source. Carries the dump's own description: total count, dump time, dumper name and version, and the build it belongs to.
offsets.csoffsetsThe offsets as a C# class.
offsets.txtoffsetsA flat table, for reading or grepping.
offsetshex.jsonoffsetshexThe same JSON with every value written in hexadecimal.
struct.hppstructClass and structure layouts, as C++.
types.jsontypesThe type of every offset, keyed like offsets.json.
fflags.hppfflagsFast flags and their addresses, as a C++ header.
fflags.jsonfflagsFast flags as JSON, decimal values.
fflags.csfflagsFast flags as a C# class.
fflags.txtfflagsFast flags as a flat table. Not every dump has it.
fflagshex.jsonfflagshexFast flags as JSON, hexadecimal values.

A verified upload may also carry files of its own — any plain name ending in .json, .hpp, .h, .cs, .txt, .lua, .py or .rs — listed with kind extra. Unpacked client binaries are never stored as offsets files, whatever an upstream listing carries.

What a build has

curl -s https://rbxoffsets.com/api/v1/windows/offsets/latest/files
curl -s "https://rbxoffsets.com/api/v1/windows/offsets/version-c5aecda2245e4fae/files?tier=default"

Fetching one

# the four offsets formats keep their short form
curl -sLO https://rbxoffsets.com/api/v1/windows/offsets/latest/hpp

# any file by name, in whichever tier is served
curl -sL -o struct.hpp https://rbxoffsets.com/api/v1/windows/offsets/latest/struct.hpp

# FFlags have a shorthand
curl -sL -o fflags.json https://rbxoffsets.com/api/v1/windows/fflags/latest/json

# one exact tier
curl -sL -o fflags.hpp https://rbxoffsets.com/api/v1/windows/offsets/version-c5aecda2245e4fae/default/fflags.hpp

Size

The offsets files are tens of kilobytes. The FFlags files are around a megabyte each, which is why an operator can choose not to mirror them — in which case they are simply absent from the default set's file list, never an error.