Map Event 1000 - Force the check of events in sequential order

[FS-21]

• By default, the game evaluates all map triggers in parallel. Adding this map event forces short-circuit evaluation as soon as any subsequent event returns false.
• This only affects evaluation from this control event (inclusive) to the last event in the list.
• All events placed before this control event still work in a non-short-circuiting manner.
• Sequential events will not begin evaluation until all preceding events have successfully completed.

In mycampaign.map:

[Events]
...
ID=EventCount,...,1000,0,0,0,...
...

[FS-21]

So if you have:

TRIGGER_ID=4,E1,E2,E3,E4
E1, E2, E3 & E4 are executed in parallel as always happened. Is the same as:
TRIGGER_ID=5,E1,E2,E3,E4,1000

TRIGGER_ID=5,1000,E1,E2,E3,E4
E1, E2, E3 & E4 are executed in sequential order.

TRIGGER_ID=5,E1,1000,E2,E3,E4
E1 is executed in parallel as always happened.
E2, E3 & E4 are executed in sequential order. Only start when all the parallel events are completed.

TRIGGER_ID=5,E1,E2,1000,E3,E4
E1 & E2 are executed in parallel as always happened.
E3 & E4 are executed in sequential order. Only start when all the parallel events are completed.

TRIGGER_ID=5,E1,E2,1000,E4
E1, E2, E3 are executed in parallel as always happened.
E4 is executed in sequential order. Only start when all the parallel events are completed.

[github-actions]

Nightly build for this pull request:

• compiled-dll-8eefb182e6c341d3649390bc1d4f750274489912.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.