Game updates
How Wax keeps up with each new build of ICARUS, and where the classes of the game can be read.
ICARUS is updated most weeks. Each update can add classes, rename a variable or change a table. A server reads every new build of the game by itself and writes down what is in it, so the Explorer and the editor's completion follow the game without anyone doing it by hand.
The state right now
Reading the status.
What happens on an update
- The server asks Steam every ten minutes which build of the dedicated server is out.
- For a new build it downloads the game's program, its debug file and its content files. A DLC arrives the same way, as more content files.
- It reads every class the program declares and every blueprint class in the content, each with its parent, its variables and its functions. The game is never started.
- It writes the result to the Icarus SDK repository and sends the new list of classes to the Explorer on this site.
A whole run takes about half an hour.
What you can read
The Icarus SDK repository holds, for the newest build:
| Folder | What is in it |
|---|---|
cpp | Every class and struct as a C++ header to read: what it derives from, each variable with its place, each function with its parameters |
types/icarus | The same classes as definitions for the Lua language server |
model | The whole model as one JSON file, for tools |
changes | What each update changed: classes, members and table rows |
pipeline | The scripts that make all of it |
The dedicated server is read because Steam gives it to anyone. Its code is the game's own. A few classes that only the game's client has are missing.