Scenario Acronyms - Printable Version +- Forums (https://www.theblitz.club/message_boards) +-- Forum: The Firing Line (https://www.theblitz.club/message_boards/forumdisplay.php?fid=1) +--- Forum: Campaign Series (https://www.theblitz.club/message_boards/forumdisplay.php?fid=8) +--- Thread: Scenario Acronyms (/showthread.php?tid=55283)

Scenario Acronyms - Scud - 04-05-2010 This was posted in the H2H section recently, to clear up some recent confusion, but I thought I'd add it here as well, in case any of you ever wondered what all those acronyms stand for when reading a scenario description: This document serves as a general guideline for filling out the Scenario Information when creating a new scenario for John Tillers Campaign Series. Hopefully this will provide some consistency in the future introductions. (Scenario Name) All MCS scenarios should be prefixed with ** For example; ''** The Last Straw'' (Designer) Full Name (DATE) 14 December, 1944 (INTRODUCTION) [LOCATION]: [PLAY MODE][SCEN TYPE][DESIGNER]: SCENARIO DESCRIPTION [SPECIAL DESIGNER NOTES] Style: [LOCATION] Akimovka, 20km SW of Melitopol OR Odessa, Ukraine OR Paris, France OR Metz, NW France Style: [PLAY MODE] [H2H]-----------------------Defined as Best Played versus Human Opponent [AXIS] --------------------Defined as Best Played as AXIS [ALLIED] ------------------Definied as Best Played as ALLIED [H2H/AXIS] ---------------Definied as Best Played vs Human Opponent OR as AXIS [H2H/ALLIED] -------------Definied as Best Played vs Human Opponent OR as ALLIED Style: [SCN TYPE] [HIS] ----------------------Historical - Extra effort in map/oob and scenario as close to history as possible [HISB]---------------------Historically Based - Scenario based on a particular battle; map and oob can be fictional. [FIC]-----------------------Fictional [WIF]-----------------------What If situation. Style: [DESIGNER] [CSL]---------------------Campaign Series Legion Designer [BB]-----------------------Beta Brigade Member Designer [GD]----------------------Guest Designer [BZ]-----------------------Blitzkrieg H2H Designer [TS]-----------------------Talonsoft Original Style: [DESIGNER] SCENARIO DESCRIPTION Provide a detailed introduction the scenario situation. It is here where you have to "sell" your scenario. Style: [SPECIAL DESIGNER NOTES] [NONE]------------------No special notes [ ]-----------------------Add any note about special rules or thoughts on the making of your scenario. CODES FOR OPTIONAL RULES within the SPECIAL DESIGNER NOTES [ALL]------------------All Options On [IFM]------------------Indirect Fire by the Map [EFOW]---------------Extreme Fog of War [EA]------------------Extreme Assault [AF]------------------Armour Facing EFfects [CC]-----------------Command Control [VV]------------------Variable Visibility [N IFM]---------------NO Indirect Fire by the Map [N EFOW]---------------NO Extreme Fog of War [N EA]------------------NO Extreme Assault [N AF]------------------NO Armour Facing EFfects [N CC]-----------------NO Command Control [N VV]------------------NO Variable Visibility Example usage: [EFOW:CC:VV]----------USE Extreme FOW, Command Control and Variable Visibility [ALL: N EFOW:N VV]----ALL OPTIONS but NO Extreme Fog of War and NO Variable Visibility [ALL: N EA]--------------ALL OPTIONS but NO Extreme Assault Example of a formatted Scenario Introduction: ** The Battle for Karpova Station Jason Petho 18 August, 1941 [Karpova Station, 30km NW of Odessa, Ukraine]: [H2H][HIS][CSL]: At dawn on the morning of August 18th, the Rumanian 3. Army Corps launched an attack to seize the Karpova Railway Station. The 3. Dorobanti Regiment of the 11. Infantry Division was to advance towards the Russian positions without preliminary artillery bombardment. The Russians were holding the line with the determined 97th Infantry Regiment, 95th Infantry Division whom were standing firm in their trenches and bunkers. An hour after the attack began, the Rumanians supported the stalled attack with a battalion of armour from the 1. Armour Division and an assault battalion. By 07:30 the station had was captured, but at a high cost to the Rumanians. Thirty-two tanks lay damaged or destroyed on the battlefield. [ALL] RE: Scenario Acronyms - Kool Kat - 04-09-2010 Hi Dave: This is good information! Maybe make it into a sticky? :chin: When I do design scenarios... I'm always looking for the latest version of this document. RE: Scenario Acronyms - Herr Straße Laufer - 04-10-2010 It is posted as a sticky in the H2H forum. ;) HSL RE: Scenario Acronyms - Scud - 04-10-2010 Hi Mike, I think this is the latest, but maybe Jason can verify when he has a moment. Ed's right, though, it's a sticky in the H2H section where it should be. I just thought it might give the non-scenario designers a little insight on what you guys follow when writing your descriptions. Thanks, Dave