Skip to content

Object Fields

Shais2304 edited this page Mar 25, 2015 · 23 revisions

The game objects in ToEE are based on a generic object model that uses a field list. Each field has a numeric index. Those indices are documented here. The first 40-50 fields or so are mixed up and we are still trying to figure out why.

Confirmed fields:

Field Name Index Remarks
obj_f_location 1 DLL erroneously says obj_f_current_aid; field type is 4 (64bit) so it matches location (locx:locy); also from PyObj GetAttr
obj_f_offset_x 2 DLL erroneously says obj_f_location; field type is 0xF (float) so it matches offset_x
obj_f_offset_y 3 DLL erroneously says obj_f_offset_x; field type is 0xF (float) so it matches offset_y
obj_f_flags 22 From debug msgs; as opposed to 19 in the DLL names list
obj_f_name 24 From PyObject GetAttr (DLL lists this as obj_f_aid)
:from here on seems to be true to the DLL specifications
obj_f_hp_damage 29 confirmed by scripting etc.
obj_f_speed_run 36 We manipulate this via script all the time for testing purposes (speedup() from batch.py)
obj_f_radius 39 referenced in the function from the PyObj GetAttr for 'radius'
obj_f_dispatcher 45 Used all over the place
obj_f_npc_pad_i_3 379 This actually stores joinable NPCs' loot behavior type

Clone this wiki locally