ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
Events: Difference between revisions
Jump to navigation
Jump to search
m Woops, category sort order |
m Fixed actions link |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{WrongTitle|[Events]}} | {{WrongTitle|[Events]}} | ||
{{ | {{MappingBar}} | ||
Events are, obviously, conditions that, once met, fire their corresponding [[Maps/Triggers|Trigger]]. Different games have different available Events and code for them. | Events are, obviously, conditions that, once met, fire their corresponding [[Maps/Triggers|Trigger]]. Different games have different available Events and code for them. | ||
| Line 7: | Line 7: | ||
== Section == | == Section == | ||
=== | === <span id="td"></span>{{td}} === | ||
[[ | [[Events/TD|List Of Available Events]] | ||
Section didn't exist, events were specified inline in the [{{Tt|[[ | Section didn't exist, events were specified inline in the [{{Tt|[[Triggers#td|Triggers]]}}] section with only one condition per trigger. | ||
=== | === <span id="ra"></span>{{ra}}, {{cs}}, {{am}} === | ||
[[ | [[Events/RA|List of Available Events]] | ||
Section didn't exist, events were specified inline in the [{{Tt|[[ | Section didn't exist, events were specified inline in the [{{Tt|[[Triggers#ra|Triggers]]}}] section with up to two conditions per trigger. | ||
=== | === <span id="ts"></span>{{ts}}, {{fs}} === | ||
[[ | [[Events/TSFS|List of Available Events]] | ||
The typical [Events] section looks like this: | The typical [Events] section looks like this: | ||
| Line 43: | Line 43: | ||
Additional conditions are listed in the same manner. | Additional conditions are listed in the same manner. | ||
=== | === <span id="ra2"></span><span id="yr"></span>{{ra2}}, {{yr}} === | ||
[[ | [[Events/RA2YR|List of Available Events]] | ||
The typical section looks exactly like in TS, except certain conditions take on a third parameter - a string: | The typical section looks exactly like in TS, except certain conditions take on a third parameter - a string: | ||
| Line 71: | Line 71: | ||
== See Also == | == See Also == | ||
*[[ | *[[Triggers]] | ||
*[[ | *[[Actions_(maps)|Actions]] | ||
Latest revision as of 07:23, 2 May 2021
This page should correctly be named "[Events]"; it is wrong due to technical restrictions.
Events are, obviously, conditions that, once met, fire their corresponding Trigger. Different games have different available Events and code for them.
Section
Tiberian Dawn
Section didn't exist, events were specified inline in the [Triggers] section with only one condition per trigger.
Red Alert, Counterstrike, Aftermath
Section didn't exist, events were specified inline in the [Triggers] section with up to two conditions per trigger.
Tiberian Sun, Firestorm
The typical [Events] section looks like this:
[Events] ID=NUM,E1,E1P1,E1P2 ID1=NUM2,E1,E1P1,E1P2,E2,E2P1,E2P2
The meanings are as follows:
| String | Meaning |
|---|---|
| ID | The Event's ID. Has to be the same as the Trigger's ID. |
| NUM | Amount of conditions in this Event. |
| E1 | The first condition (its index in the Available Events list) |
| E1P1 | The first parameter for E1, defaults to 0 |
| E1P2 | The second parameter for E1, defaults to 0 |
Additional conditions are listed in the same manner.
Red Alert 2, Yuri's Revenge
The typical section looks exactly like in TS, except certain conditions take on a third parameter - a string:
[Events]
ID=NUM,E1,E1P1,E1P2
ID1=NUM2,E1,E1P1,E1P2,E1P3,E2,E2P1,E2P2
| String | Meaning |
|---|---|
| ID | The Event's ID. Has to be the same as the Trigger's ID. |
| NUM | Amount of conditions in this Event. |
| E1 | The first condition (its index in the Available Events list) |
| E1P1 | The first parameter for E1, defaults to 0 |
| E1P2 | The second parameter for E1, defaults to 0 |
| E1P3 | The third (optional) parameter for E1 |
Again, additional conditions are specified in the same manner.