Skip to content

Documentation versions

OED export ​

An Engine Atlas card explains a class to a person. An OED file gives the same knowledge to a program: it tells a mod's build where a function lives in the game, how to call it and when that is safe. The file turns into ordinary C++, so a mod works with the engine without hunting for addresses by hand.

OED (Octane Engine Definition) is a text file describing the link between a mod and one exact version of libasphalt8.so. A single line says roughly this:

text
method MainMenu.classId id=oed.game.class_id module=game result=ptr rva=0x7a32f8 isa=arm thread=any phases=active,stop

This is the classId method of the MainMenu type: it returns a pointer, lives at address 0x7a32f8 and may be called in the listed phases of a mod's work.

Getting the file ​

Open a class and press Export OED next to Show in list. The browser downloads a file named after the class. Through Engine Atlas MCP, ask the model for the same file:

Export the OED for GS_MainMenu.

The button appears on classes that have something to export: studied classes and classes with confirmed bindings.

What is inside ​

LineWhat it means
A plain lineA confirmed binding. A mod can rely on it
A line starting with # methodA draft from the card. It does nothing until confirmed
thread=?, phases=?, result=?Research has not established this yet

Drafts save you from starting empty: the address, instruction mode and known types are already there. To make one work, establish what is missing from the game's code, replace the ? and remove the #. A guess is worse than a gap here: a wrong argument type or thread crashes the game.

What the file does not do ​

  • It does not change the game and is not a mod. It is a description used by a mod's build.
  • It does not replace checking. A method on a card is not proof that calling it is safe.
  • It fits only the libasphalt8.so version named inside it. Any other library is refused at startup.

Edits in edit mode do not affect the file: it reflects published data.