Road Marching and Frustration, Frustration, Frustration...
Posted: Fri Nov 16, 2012 5:46 am
I would first like to pose a question: Do any scenario designers use move commands with along with the use roads feature? And do any of the multiple features the game provides work?
Because I have noticed that in most of the scenarios I've created, REGIMENTS WILL NEVER USE THE DAMN ROADS!
Sorry, I got a little heated for a second.
It is easy enough to make a commander, or an entire command, use a road: simply use (A)moveto and (A)useroad. Or use (A)roadmarch. The frustrating part is making regiments use the road.
To address the entire situation, I should note that there are 4 ways to make unit(s) use roads according to the SDK Version 1.06:
forcepath - A regimental command only, it directs the named unit to move via roads.
Example given in SDK: TIME, UNIT ID (Regiment), forcepath, location x, location z.
movepath - Command combines moveto and useroad. For brigade and higher sized units.
Example: TIME, UNIT ID (Commander), movepath, location x, location z.
(A)roadmarch - Commands the a unit to use the road, bypassing the “useroad” command.
Example: TIME, UNIT ID, (A)roadmarch, location x, location z
(A)moveto + (A)useroad - Commands unit to move to location via roads.
Example: TIME, UNIT ID, (A)moveto, location x, location z
TIME, UNIT ID, (A)useroad
Unfortunately, not all of these work, and the ones that do work don't always work to the intended purpose.
Through scenario scripting, I have found that when the command is used on a leader and subordinates:
Aroadmarch = march on road + road column at destination
Amovepath = road column at destination
Aforcepath = nothing
Amoveto + Auseroad = march on road + road column at destination
(I'm assuming the road coluumn at destination is due to the commander's current "formation".)
When the command is used just on a commander:
roadmarch (on leader) = march on road to destination
movepath (on leader) = march to destination
forcepath (on leader) = nothing
moveto + useroad (on leader) = march on road to destination
And when the command is used on a regiment only:
roadmarch (on unit) = march to destination
movepath (on unit) = march to destination
forcepath (on unit) = nothing
moveto + useroad (on unit) = march to destination
So why is there such a discrepancy between the SDK and scripting? Am I doing something wrong in my scripting, or is the SDK out of whack?
Looking at the gui.csv, I have noticed that the forcepath is not actually used with a destination, indicating an incorrect definition in the SDK. Perhaps the rest of these are in a similar boat, most notably the movepath command, which doesn't use the paths at all.
Hopefully, the team can look into this matter and see if it is any easy fix. If the problem merely resides in the SDK, I would be very willing to test out every command and write up a correct discription with example for the community.
Thanks for your support.
Because I have noticed that in most of the scenarios I've created, REGIMENTS WILL NEVER USE THE DAMN ROADS!
Sorry, I got a little heated for a second.
It is easy enough to make a commander, or an entire command, use a road: simply use (A)moveto and (A)useroad. Or use (A)roadmarch. The frustrating part is making regiments use the road.
To address the entire situation, I should note that there are 4 ways to make unit(s) use roads according to the SDK Version 1.06:
forcepath - A regimental command only, it directs the named unit to move via roads.
Example given in SDK: TIME, UNIT ID (Regiment), forcepath, location x, location z.
movepath - Command combines moveto and useroad. For brigade and higher sized units.
Example: TIME, UNIT ID (Commander), movepath, location x, location z.
(A)roadmarch - Commands the a unit to use the road, bypassing the “useroad” command.
Example: TIME, UNIT ID, (A)roadmarch, location x, location z
(A)moveto + (A)useroad - Commands unit to move to location via roads.
Example: TIME, UNIT ID, (A)moveto, location x, location z
TIME, UNIT ID, (A)useroad
Unfortunately, not all of these work, and the ones that do work don't always work to the intended purpose.
Through scenario scripting, I have found that when the command is used on a leader and subordinates:
Aroadmarch = march on road + road column at destination
Amovepath = road column at destination
Aforcepath = nothing
Amoveto + Auseroad = march on road + road column at destination
(I'm assuming the road coluumn at destination is due to the commander's current "formation".)
When the command is used just on a commander:
roadmarch (on leader) = march on road to destination
movepath (on leader) = march to destination
forcepath (on leader) = nothing
moveto + useroad (on leader) = march on road to destination
And when the command is used on a regiment only:
roadmarch (on unit) = march to destination
movepath (on unit) = march to destination
forcepath (on unit) = nothing
moveto + useroad (on unit) = march to destination
So why is there such a discrepancy between the SDK and scripting? Am I doing something wrong in my scripting, or is the SDK out of whack?
Looking at the gui.csv, I have noticed that the forcepath is not actually used with a destination, indicating an incorrect definition in the SDK. Perhaps the rest of these are in a similar boat, most notably the movepath command, which doesn't use the paths at all.
Hopefully, the team can look into this matter and see if it is any easy fix. If the problem merely resides in the SDK, I would be very willing to test out every command and write up a correct discription with example for the community.
Thanks for your support.