ORIGINAL: Arjuna
ORIGINAL: wodin
...maybe Im being chicken and should grab the bull by the horns and get on with it...
Yep just go for it. The best way to learn is trial and error. And the good thing about a computer game against the AI is that no one needs to know how badly you did the first time through. [:)]
I used this technique to great effect during my playtesting.
Since I was testing and needed to be able to provide fedback and saved games just prior to CTDs I made a policy of saving every hour of game time. My saves took on a structure of "Scenario name"-"Day"-"Time" (example: Race for Bastogne-D2-1300).
This kept saved games in chronological order and allowed me to easily go back to any save point and "try again". If it took 6 hours of game time for me to discover my plan was flawed, I would simply go back 6 hours and try something different.
This is obviously something one could never do in a head to head game, or should be done if one is testing one's own prowess against the AI, but it is a tremendous tool for learning how things work, how long it takes for your troops to respond to your orders and accomplish the tasks set for them and for determining "what one should do" in terms of issuing orders and geting the ball rolling from the scenario start.
I strongly suggest that anyone who seems overhwelmed by the task of issuing initial orders to get a scenario started take the approach that your first go at it constitutes "personal playtesting and putzing around with the game engine" to gain sufficient familiarity with things to acquire a comfort level with the "command burden". Wade in, play around, go back and rework until you have a comfort level......then worry about tackling a full scenario without restarts to gauge your competence.
