Differences

This shows you the differences between two versions of the page.

--- ofp:modeling:tokennames [2007/07/10 09:52] – external edit 127.0.0.1
+++ ofp:modeling:tokennames [2024/07/31 16:14] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== Token Name Value Types ======
+====== OFP Token Name Value Types ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=43|OFP Forum]], [[:ofp|OFP Home]], [[ofp:file_formats|OFP File Formats]], [[ofp:tools|OFP Tools]], [[ofp:missions|OFP Missions]], [[ofp:modeling|OFP 3D Modeling]], [[ofp:terrain|OFP Terrain]]
+**Operation Flashpoint (OFP)** aka ArmA: Cold War Assault (CWA)
 **Token Name values**
-The ofp engine, and specifically, a raPified (binarised) file identifies only a few different 'types' of Token Name
+The ofp engine, and specifically, a raPified (binarized) file identifies only a few different 'types' of Token Name
 <code>
@@ Line 30: / Line 34: @@
 </code>
-A **boolean** as such, //does not exist// in binarised (raP) files. It is an integer. It is //only// a poetic licence for an author when creating text (config.cpp) files.
+A **boolean** as such, //does not exist// in binarized (raP) files. It is an integer. It is //only// a poetic licence for an author when creating text (config.cpp) files.
 ====== Integers ======
 <code>
  anInteger = 99;
 </code>
@@ Line 64: / Line 68: @@
 </code>
-this is **not** binarised into an integer (or a float), but remains 'in string'
+this is **not** binarized into an integer (or a float), but remains 'in string'
 See At the End of the Day for what actually happens to this 'string'.
@@ Line 70: / Line 74: @@
 ====== Arrays[]={...}; ======
 Arrays are of unrestricted content in terms of what 'types' they can have in them, and, their number.
 Arrays, can be (and often are) embedded within arrays.
@@ Line 100: / Line 104: @@
 ====== At the End of the Day ======
-The engine will always look at its raPified (binarised) data in the context it wants. A config.cpp - generally a text file - will always be processed into an internal config.bin (raPified) before use by the engine.
+The engine will always look at its raPified (binarized) data in the context it wants. A config.cpp - generally a text file - will always be processed into an internal config.bin (raPified) before use by the engine.
 Thus, while a value is stated to be a float
@@ Line 125: / Line 129: @@
 For examples of this duality see CfgVehicles Config Reference (coming soon snakenote)!