Scenario Design

[TheBigRedOne]

I do have an interest in designing some scenarios. But strangely, having played SqB pretty heavily for 18 months now, I still feel I need more experience in the game to do so effectively.
2. I know I would like this one - a tutorial in scenario design. One designer begins a thread or email tree showing his approach and design steps. For example: "I am Romeo Poppa and I am going to build a scenario in Red Victory based upon a real/hypothetical engagement at _____ on 12 Sep, 1943. First thing I do is: xxxx" and so on allowing budding designers to get their feet wet under the tutelage of an experienced hand.

Mike Cox put this out with Dien Bien Phu. Take a look....

http://tfe4.files.wordpress.com/2009/07/...ch-dbp.pdf

---

Also, this was something I compiled a while ago and posted here:

====

A while ago I compiled some thoughts from three of HPS's main SB scenario designers. An edited version of this was released on JZtemple's Fan Site, but with the release of Dien Bien Phu, I can post the full version.

I posed the question regarding how these guys go about the design process. Obviously it could fill several volumes of text, but I just wanted to get a glimpse of how these guys go about their work.

For those of you purchasing DBP, you'll find a PDF file in the folder that describes how to design a scenario from scratch, written by Mike Cox, the designer for DBP. I have included this file as an attachment for those of you who might not fancy a fight in the muddy fields on Dien Bien Phu, but would still be interested in a step-by-step account of how to go about making a rudimentary scenario. Thanks to Mike and Rich Hamilton for allowing me to post this document.

Enjoy.

A
---
Mike Cox (SAW, DBP, variety of after-release scenarios)

I get inspiration from reading detailed accounts of the battles as well as other games. Whenever I read I have Post It's handy to flag passages with scenario material. Sometimes seeing a scenario for another game leads to further research on a particular fight. The main thing is that the fight has to be a contest and not a walkover. Is the turning point of the battle able to be modeled in SB?

The first question I ask - is there a suitable map available to use for a submap? (Or do I have to get one done?)

I tend to like shorter scenarios - 1 hour or so. Though if the action is 2 hours, then 2 hours it is. I tend to discount mopping up, but try to gather at what point the action turned.

I love gadgets. Mention of an obscure tank makes me want to work it in. (And I am still trying to get a Japanese tank or old FT-17 into a DBP scenario.)

For OOB's I try to build up standard ones then copy/paste them in. Once in the oob, I tweak them to meet the description. (DBP as an example - the oob's I inherited pretty much had AAT-52 for the French MG as standard issue. My reading has the them often using older equipment, so change those to Brownings or Vickers. For example.)

The other thing I like is a bit of randomness - say with reinforcements. Historically, the tanks saved the day by coming at 1345h. What if they were 10 minutes late? Early? Though I have not used it much I think the alt arrival hexes are a big boon.

Joao Lima (SCW, AoTR post-release)

- The process is quite straightforward, I usually do: idea-research-map-oob-build-test

- Ideas may come from the most amazing sources. In SCW ideas came from interviews, tv documentaries (amazingly on a British channel), books, websites... The tricky thing is not finding what sounds like an excellent idea, the trick is in actually move from the idea to completing enough research to provide an accurate and realistic scenario. The other issue is that sometimes things just do not fit. I had a couple ideas for SCW that would work brilliantly in ASL (because of the multi-hex, multi-level buildings) but when done in SB just did not work. Sometimes a great idea also needs to be slightly stretched when you realize that the research showed things not be quite as you thought, and then, presto, an hypothetical scenario is born...

- OOB's are a very mixed bag. For WW2, for example, you have a wealth of information easily available, however sometimes that information is just too high level yo allow you to transport it to SB. However , don't let the OOB constrict you too much, this where balance sometimes get's in, and even if historical , an OOB might be slightly tweaked to allow a proper balance. Where to find them is too big an answer, but usually specialized internet forums are a place to start. BUT, BIG LESSON, ALWAYS CROSS YOUR INFORMATION WITH ANOTHER RELIABLE SOURCE!!!

- Time for a scenario is highly variable, but I can put together the skeleton in a couple of days, preliminary tuning takes another couple of days, and then, to fine tune, who knows? ;-)

- I started to plan new scenarios focused on too big scenarios, with far too many units , and gigantic maps. It took me a while to understand that what's need is a map roughly the size of my screen , and units that are the size of a reinforced company. For variety a couple of tiny and a couple of big ones.
But the basic principle is a balance between historical and fun. It's a game after all, if you fail to captivate the interest of the players, then it does not matter how historical your scenarios are, nobody will play them.

Ozgur Budak (RV, SAW, WW, A@W, many post-release scenarios)

One thing I find useful is writing down the outline of the planned scenario. A small text containing date, hour, weather, OOBs (co/btn/div/corps) for both sides, info on the topography (if possible copying the map), a summary of the action including reinforcements and key events. I frequently come back to this outline text during the design process. The text provides the framework of the scenario with all needed and accesible data so I dont get lost. Best time for writing down such a text is after reading the various sources and deciding what to focus. Sometimes I am creating several of those texts so I dont get confused about the planned scenarios that awaits. Planning and classifying is especially important when you have to design dozens of scenarios.