Home › Engine executable › Event data fields

Event data fields (as read by the exe)

Each GameCore bus event carries a small data object. This page lists, for 109 events, the fields the exe's own handlers read from it: the byte offset, the width in bytes, how many analysed handlers read it, and constants a handler compares a field with. It was recovered by tracing how the decompiled handlers use the event data parameter (138 handlers of the renderer, audio, telemetry, UI and network systems).

Offsets are from the start of the event data object. A plot is typically two 4-byte fields (x, y) that some handlers read as one 8-byte value, so only the wider read is shown. The Lua parameter column is the parameter list of the matching Lua event from the GameCore reference; where the number of fields equals the number of Lua parameters (9 events) the order is probably the same, otherwise the two lists are only shown side by side. Fields that no analysed handler reads are not listed, and the field names are not in the exe.

Reliability. Inferred: handler addresses for the 3D renderer were matched to the Linux build by registration order, a wrong match would show another event's fields; handlers that take the event as a second parameter were assumed to do so; reads through an unresolved indirect call are missed. The method was checked on TERRAIN_STATE_CHANGED (the plot at 4 and 8, shown as one field, the state hash at 0xc, the set-or-clear flag at 0x10), which matches a hand disassembly.