TokenNameValueTypes: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (FloatTokenNames moved to TokenNameValueTypes: made a single page (and therefor single link) to all the separate bools, ints, string, and array definitions. It's a small 'quick read' blurb for each 'type' and dont require separate pages as such.) |
(No difference)
|
Revision as of 06:17, 1 July 2006
Token Name values
The ofp engine, and specifically, a binarised file (signature raP) identifies only a few different 'types' of Token Name
aString = "A string"; anInteger = 1234567; aFloat = 0.0123; anArray[] = {.....};
Everything that can be stated in a config.cpp, a description.ext, a mission.sqm for TokenName value pairs devolves to one of the above 'types'.
Separately, a fifth type exists called boolean.
aBoolean = 0;
In fact the engine only stores and 'sees' this value as an integer. But by convention in humanly readable text files (config.cpp vs config.bin), integers that can only have zero or non zero values are declared in statements as
#define false 0 #define true 1
LightOn = true;