RF Online data reference

The reference is organised by categories of game data. Each category has an overview (what it is and how it works), the list of its files in the registry, tables of used fields for every file and, at the end, a separate section of unused fields. Offsets are counted from the start of the record, in hexadecimal.

Field statuses

• known — the server or the client reads the field; its meaning is established from code, file bytes or an in-game check;
• derived — a client-file field that the build computes from server data (or vice versa); it is never edited on its own;
• unused — no reader found: the field is preserved byte for byte but affects nothing.

Registry levels

“ready for full” — the format is understood and the fields are described; “derived” — the file is assembled from another; “opaque” — the format is not fully known; “postponed” and “out of scope” — the studio does not edit the file.

The source is the RF Dev Studio research: per-domain digests (disassembly of the ZoneServer and the AoP client, reading the AoP, GU 2.2.3.2 and Sirin corpora, in-game checks) and the machine field catalog built from them. Values in the “Data” column are test content of the GU corpus (AoP when the file is absent): they show how the field is filled, not a rule.

Coverage