 |
|
Scenario Introduction Template - 20091123 - 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 Introduction Template - 20091123 (/showthread.php?tid=53696) Pages:
1
2
|
Scenario Introduction Template - 20091123 - Jason Petho - 11-24-2009 Scenario Introduction Style Format For the John Tillers Campaign Series December 18, 2007 Updated: November 23, 2009 Created by Jason Petho 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 [OPTIONAL RULES][SPECIAL DESIGNER NOTES][GAME VERSION] 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: [OPTIONAL RULES] 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 Style: [SPECIAL DESIGNER NOTES] Desinated space for any special notes regarding your scenario. Style: [GAME VERSION] [1.05]------------------This scenario was created or updated to the 1.05 UPDATE standards. 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][NONE][1.05] UPDATED: 20091123 Jason Petho RE: Scenario Introduction Template - 20091123 - Jim von Krieg - 11-24-2009 next, you'll be telling us to FALL-IN... Oh, you are so bossy... LOL.. good idea... RE: Scenario Introduction Template - 20091123 - Jason Petho - 11-24-2009 *laughs* Thanks, boss. Jason Petho RE: Scenario Introduction Template - 20091123 - Herr Straße Laufer - 11-24-2009 Shall we wait for the 1.05 version update to follow this pattern? Or, should we make our scenario updates now? [GD]----------------------Guest Designer [BZ]-----------------------Blitzkrieg H2H Designer [BZ] only for H2H approved or for any that have been worked to PBEM balance?  .... Sir!  I printed out the two pages and put them next to my monitor. :smoke:  RR RE: Scenario Introduction Template - 20091123 - Jason Petho - 11-24-2009 Feel free to implement as soon as you wish! Jason Petho RE: Scenario Introduction Template - 20091123 - Herr Straße Laufer - 11-24-2009 Sir. Yes .... Sir!Though, can you let me know who is a BZ and who is a GD? :conf: RR RE: Scenario Introduction Template - 20091123 - Jason Petho - 11-24-2009 A GD, guest designer, is a member who has a scenario included in an official UPDATE or release that is not a member of the CS Legion or Beta Brigade. A BZ is a member of the blitz releasing scenarios through the H2H system. Jason Petho RE: Scenario Introduction Template - 20091123 - Herr Straße Laufer - 11-24-2009 O.K., what if you are neither or both at the same time? :rolleyes: I'm not trying to be difficult. I just don't understand if it applies to the scenario or to the designer of the scenario. :chin: RR RE: Scenario Introduction Template - 20091123 - Jason Petho - 11-24-2009 MrRoadrunner Wrote:O.K., what if you are neither or both at the same time? :rolleyes: It applies to the designer. If none apply to you, then "NA" should work. If you are both, then GD overrides the BZ designation. The GD designation means you've been asked to include scenarios for an UPDATE. Jason Petho RE: Scenario Introduction Template - 20091123 - Chuck10mtn - 11-24-2009 MrRoadrunner Wrote: Hey Ed, In military terms Sir is for officers and sargent is for working people. Jason seems to be working so maybe he'll do better as yes Sargent Chuck |
){kind=link}