After my post about stacking orders for spawn
I have been playing with them in hotseat to figure out how this works, especially in situations where a direct attack order proves impossible to carry out - i.e. because the route to the redlined unit is blocked.
I seem to pull up 2 different results
1) drone just stops, and waits
or,
2) order gets cancelled and the drone then attacks nearest target.
It was suggested by Vasco that losing LoS cancels the order enabling you to stack attack orders, so that your drone would carry out the rest of the orders. But I can't get this to work - either all orders get cancelled (regardless of LoS), or it sits there and waits (whether or not it has LoS) - I got one drone to stop about 7 metres from a line of blocking drones and then stand there for the rest of the turn, even though LoS to its target had long since gone...
Stacking direct attack orders simply does not appear to work, unless the drone is able to kill its first target, then it will move onto its second.
However for the Queen none of this applies - regardless of the situation, if the Queen is unable to bite a redlined target, then her orders ALWAYS get cancelled, and she will then bite nearest target. In testing she NEVER sat there and did nothing...
Does anyone know how the client decides whether a spawn should wait to carry out a direct attack order, or whether it will cancel the order and then go to the rules of engagement?
My theory is - that if you specify a direct attack order which is impossible at the start of the turn it just gets cancelled, and then the rules of engagement apply. If however you specify a unit that you can reach at the start, which then moves so that a path to it is blocked then you get the stopping and waiting (although this didn't happen in every case - I just can't figure out what the difference is - p'raps the code has got bugs in it hence the inconsistencies)
Old enough to know better. Young enough not to care...
I have been playing with them in hotseat to figure out how this works, especially in situations where a direct attack order proves impossible to carry out - i.e. because the route to the redlined unit is blocked.
I seem to pull up 2 different results
1) drone just stops, and waits
or,
2) order gets cancelled and the drone then attacks nearest target.
It was suggested by Vasco that losing LoS cancels the order enabling you to stack attack orders, so that your drone would carry out the rest of the orders. But I can't get this to work - either all orders get cancelled (regardless of LoS), or it sits there and waits (whether or not it has LoS) - I got one drone to stop about 7 metres from a line of blocking drones and then stand there for the rest of the turn, even though LoS to its target had long since gone...
Stacking direct attack orders simply does not appear to work, unless the drone is able to kill its first target, then it will move onto its second.
However for the Queen none of this applies - regardless of the situation, if the Queen is unable to bite a redlined target, then her orders ALWAYS get cancelled, and she will then bite nearest target. In testing she NEVER sat there and did nothing...
Does anyone know how the client decides whether a spawn should wait to carry out a direct attack order, or whether it will cancel the order and then go to the rules of engagement?
My theory is - that if you specify a direct attack order which is impossible at the start of the turn it just gets cancelled, and then the rules of engagement apply. If however you specify a unit that you can reach at the start, which then moves so that a path to it is blocked then you get the stopping and waiting (although this didn't happen in every case - I just can't figure out what the difference is - p'raps the code has got bugs in it hence the inconsistencies)
Old enough to know better. Young enough not to care...
