|
ralphtricky -> Toaw 3.4 Call for Scenarios (5/5/2010 12:58:39 AM)
|
Toaw 3.4 Call for Scenarios.
Please send me an email if you are interested in updating one of your scenarios in TOAW III or have a new scenario you'd like included.
RalphTrickey (at) OperationalWarfare.com
Thanks,
Ralph
Rules for scenario submission are as follows:
1. Updates of scenarios already in the suite are welcome. We expect veterans of the process to know what to do. Please try to maintain the formatting we used with the previous version.
2. New scenarios are no longer vetted by the team. But we do ask that designers vet their own work, and only submit quality designs. Regardless, the scenario must be “Valid” as per the “Properties” test. We will not fix a scenario that fails that test nor consider it for inclusion. If the scenario uses an equipment mod, the correct mod must be included.
3. If your submission is a modification of an existing designer’s scenario, and that designer can still be contacted, you should have his consent to submit. If the designer has dropped off the edge of the Earth then we’ll require no such consent.
4. There is no specific deadline for submission. But they must be ready to include well before the time the final build is started – and that may begin at any time. So submit ASAP. Dates are uncertain, but the build could be as early as May 30th.
5. Be sure to include any scenario specific graphics, equipment mod file, documents, scenario bmp, etc., preferably in their correct folders. Zip the entire package, if possible.
6. Send the scenarios to Nemo (at “toaw (at) free.fr”) for final formatting and inclusion in the 3.4 build. We recommend that you also submit a note (not the file itself) to Ralph (at “ralphtrickey (at) operationalwarfare.com”) that you did so, as a double check to make sure it isn’t missed.
7. Note that if you had previously sent scenario files to JAMIAM at any point since the last update, those files are probably not going to be found now – so send them again to Nemo to be safe.
8. We would appreciate if submissions would arrive already compliant with our format requirements. Otherwise, we will have to correct them for you. Those format requirements are to present a professional look to the suite and are as follows:
9. File name should be “Title Date.sce” – in that order. Title should use whole words. Dates should be four digits if possible. For example: “Saddams Final Gamble 2003.SCE”. Avoid strange mnemonics and abbreviations if possible. Use spaces, not underlines, for word separators. Especially leave off version numbers. It should be short enough to fit in the scenario list display width.
10. If possible, include a scenario bmp (see the "how to" document in the manual folder). Otherwise, one will have to be devised by the team.
11. The scenario briefing should begin with a header section that includes the following in order: Title, Version number, Designer’s name and email address, TOAW-3 version required, whether the scenario is PO programmed for either side and/or can be PBEM, date/location/hex-scale/turn-scale/unit-scale/length, and unit colors. Note that the briefing need not be in English (we welcome foreign-language designs). But, whatever language, please check spelling and grammar (best done with a word processor). An example briefing header is shown here (feel free to use it as a template):
"NAPOLEON'S LAST BATTLES"
The Waterloo Campaign
Version 4
Designer: Bob Cross
Email: (email address)
TOAW-3 ver. 3.4
:: PBEM ::
:: Allies PO, French PO ::
Date: June 16-18, 1815
Location: Belgium
Map scale: 2.5km per hex
Time scale: 6 hour turns
Unit scale: Division
Length: 10 turns
UNIT COLORS
French - White on Blue
Guard - Black on Dk. Blue
British - White on Red
Dutch-Belgian - Blue on Green
Brunswick - Blue on Black
Prussian - Gray on Dk. Gray
|
|
|
|
