Page 1 of 1
Back up Plan Orders Question
Posted: Fri Jan 25, 2008 6:10 pm
by emcgman
Is it possible to give a backup plan order.
ie; Tell a Unit/HQ to defend/wait at a position until (x) time, and then move/attack another position.
Thanks
RE: Back up Plan Orders Question
Posted: Fri Jan 25, 2008 7:59 pm
by HansBolter
Not in the current game engine, but I believ sequential orders are on the list of desired items to be added in future versions.
RE: Back up Plan Orders Question
Posted: Fri Jan 25, 2008 9:48 pm
by Arjuna
Correct. Along with Triggers - ie conditional events that trigger the transition between one task and another. Eg Defend at X. If enemy enter Y then Attack Z.
RE: Back up Plan Orders Question
Posted: Sat Jan 26, 2008 2:38 am
by FredSanford3
That sounds like a neat feature. Is it going into BftB, or is that further down the road? I take it the "trigger" task wouldn't be subject to orders delay (except for the delay in initially assigning the order).
RE: Back up Plan Orders Question
Posted: Sat Jan 26, 2008 7:56 am
by Arjuna
No triggers would either be exempt any orders delay or have a significantly reduced delay period. I'll have to ponder that one some more, though. Good point. Thanks.
RE: Back up Plan Orders Question
Posted: Sat Jan 26, 2008 7:25 pm
by FredSanford3
It would seem to me that the orders delay for the 'trigger' portion of a task would be integral to the base task's orders delay. My reason for saying that is that I would imagine that the 'trigger' sub-task order would be promulgated simultaneously with the base task order. Something along the lines of "Col, take your Bn and defend region X. IF any enemies approach from direction Y, move to attack them immediately." This would be considered all one order, and the Bn commander would presumably take the potential attack scenario into his planning and subunit orders development.
Now, if for example a unit was already defending region X, and you then came along and added the contingency attack, then that would be another, separate order that would need to be planned, promulgated, and implemented and would thus incur it's own orders delay, as it wasn't a part of the orignal task order. Thus you couldn't game the system by adding a 'trigger' to deal with a sudden development and short-circuit the orders delay.
Seem reasonable?