Originally posted by SELECTOR
problem with scenarios is
1 they almost always run late.
2 after an hour they turn into a MA situation.
3 there is unrelenting questions about the rules from begining to end.
4 the results( i think) are bent to fit into the scenario box..(we want a historical result . so we make it historical regardless)
To answer your gripes in order:
1) You mean start late? Yeah ... that's always a problem and can't be helped much. But after doing this so often I'm pretty good at making last minute adjustments to compensate and get people off pretty close to on-time.
2) My events don't turn into the MA. No attacks on AAA or radar are allowed. No running off-map is allowed. Strict altitude and formation restrictions are in place. My events focus on planning and executing a proper strike mission and interception of one. When players get it right, they never forget the experience.
3) Rules. Yeah. Well if you read the Rangoon write-up obviously I've been through this before (I invented the genre). I back up the rules with discussion of their intent and stay involved with the command topics in the forum to make sure everyone understands what they should do and what they should expect.
4) I don't design events to recreate a historical result. I pick battles which are interesting and preferably asymmetrical in at least one dimension. I start with a point in history and then build around it instead of matching it. Rangoon is such an example - in real life the Allies were hopelessly outnumbered. But that's no fun, so I took a left turn at history and said: "OK, lets assume after the first couple attempts the IJA decided to wipe out all Allied air assets in the assault and brought up reinforcements, and that the Allies decided to make a stand with everything they could spare in the CBI theatre."
As I've said before, I don't know how other people do things or what's gone on before. I just know how I run the show. My events are very difficult and demand good planning and flawless execution to achieve victory.
