Guide for Design and Implementation of Scenarios, v1.0

compiled by Brooke (brooke@electraforge.com), 8/5/2006

Implementation Checklist

When implementing the scenario design in the special-events arena, as suggested by Easycor:

1. Check all the spawn points.
2. Check all the key object types.
3. Check all the key paths of travel (bridges/flak density.)
4. Check/review all the Arena settings.
5. Check/review all the Object settings.
6. Check the plane-set characteristics and ride numbers balance.
7. Check the fuel ranges and time aloft for each plane.
8. Check the COs (might want to develop a written application)
9. Check the write-up for clear Order of Battle.
10. Check the write-up for clear and balanced Objectives.
11. Check the write-up for clear and balanced Restrictions
12. Check the write-up for clear and complete arena and object Settings.
13. Prompt public announcement to player base when a setup or terrain issue is under review.
14. Keep player violations off the public boards when a penalty is under review but notify both COs.

New Designs

Do not run a new scenario unless (1) it has a side switch or (2) it is a modified version of a previously run scenario.  For example, if you have in mind a 4-frame non-switch scenario that is new, cut down its objectives and run it first as a 4-6 frame side-switch event.  That way, people have fun even if it is unbalanced, and it allows you to see what needs to be adjusted to get balance.  Then next time around you can run it as a non-switch event.

Do not have scenarios with no penalty for dying.  It creates a dynamic that is more like the main arena.  It should at least have something that provides an incentive to live.  Some examples of possibilities include, among others:

• Limited number of lives.
• One life in a primary ride, one life in secondary ride, and unlimited lives as gunners.
• Limited number of planes.
• Time delays after death.

Command Staff

Do not get cavalier or haphazard CO's.  They reduce the quality of the event by not organizing well, not working on orders, not taking the event all that seriously, not picking good GL's who will do the same, etc.  It is critical to get CO's who are "into it," dedicated, and communicative.  Pick someone who has been a good scenario GL or good scenario CO previously.  There are plenty of people who have been GL's in scenarios -- plenty to pick from.

Timeline

Starting from when the first design candidate is complete, the following allows 2 weeks to recruit CO’s, 2 weeks of rules wrangling, and 2 weeks for command staffs to come up with their plans prior to frame 1.

• Finish the candidate for final scenario design (T0).
• Post writeup of final-design candidate on ahevents.org.
• Post the “next scenario” PR on ahevents.org.
• Pick approximate date for frame 1 that is 6 weeks from completion of candidate for final design.
• Start recruiting CO’s.
• Finish recruiting CO’s (T0 + 2 weeks).
• Set official date of first frame as 4 weeks after both CO’s have accepted.
• Do not set official date of frame 1 prior to both CO’s committing.
• Open registration only after both CO’s commit.
• Start the process of rules adjustment (if any) with CO’s and designers.
• Check the implementation (see section above).
• Run a beta test.
• Scenario design finalized (T0 + 4 weeks).
• Post writeup of final design.
• Post the full PR including on ahevents.org.
• Run frame 1 (T0 + 6 weeks).

Change Log

v1.0

-- Initial version of this document.