If the name contains variables, they will be substituted each time the event is triggered. Spaces in event names can be interchanged with underscores (for example, name=new turn and name=new_turn are equivalent). Any value not listed there is a custom event name which can be triggered only by a tag somewhere else. * Note that unless you use first_time_only=no, the event will fire only once, not once for each listed type.Īll predefined event types are listed below, along with a description of when this value will cause the event to be triggered, in the Predefined Events Without Filters and Predefined Events With Filters sections. However, this distinction is usually unimportant in most discussions and the event handlers are therefore simply referred to as "events" in this documentation. Lexicon side note: The word "event" in the tag itself may be considered an abbreviation of the word "event handler" because it is technically not a game "event" but an event handler for the game events fired with the given 'name'. All of the others can be used or not and the event actions will fire either way. Therefore, from a practical standpoint, it can be considered mandatory. Without it, no error will be raised but the event will never fire. This tag has keys and child tags that control when and if the event actions will be triggered. When used in an, the event will occur in any scenario which is played using that era. When used in a tag, the event will occur in all scenarios in which a unit of that type appears in (only after such a unit appears during the scenario, however). When used in a tag (also includes, and ), the event only occurs in that scenario. This tag is a subtag of the, and tags which is used to describe a set of actions which trigger at a certain point in a scenario. 6.3 Delayed Variable Substitution Example.6.1 Primary/Secondary Unit Speaker Example.5.25 unit placed (Version 1.13.3 and later only).5.5 pre attack (Version 1.17.7 and later only).
0 Comments
Leave a Reply. |