Matrix Games Forums

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

holy cow [X(] [&o]

Ralph didn't discuss this with us before he posted, so I don't know for sure, but I doubt that he wants you to send the scenarios to him, personally. We're still pondering the correct destination for that, and there will be a few other instructions, if you'll stay tuned.

Ralp, tell us more! Don't just disappear. When is the patch coming?

ORIGINAL: Karri

Ralp, tell us more! Don't just disappear. When is the patch coming?

I hope saturday than it's 65 years ago VE-Day

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

The Deadline for the TOAW 3.4 Call for scenarios has been set for June 6th. After that date, the call will close and no more entries will be considered.

The TOAW 3.4 Call for scenarios has now closed and no further submissions will be accepted for this update. Thanks to all who submitted scenarios.

Scenario Designers:

As you know, we closed the TOAW 3.4 call for scenarios back on June 6th. The scenario files had been mostly sent (as instructed) to Marc Martinez (Nemo). He was supposed to have then formatted and posted those submissions soon after they were received. Unfortunately, however, here’s what’s developed:

It has now been over three weeks since the call was closed and there’s been nothing from Marc. Furthermore, I can’t get any email response from him either. I don’t know what the issue is, but it’s time to take the next step. We’ve sat on our thumbs long enough and there’s no reason to continue to do so. The scenarios are the last thing left to do before the full build can be made.

So, I’m now asking submitters to resubmit their files – this time to me – that they had submitted to Marc before. My email is: crossrl (at) qzip.net.

Furthermore, since I don’t know just exactly who submitted to Marc, even those who didn’t submit earlier can still do so now, and I won’t be the wiser. (Don’t ask and don’t tell.) [;)] So, this is sort of like a second call. Same rules as before, though, and I won’t wait long (we’ve all waited long enough as it is).

Sorry for this inconvenience for those who had already submitted. And sorry for the delay for those that have been waiting. Marc may yet pop in with his results, and that will be a good thing. But everyone is waiting, and they shouldn’t have to any more than necessary.

Bob Cross

PS: A few of you did send your files to me the first time (Steve Sill, Mark Stevens and Ben Turner). No need for you to repeat - unless there were other submissions beyond those.

ORIGINAL: Curtis Lemay
Scenario Designers:

As you know, we closed the TOAW 3.4 call for scenarios back on June 6th. The scenario files had been mostly sent (as instructed) to Marc Martinez (Nemo). He was supposed to have then formatted and posted those submissions soon after they were received.

Bob Cross

This seem to be a FUBAR situation [:D]

Is there mayby all a DORU [:D] (Date of Release Update)

I wonder how many, if any, scenario designers will miss these calls for re-submissions buried in original call threads.

SNAFU

ORIGINAL: E

I wonder how many, if any, scenario designers will miss these calls for re-submissions buried in original call threads.

Bob sent an E-Mail to (hopefully) all.

ORIGINAL: Telumar

ORIGINAL: E

I wonder how many, if any, scenario designers will miss these calls for re-submissions buried in original call threads.

Bob sent an E-Mail to (hopefully) all.

I wouldn't think so, because of this statement...

ORIGINAL: Curtis Lemay

Furthermore, since I don’t know just exactly who submitted to Marc, even those who didn’t submit earlier can still do so now, and I won’t be the wiser.

I guess my point is, wouldn't it be better to start a new thread that might catch the eye of more of the original scenario submission authors?

ORIGINAL: E



I guess my point is, wouldn't it be better to start a new thread that might catch the eye of more of the original scenario submission authors?

Nothing is holding you back from linking this to a new. [;)]

Marc is a stand-up guy and I'm sure he has a good reason for his disapearance. But we don't know how long he may be gone and I'm not doing anything. So I figured I might as well go ahead and handle it.

Thus far, I've gotten the submissions from everyone that Marc told us had submitted except for two names I don't have email addresses for:

Miroslav Salomon and Mauro Medina.

I don't even know their psudonames. If anyone knows their email addresses please drop me a PM.

Of course, I don't know who may have submitted after Marc's last report. I can just hope that they see the anouncements.

stop torture us [;)]

ORIGINAL: pionier

stop torture us [;)]

[:D]

Bob,

So what your saying is that things are on 'hold' until this part of the action becomes clarified?

ORIGINAL: L`zard

Bob,

So what your saying is that things are on 'hold' until this part of the action becomes clarified?

No. Things are not on hold now. They would be if we were still waiting on Marc.