I posted a list of these functions about a month ago in the discussions . It seems those functions are defined in the Lua scripting engine that's included in the game.

I don't have the script anymore that I used to dump the function list, because they updated the file that I had edited. But yeah, have fun :)

Indeed, those are defined in metatables which I can't dump safely. Hopefully a full documentation will be released soon. In the meantime, you'll need to inspect the EXE directly.

Useful, thanks! But this still doesn't seem to show the whole story: for example given an element "instruction" of a "code" subtable, you can do "instruction:GET_OPCODE_NAME()" which returns a string. This must involve some sort of metatable stuff or other magic.

We can see several more of those magic methods being used in Scripts/Disassembly.lua and other files. I wonder what the complete set of magic methods is.

Small update: Now the mod is dumping everything, so it's possible to easily compare the source code in Data/Scripts to its disassembly.

Still easy enough to do it in a reasonable amount of time I see ;)
I can confirm it works. The assembly is way easier to read now! Thanks!

Good idea Archomeda! This was easier said than done, but I've updated the mod to do so. Now tables with less than 2 elements will appear on the same line, except if it has 1 element that is itself a table.

Certainly very useful :)
I did this myself as well, but I didn't automate it for all files, only the ones I needed so far. Nicely done!

One small request though, can you change the output of the code tables? At the moment it shows for example:
1 = GETGLOBAL 0 0 {
instruction = number: 5
}
I would like to have it a bit more readable on one line:
1 = GETGLOBAL 0 0 { instruction = number: 5 }
From 3 lines to only 1 line per instruction. Especially with large files this can make a huge difference when scrolling.