Way points and conditional route questions.

[IamKirk]

#1

When a unit arrives at a way point and there are conditional routes leading from that way point, does the unit take the first route that is true or does it check all conditional routes and then take the true route?

Question behind the question: I am wondering that if there are two true conditional routes will the unit get stuck, or will it take the first true conditional route and ignore the other one?

 

#2

In regards to XNew variable getting a new random value for each conditional, how often are the conditional routes checked when a unit arrives at the way point?  Are the conditionals only checked once upon arrival or are they checked multiple times at some frequency after arrival?

 

#3

If the way point has 4 routes leading from it where 1 is not conditional, but the other 3 are, will the unit ever choose one of the conditionals provided that one of them is true, or it will always choose the unconditional route regardless of the other 3 conditional routes?

[Rotareneg]

1. It will take the first route evaluated to be true, checked in order of last route added to the originating waypoint to the first route added.
2. The "new" variable is rolled once for each conditional route at a waypoint, meaning each conditional route at a waypoint gets it's own independent "new" variable. It doesn't reroll the "new" variable as long as that unit remains at the waypoint, but other conditions are continuously monitored.
3. Unconditional routes are taken if no conditional routes are true, again taken in order of last route added to the first route added.

Edited October 11, 2020 by Rotareneg

[Ssnake]

#1 it takes the "first" true embark condition, whichever that may be (there is no way to predict that). So, ideally, construct the scenario in a way that the conditions are mutually exclusive.

 

#2 on arrival, and whenever other co-conditions are checked (as long as no condition is true, they get all checked at regular intervals (e.g. to satisfy "delay before checking" options)

 

#3, the ones with conditions will be checked first. and if the waypoint has a tactic other than "none", the unit will remain in the vicinity until either one of the explicit conditions is satisfied, or if an implicit condition (see user's manual, chapter eight) is met for the unconditioned route.

[stormrider_sp]

6 hours ago, Ssnake said:

#1 it takes the "first" true embark condition, whichever that may be (there is no way to predict that). So, ideally, construct the scenario in a way that the conditions are mutually exclusive.

 

#2 on arrival, and whenever other co-conditions are checked (as long as no condition is true, they get all checked at regular intervals (e.g. to satisfy "delay before checking" options)

 

#3, the ones with conditions will be checked first. and if the waypoint has a tactic other than "none", the unit will remain in the vicinity until either one of the explicit conditions is satisfied, or if an implicit condition (see user's manual, chapter eight) is met for the unconditioned route.

I think I never understood the delay before checking timing. Is its main purpose to allow for re-sorting the order at which the conditioned routes are checked?

[Ssnake]

Upon arrival on a waypoint, a unit may not have the necessary information yet to make an informed decision about which route to take next (e.g. "unit (this) can see enemy units in region (X)" - how would it know without being given time to look at that region X first?).

The delay before testing option gives the unit time to observe before deciding.