Difference between revisions of "Globals"
Jump to navigation
Jump to search
imported>GhanBuriGhan (Added to glossary) |
imported>Scruggs (added note) |
||
| Line 10: | Line 10: | ||
*'''Value:''' The default value for the global variable. This affects the variable only when the plugin was just installed. After that the value is stored in the savegame. | *'''Value:''' The default value for the global variable. This affects the variable only when the plugin was just installed. After that the value is stored in the savegame. | ||
==Notes:== | |||
* In almost all cases, using a global variable is unnecessary. Variables defined in quest scripts are generally used instead, and accessed via '''questID.varName''', or '''getQuestVariable questID varName'''. | |||
==See also== | ==See also== | ||
Revision as of 11:52, 8 August 2006
A global variable is available for any script or condition to reference without being linked to a particular quest or object.
Global variables are declared in the main menu under Gameplay -> Globals
- EditorID: The name of the variable. No spaces or special characters are allowed.
- Variable Type: Short and Long are actually the same thing. Both are integer formats. Float is a real number format. Internally all types of global variables are stored as 32-bit floats. The technical implementation of this variable-format causes inaccuracies at very high or low values. (e.g all numbers from 2000000000 to 2000000064 are stored as 2000000000)
- Value: The default value for the global variable. This affects the variable only when the plugin was just installed. After that the value is stored in the savegame.
Notes:
- In almost all cases, using a global variable is unnecessary. Variables defined in quest scripts are generally used instead, and accessed via questID.varName, or getQuestVariable questID varName.