View Full Version : A New Rome?
The Purist
10 Jul 05, 16:50
The second of five scenarios in the 'Italy at War' series is ready to go. This time we travel back to September 1940 and the Italian invasion of Egypt. The Italians have dispatched a motorized column along with the 'Babini Armoured Group' in a flanking move hoping to cut the coastal highway east of Sollum. With some luck, bravery and skill they may trap the rearguard and open the way for an unoppossed advance into Egypt.
A light screening force from the intrepid 7th Armoured Division is tasked with delaying the Italian advance. The place chosen was at one of the few points where the escarpment could be climbed via a steep track. The British challenge will be in holding the junction as long as possible and then pulling out and falling back with minimal casualties.
Why are neither of the scenarios in the archives? :p
To anyone else who has designed CM scenarios- post them as well please. :D
The Purist
01 Aug 05, 22:15
Why are neither of the scenarios in the archives?
Quite simple, really, I have yet to write up the text. Designing the scenario was easy when compared to composing the appropriate narrative. Hopefully by this weekend I will be able to figure out how to create a text file and do the write-up.
Designing the scenario was easy when compared to composing the appropriate narrative.
Tell me about it! :eek:
Although they are daunting & a pain at times they are fun to research. :D
British Tommy
02 Aug 05, 19:31
Quite simple, really, I have yet to write up the text. Designing the scenario was easy when compared to composing the appropriate narrative. Hopefully by this weekend I will be able to figure out how to create a text file and do the write-up.
Gerry,
Use notpad to create your briefings. I always label them as:
'scenario name-both'
'scenario name-axis'
'scenario name-allied'
So easy to get them mixed up when you come to installing them :hmmm:
One thing which I find frustrating is getting the layout right. In notepad form it looks good but after installing the briefings and starting the scenario, you will always find a sentence that's out of line or a big space between two words! :mad:
Getting it so it looks neat and tidy can take many attempts at times! :o
Good luck mate and if you want the bumps and lumps play tested out of it, you know which site to post it first before sending it to SZO :D
It's even easier than that! ;) and you can use WORD.
All you have to do to get it right almost every time the first time is "save as" your briefing & select "plain text" (from the drop down list at the bottom) thats how CM "see"s the briefings in the first place.
When you save it the Word Program may tell you that some of your briefing is not formated correctly or that you may lose some of it, but you won't. CM likes it that way. :laugh:
It's the EASIEST way to handle this strange system.
I save mine like this: Valor in Prussia = VIPGEN.txt / VIPAX.txt / VIPAL.txt, this keeps all the briefings together & with short file names.
(GEN= General briefings)
British Tommy
03 Aug 05, 19:39
It's even easier than that! ;) and you can use WORD.
All you have to do to get it right almost every time the first time is "save as" your briefing & select "plain text" (from the drop down list at the bottom) thats how CM "see"s the briefings in the first place.
When you save it the Word Program may tell you that some of your briefing is not formated correctly or that you may lose some of it, but you won't. CM likes it that way. :laugh:
It's the EASIEST way to handle this strange system.
I save mine like this: Valor in Prussia = VIPGEN.txt / VIPAX.txt / VIPAL.txt, this keeps all the briefings together & with short file names.
(GEN= General briefings)
And all this time I have been struggling with Notepad! :rolleyes:
You could of told me that when CMBO first came out! ;)
Well, let me know how easy you find it.
About the only problems I've had is maybe a "tab" sentence or one I didn't want in. But once I saw it it was easy to correct.
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.