|
|
| Line 28: |
Line 28: |
| ! Property | | ! Property |
| ! Type | | ! Type |
| |-
| |
| | '''Type'''
| |
| | Type
| |
| | Object class.
| |
| | <small><tt>itemClass</tt></small>
| |
| | [[String]]
| |
| |-
| |
| | '''Variable Name'''
| |
| | Init
| |
| | Unique system name. Can contain only letters, numbers and underscore. The name is not case sensitive, so 'someName' and 'SOMENAME' are treated as the same variables.
| |
| | <small><tt>Name</tt></small>
| |
| | [[String]]
| |
| |-
| |
| | '''Init'''
| |
| | Init
| |
| | Expression called upon at start. In multiplayer, it is called on every machine and for each player who joins in the progress. The variable 'this' refers to the affected object.
| |
| | <small><tt>Init</tt></small>
| |
| | [[String]]
| |
| |-
| |
| | '''Position'''
| |
| | Transformation
| |
| | World coordinates in meters. X goes from West to East, Y from South to North and Z is height above terrain.
| |
| | <small><tt>position</tt></small>
| |
| | [[Position3D]]
| |
| |-
| |
| | '''Rotation'''
| |
| | Transformation
| |
| | Local rotation in degrees. X is pitch, Y is roll and Z is yaw.
| |
| | <small><tt>rotation</tt></small>
| |
| | [[Number]]
| |
| |-
| |
| | '''Placement Radius'''
| |
| | Transformation
| |
| | Placement radius in meters. The entity will start at a random position within the radius.
| |
| | <small><tt>placementRadius</tt></small>
| |
| | [[Number]]
| |
| |-
| |
| | '''Player'''
| |
| | Control
| |
| | Player in singleplayer. When enabled, the character will also be available in multiplayer and team switch ('Playable' status cannot be disabled individually in such case).
| |
| | <small><tt>ControlSP</tt></small>
| |
| | [[Bool]]
| |
| |-
| |
| | '''Playable'''
| |
| | Control
| |
| | When enabled, the character will appear as a slot in the multiplayer scenario lobby and in the list of roles available for team switch.
| |
| | <small><tt>ControlMP</tt></small>
| |
| | [[Bool]]
| |
| |-
| |
| | '''Role Description'''
| |
| | Control
| |
| | Multiplayer role description visible in the multiplayer lobby. When undefined, the object type name will be used by default.
| |
| | <small><tt>description</tt></small>
| |
| | [[String]]
| |
| |-
| |
| | '''Probability of Presence'''
| |
| | Presence
| |
| | Probability of presence evaluated at the scenario start. When it fails, the object is not created at all.
| |
| | <small><tt>presence</tt></small>
| |
| | [[Number]]
| |
| |-
| |
| | '''Condition of Presence'''
| |
| | Presence
| |
| | Condition of presence evaluated at the scenario start, must return boolean expression. When false, the object is not created at all.
| |
| | <small><tt>presenceCondition</tt></small>
| |
| | [[String]]
| |
| |} | | |} |
| </onlyinclude> | | </onlyinclude> |
A system is a virtual object which can expand your scenario with a new functionality.
A module provides complex functionality which would otherwise have to be scripted. It can usually be configured using custom attributes, and can sometimes be affected by synchronization connections. For example, many modules are activated only once all the synchronized triggers are active. To see more about the individual modules, explore their attributes.
A logic entity is simply a virtual object, without any inherent functionality. It is mainly used in cooperation with modules or scripts, for example, to mark positions and their relations.
Some Virtual Entities are playable. They are used in multiplayer for abstract roles such as a spectator or headless client.
Be sure to investigate all the available systems, especially modules. Because each has its own rules, do not forget to also check their attributes.
Attributes
| Info
|
Development
|
| Name
|
Category
|
Description
|
Property
|
Type
|