Command & Control - Ideas (2)
I found the time to play test the rules a few days ago and found a number of problems. See the Battle of Greenford for details. While playing I made a number of tactical errors, which were based on playing the game assuming normal control. One factor may cause problems in offense.defense games is that it increases the time that the attackers spend under fire, especially artillery.
Firstly as mentioned by Steve it's quite slow. The idea was mainly to provide a mechanism to allow solo play. I also found that by allowing for the casualty effect meant that non-commanded units had it a bit too easy. The solution to both is to drop the casualty effect from the calculation. It's already covered in a sense by the morale and other factors, so it is probably overkill.
As expected sending troops into woods caused command/control problems as they often missed the required dice roll, even if they were just 2 lower. Using the commander was similarly a problem. I hadn't added this as a factor, but given they have to fall back to do so then the command distance is increased and the issue is adequately covered this way.
I will now use the following
+2 if the commander is with the unit (attached)
-1 Per 12" away from the commander
-2 If out of sight of the commander
+1 if a well trained unit
-1 if a poorly trained unit
-1 "group" move (several units belonging to the same commander moving together)
+1 if the CinC is within 6" of the commander (optional)
After all command rolls are completed any individual units that have not tested for command can test independently needing a 3 of lower be be able to move (still with +/-1 for training).
Posts
2 comments:
Will - I was thinking further on this as I was cycling home the other day (probably should have been focussed more on the maniac car and lorry drivers!).. a long time ago, my regular opponent DG had a set of home grown rules that used a command & contraol mechanism based on the last order the unit had been give - thought it might work in conjunction with your test.
Using your mechanism this would work as follows - a unit is given an order to do something (advance to somewhere, fire at someone, etc.), and is then tested using the mechanism as you describe. The difference being that instead of being tested again, the unit is not tested again until that order is completed... the only concern I had is that it might increase the paperwork a little to figure out what all the units are doing???
Steve, you are obviously thinking along the same track as myself. I was thinking of creating a number of standard order cards to add behind the units.
Post a Comment