ColHut Posted November 2, 2013 Report Posted November 2, 2013 Dear Lo, I cannot remember if this is needed and what it does in the timetable commands list Can you remind me please? regards Wol Quote
sniperton Posted November 4, 2013 Report Posted November 4, 2013 Lo, if you don't mind, I copy here what I have from the old forum (JastaV's excellent summary from 2007): HERE A LIST OF TIMETABLE COMMANDS UPDATED TO DCG ver. 3.32 1- NewColumn: ADD NEW COLUMN: armors, supply columns, ships,..... Syntax: DATE NewColumn #_Chief CLASS.#UNIT @LOCALES $"editable unit name" ~FLAG examples: 19410808 NewColumn 38_Chief Armor.4-T26_Early 1 @German_Depot $Armor_Group_2 ~L 19440720 NewColumn 39_Chief Ships.Tramp 1 @NW_Guam_Isle_Sea $USS_LSD_219_Hudson ~L 19440719 NewColumn 68_Chief Armor.3-M5A1Stuart 1 @Blank $132nd_USMC_Rgt ~X notes: DATE is encoded as YY/MM/DD Use any #_Chief -chief number- not already used into campaign Master file. A chief number cannot be used twice into a campaign. CLASS is any class of Il2 Moving units. #UNIT identify number of units and their type according to Il2 database. @LOCALES is the spawning locations: can be a Ground or Sea Locations per Ground units and Sea units respectively. @LOCALES = @Blank identify a unit not spawned over map at DATE: it's added to the units pools for later spawning. $"editable unit name" here user can edit a choice name for the units. ~FLAG are codes used to identify units movement state: ~L indicates a unit deployed at a location, ~X is an un-deployed units available in the campaign units pools for later spawning: think of it as a reinforcement unit. Mostly symbols here used are common to columns.dcg file !!!!!! 2- NameColumn: EDIT COLUMN NAME: armors, supply columns, ships,..... Syntax: DATE NameColumn #_Chief "editable unit name" examples: 19410801 NameColumn 0_Chief Armor_Group_1 19410801 NameColumn 1_Chief Panzer_Gruppe_1 19430617 NameColumn 15_Chief CV_USN_Hornet 19431122 NameColumn 24_Chief 5th_Indian_Brigade notes: #_Chief is relative to a column already edited, (matching chief number) into a campaign Master file 3- RemoveColumn: COLUMN REMOVED FROM CAMPAIGN: armors, supply columns, ships,..... Syntax: DATE RemoveColumn #_Chief examples: 19420510 RemoveColumn 20_Chief 19420510 RemoveColumn 21_Chief 19420511 RemoveColumn 22_Chief notes: Columns added by Campaign template, (Master file) and/or added by Timetable commands can be removed at will. When removing a CV it's useful to remove or redeploy any CV linked squadron. 4- MoveSquad: MOVE A DEPLOYED SQUADRON AT ANY AIRFIELD/CV Syntax: DATE MoveSquad Squadron_ID "Destination base" examples: 19420603 MoveSquad IJN_AG_341z1 AV_MS_Shonan_Maru_Seaplane_Base 19420506 MoveSquad IJN_C_Shoho_FS0 IJN_CVE_Shoho 19420806 MoveSquad IJN_AG_341z1 Rabaul_Airfield notes: Squadron_ID have to beeing used according to Il2 encoding squadron system: You can sea at squadind.dcg file for a list on encoded squadrons. "Destination base" it's the airfield, airstrip, Seaplane-base -Seaplane only-, CV where the squadron is commanded to deploy to. For airfield, airstrip, Seaplane-base*** use matching location name as per RDS, SRD*** file. For CV use CV name.....see NameColumn timetable command and NewColumn command -"editable unit name"- described before. 5- RemoveSquad: REMOVE SQUADRON FROM CAMPAIGN Syntax: DATE RemoveSquad Squadron_ID examples: 19420510 RemoveSquad IJN_C_Shoho_FS0 19420510 RemoveSquad IJN_C_Shoho_FS_VT0 Notes: KEEP CARE.....DO NOT REMOVE PLAYER SQUADRON 6- RoadBlockOn: COLUMNS CANNOT MOVE ALONG ANY ENCODED ROUTE SEGMENT: it's true for Ground units and ships, too. Syntax: DATE RoadBlockOn "location name" examples: 19440613 RoadBlockOn Central_Pacific_Ocean_2 19440613 RoadBlockOn Marianas_Inner_Sea notes: Any "ROUTE SEGMENT" has a start and destination location name as encoded into RDS, SRD file. Example: [Central_Pacific_Ocean_2 to Marianas_Inner_Sea] RoadBlockOn commands for both start, both destination location along a route segment have to beeing edited. Virtually it's possible to edit start/destination locations RoadBlockOn commands at once. Example: 19440613 RoadBlockOn Central_Pacific_Ocean_2 to Marianas_Inner_Sea Indeed, I never verified that with my tests. Any kind of units movement along a specific route-segment will be inhibited as soon as a RoadBlockOn command is active for that route-segment: it includes normal columns movement, as retreat and pursuit, when allowed. Columns prohibited to advance sit down and deploy at a RoadBlockOn location. I never tried RoadBlockOn command in relation to RailRoad movement: I suppose it should work too 7- RoadBlockOff: RESTORE COLUMNS MOVEMENT ALONG A ROUTE SEGMENT: it's true for Ground units and ships, too. Syntax: DATE RoadBlockOff "location name" examples: 19440722 RoadBlockOff Agana_Port 19440722 RoadBlockOff Marianas_Inner_Sea Where Agana_Port and Marianas_Inner_Sea are contiguous location connected by a Sea-Route segment. notes: see RoadBlockOn command before for most common issues. RoadBlockOff command restore any kind of movement along a ROUTE SEGMENT previously interdicted to units movement from a RoadBlockOn command. EDITING TIPS: RoadBlockOn/RoadBlockOff can be used to influence columns movement during a campaign. Routes inactive at campaign start can be activated later..... Time trigged advances, flanking manouvers, selective landings at amphibious invasion points, train supply/reinforcement delivery*** and cargo-ships columns unloading can be simulated by a smart usage of RoadBlockOn/RoadBlockOff commands. 8- NewPayload: CHANGE PAYLOAD FOR A PLANE TYPE: payload can be separately changed for any plane type, according to mission profile. Syntax: DATE NewPayload "Plane type" "Payload type" = "Selected Payload" examples: 19420502 NewPayload G4M1_11 ASWeapon = none 19410810 NewPayload JU_88A4 GAWeapon = 2xSC1000 19410810 NewPayload JU_88A4 LBWeapon = 10xSC50 19410810 NewPayload JU_88A4 ASWeapon = 2xSC1000 19410810 NewPayload FW_190A8 AAWeapon = r14mg15120 19410810 NewPayload FW_190A6 Droptank = r11tank LBWeapon: level bomber strategic run. ASWeapon: anti-ship. GAWeapon: anti-ground CAS missions. AAWeapon: fighter anti-bomber. Droptank: fighter long range. notes: "Plane type" according to Il2/DCG ID for any specific plane type/model "Payload type": ASWeapon for Anti-ship, LBWeapon for Level-Bombing, GAWeapon for Ground-Attack, Droptank for external droptanks, AAWeapon fighters anti-bomber "Selected Payload": the payload to be used. See allpayloads.dcg file for the payloads enlisted per plane type/model. Payloads can be edited multiple times at will during a campaign. EDITING TIPS: Payloads selection influences plane types employement profile. Example: 19420502 NewPayload G4M1_11 ASWeapon = none 19420502 NewPayload G4M1_11 LBWeapon = none 19420502 NewPayload G4M1_11 AGWeapon = none G4M1_11 will be not committed to Anti-ship, Level bomber mission, or Ground Attack missions .....As a consequence, Betty squadrons will be assigned to recon missions. Example: 19420603 NewPayload B5N2 ASWeapon = none 19420603 NewPayload D3A1 ASWeapon = none 19420606 NewPayload B5N2 ASWeapon = 1x91 19420606 NewPayload D3A1 ASWeapon = 1x2502x60 The example is from Midway Campaign: at Campaign start, (19420603-19420605), B5N2 & D3A1 squadrons will not be assigned to Anti-Ship missions....So IJN squadrons will ignore Allied CVs and will engage Ground Installation at Midway. Later, 19420606, As Anti-Ship payloads will be available for B5N2 & D3A1, and they could be assigned to Anti-ship missions against the Allied CVs Task Forces. With this TIP I could recreate into a DCG campaign the strategic element - the late sighting of USN CVS by IJN Recon planes - for the Allied victory at Midway. 9- NewPlane: CHANGE PLANE TYPE EQUIPPING A SQUADRON Syntax: DATE NewPlane Squadron_ID "Plane type" examples: 19410807 NewPlane II_JG770 BF_109F4 notes: see before for explanations. Plane upgrade/downgrade is not influenced or influence NewPlane Command. NewPlane Command allows a squadrons to be equipped with a plane type of choice. I NEVER TRIED or TESTED NewPlane COMMAND yet. 10- NameSquad: CHANGE SQUADRON NAME/DESIGNATION Syntax: DATE NameSquad "Squadron ID" "Squadron new ID" examples: 19410807 NameSquad g010 II_JG770 notes: The command changes the squadron ID. Squadrons ID are to be used according to Il2 Squadron ID routine. see Squadid.dcg file for a list of most Il2 Squadrons. 11- TCapture: SWITCH LOCATION CONTROLLING SIDE Syntax: DATE TCapture "location status" "Location name" examples: 19410802 TCapture Contested Border_Village 19410804 TCapture Allied Border_Village notes: "location status": Allied, Axis, Contested are the allowed codes. "Location name": it's the location name according to RDS file. It's also possible to enforce a change into location control by NewColumn TimeTable command....In fact adding new columns to an enemy controlled location, new columns could conquer the location. 12- SetSupply: CHANGE SUPPLY LEVEL FOR A SIDE Syntax: DATE SetSupply SIDE "Supply Level" examples: 19410801 SetSupply Allied Default 19410801 SetSupply Axis 110 notes: I did not tried SetSupply command in my 3rd party campaigns !!!!! 13- SetOilSupply: CHANGE OIL SUPPLY LEVEL FOR A SIDE Syntax: DATE SetOilSupply SIDE "OilSupply Level" examples: 19410801 SetOilSupply Allied 60 19410801 SetOilSupply Axis Default notes: I did not tried SetOilSupply command in my 3rd party campaigns !!!!! 14- ShowMovie: a movie/trak is played before matching date mission generation. Syntax: DATE ShowMovie (Movie)Name.ntrk examples: 19430902 ShowMovie opening-movie.ntrk notes: The movie -NTRK file- is to be placed into Il2/Intros folder. Check active show intro at Il2 configuration setting menu to play traks. 15- AddSquad: Add a new squadron to a campaign Squadrons OOB. Syntax: DATE AddSquad "Squad ID" example: 19420506 AddSquad IJN_C_Shoho_FS0 notes: "Squad ID" identify the new squadron we are going to add. IMPORTANT: when adding a squadron by AddSquad Command indicate also the plane type to be used by NewPlane Command. example: 19420506 AddSquad IJN_C_Shoho_FS0 19420506 NewPlane IJN_C_Shoho_FS0 A6M2_21 When the new Squadron is to be assigned to a CV a MoveSquad Command is to be used. Example: 19420506 AddSquad IJN_C_Shoho_FS0 19420506 NewPlane IJN_C_Shoho_FS0 A6M2_21 19420506 MoveSquad IJN_C_Shoho_FS0 IJN_CVE_Shoho In last example "First Shoho Fighter Squadron", equipped with A6M2-21 is added, based over IJN CV Shoho at 19420506. New squadron will be composed of 16 planes; pilots experience will be default one according to Year and Service; Squadron will use Il2 default skin or any skin encoded into allpaints.dcg file for that plane type. 16- SetTimePassage: set time passage setting for a campaign. Syntax: DATE SetTimePassage “Time Passage” Example: 19420695 SetTimePassage Slow “Time Passage” can be set according to setting value available in DCG main page setting for the Time Passage field: Normal, Slow, Fast, ...... Note: I tried Slow and Normal in my test over DCG betas and in “work in progress TPC”. Time Passage can be changes more time at will during a campaign. 17- TimeTable Off: trigger full movement/advance option for Columns when Timetable is used for a campaign. Syntax: DATE TimeTable Off Note: at first timetable.dcg file was created to inhibit Columns movement in a campaign. Adding “TimeTable Off” command restore full movement for Columns: advance, retreat, pursuit,.... All other TimeTable commands are till effective when a “TimeTable Off” is enabled. All TimeTable commands are time trigged and related to a specific unit, location , squadron,.... TimeTable commands can be used more times, in turn, during a campaign in relationship to the same unit, location , squadron. 18- BanPayload: Ban enlisted Payloads form on line game session. Syntax: DATE BanPayload “Plane Type” = Payload#1; Payload#2, ..... Note: Mainly used to ban some payloads type from on line sessions. 19- NewsBrief: ADDS BRIEFING NEWS/MESSAGES. Syntax: DATE NewsBrief "LANGUAGE" = "BRIEFING NEWS/MESSAGE TEXT" examples: 19410801 NewsBrief English = Welcome to the Test Campaign. notes: "LANGUAGE" any language supported by Il2DCG. JastaV Quote
ColHut Posted November 4, 2013 Author Report Posted November 4, 2013 Dear Sniperton, Outstanding. I wish I could access those old posts! I think I may have kept some but not many. You tend to act as thought the material on the web will always be there for later :-( I once got part way through updating Tailspin's guide and foolishly gave it up. Now DCG is so great (in all respects) even Lo can't remember what is in it! regards Wol Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.