ObjCondition Triggered: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Description''' | '''Description''' | ||
---- | ---- | ||
Triggered conditions are marked complete when they receive an event that matches their 'tag'. Triggered conditions have the lowest CPU overhead of any of the conditions which makes them a good choice if you want to render an icon somewhere in the level or some other form of 'dummy' | Triggered conditions are marked complete when they receive an event that matches their 'tag'. Triggered conditions have the lowest CPU overhead of any of the conditions which makes them a good choice if you want to render an icon somewhere in the level or some other form of 'dummy' behavior which doesn't contribute to the objective's completion state. | ||
'''Configurable Properties''' | '''Configurable Properties''' | ||
Latest revision as of 17:01, 6 November 2013
Description
Triggered conditions are marked complete when they receive an event that matches their 'tag'. Triggered conditions have the lowest CPU overhead of any of the conditions which makes them a good choice if you want to render an icon somewhere in the level or some other form of 'dummy' behavior which doesn't contribute to the objective's completion state.
Configurable Properties
| Variable Name | Variable Type | Description |
|---|