Location: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (locations defined in config, not wrp) |
||
Line 6: | Line 6: | ||
*They can be attached to objects, with all of the location's relevant properties automatically updating if the object moves (frequency unknown). | *They can be attached to objects, with all of the location's relevant properties automatically updating if the object moves (frequency unknown). | ||
*They can use setVariable and getVariable. | *They can use setVariable and getVariable. | ||
*Existing locations | *Existing locations defined in an island/terrain's config can not be changed using the location script commands, but they can be found and read. This provides a single command method of finding nearby high points, towns, etc. |
Revision as of 22:26, 26 November 2007
A location is like an extended type of marker. I don't know when the commands were introduced, but I found them in 1.08.
- Locations have a name, a side, a 3D position, an 2D area, and an orientation.
- They have a non-scaling map representation (icon &/or text, depending on class).
- They require a class definition to define basic properties that cannot be changed using script commands (text size, font, colour, icon type). Classes are defined in bin\Config.bin\CfgLocationTypes
- They can be attached to objects, with all of the location's relevant properties automatically updating if the object moves (frequency unknown).
- They can use setVariable and getVariable.
- Existing locations defined in an island/terrain's config can not be changed using the location script commands, but they can be found and read. This provides a single command method of finding nearby high points, towns, etc.