Home › ArtDef vocabulary

ArtDef vocabulary

Art definitions (.artdef XML files in ArtDefs/ folders of the base game and every DLC) tell the renderer, the unit system, the lenses and the audio how things look and behave. The engine executable reads them with ConfigureFromArtDefs-style functions that ask for collections and parameters by name. This section lists, for each artdef type (the m_TemplateName stored in the file), the collection and parameter names the exe asks for, the value class each parameter has in the shipped files (Float, Int, Bool, String, Coord2D, RGB, ArtDef reference, BLP entry, ...), how many shipped files use it, and which parameter names the exe never asks for.

What is verified and what is inferred. The names in the exe and the value classes and counts in the shipped files are Verified (strings referenced by a function, names counted in the files; no values or asset paths are kept). Which artdef type a function belongs to is Inferred: a function is assigned to the type whose names cover at least half of the names the function uses and clearly more than any other type (53 of 66 functions are assigned; the rest are listed below). "Not read by the exe" means the name is in shipped files but not in the strings of the assigned functions; it may be read by a function that is not assigned, by a shared helper (for example the keyframe fields Time, FOV and Tilt of the camera curves are read by common curve code), or be unused.

For modders. The names listed are the ones the exe code looks up, so they are the names worth using in a new artdef; a parameter that no function looks up is probably without effect (not tested in the game: the exe may also log or reject unknown names). The value classes show how the shipped files store each parameter; the exe code reads a parameter through its own typed accessor, so keep to the class the shipped files use. See also the files and paths page for where the game looks for ArtDefs folders.

Artdef types

Functions not assigned to a type (13)