Difference between revisions of "Building a Campaign"
| Line 3: | Line 3: | ||
{{Note}} Work in progress... | {{Note}} Work in progress... | ||
| − | ALiVE excels when it comes to building large scale dynamic campaigns. Instead of a single, short, highly scripted linear mission, an ALiVE campaign consists of multiple missions played over several sessions with progress automatically tracked and saved to the War Room. This short demo is based on a popular campaign created for www.volcbat.com that ran for over six months on Reshmaan province. It covers campaign planning, the technical build and also an example of the Op Orders and Reports written by the participants as the campaign progressed. | + | ALiVE excels when it comes to building large scale dynamic campaigns. Instead of a single, short, highly scripted linear mission, an ALiVE campaign consists of multiple missions played over several sessions with progress automatically tracked and saved to the War Room. This short demo is based on a popular campaign created for [http://www.volcbat.com VOLCBAT] that ran for over six months on Reshmaan province. It covers campaign planning, the technical build and also an example of the Op Orders and Reports written by the participants as the campaign progressed. |
The process, in short, is deceptively simple: think up a vaguely credible scenario, plonk some ALiVE modules and press go. It takes about an hour to do the whole thing from scratch and uses no scripting other than what ALiVE provides out of the box. | The process, in short, is deceptively simple: think up a vaguely credible scenario, plonk some ALiVE modules and press go. It takes about an hour to do the whole thing from scratch and uses no scripting other than what ALiVE provides out of the box. | ||
| Line 13: | Line 13: | ||
| − | + | # Pick a map. Check the list of [[Supported Maps]] to ensure it works with ALiVE. | |
| − | + | # Think up a high level scenario and overall missions for '''both''' OPFOR and BLUFOR. The missions don't need a lot of detail at this stage e.g."OPFOR are invading because reasons; BLUFOR are counter attacking because NATO." | |
| − | + | # Choose one of the [Supported Factions] for each side of the conflict. These all have groups properly defined by you can also manually [Declaring Faction Mappings|declare faction mappings] for unsupported addons if you wish. Ideally you want 2 or 3 different Inf groups, Motorised, Mech, Armour and Air. AA, Snipers and other specialists are best configed as SF groups so you can control their numbers easily. | |
| + | # Work out a starting Order of Battle (ORBAT) for each faction. For example, OPFOR has 3 battalions of light infantry supported by 3 attack helicopters, 1 artillery battery and a special forces group. BLUFOR are a company of mech inf with 4 support helicopters and 2 fast jets for close air support. Jot this down on a notepad for reference. The player group and any supporting assets should be subset of the BLUFOR ORBAT. This is lends a lot of flavour and credibility to the campaign without needing mountains of text and also massively helps with tracking campaign progress later. | ||
| − | |||
| − | + | =Preparation= | |
| − | + | # Create a mission in the editor. As a minimum you need to place one playable unit and a marker named ''respawn_west''. | |
| − | + | # Place down an [Military Placement (Military Objectives)] and [Military Placement (Civilian Objectives)] with debug on. Hit Preview and screenshot the results. This provides a useful reference of all the Objectives on the map. If there are any massive gaps in areas where players are likely to go, you can fill them in with one of the premade [Military Placement (Custom Objectives)] like road blocks, field camps, heli FARPs, or use the Random Objective Placement option. | |
4. Define TAOR zones on the map for each faction group. For Op TH, I placed 3 very large rectangles covering East, Centre and West of the map (coloured Orange, Red and Brown for easy reference) and a fourth Blue rectangle covering the start base for BLUFOR. | 4. Define TAOR zones on the map for each faction group. For Op TH, I placed 3 very large rectangles covering East, Centre and West of the map (coloured Orange, Red and Brown for easy reference) and a fourth Blue rectangle covering the start base for BLUFOR. | ||
Revision as of 10:23, 28 November 2014
-
Note: Work in progress...
ALiVE excels when it comes to building large scale dynamic campaigns. Instead of a single, short, highly scripted linear mission, an ALiVE campaign consists of multiple missions played over several sessions with progress automatically tracked and saved to the War Room. This short demo is based on a popular campaign created for VOLCBAT that ran for over six months on Reshmaan province. It covers campaign planning, the technical build and also an example of the Op Orders and Reports written by the participants as the campaign progressed.
The process, in short, is deceptively simple: think up a vaguely credible scenario, plonk some ALiVE modules and press go. It takes about an hour to do the whole thing from scratch and uses no scripting other than what ALiVE provides out of the box.
Campaign Planning
The first step is to define the context for your campaign.
- Pick a map. Check the list of Supported Maps to ensure it works with ALiVE.
- Think up a high level scenario and overall missions for both OPFOR and BLUFOR. The missions don't need a lot of detail at this stage e.g."OPFOR are invading because reasons; BLUFOR are counter attacking because NATO."
- Choose one of the [Supported Factions] for each side of the conflict. These all have groups properly defined by you can also manually [Declaring Faction Mappings|declare faction mappings] for unsupported addons if you wish. Ideally you want 2 or 3 different Inf groups, Motorised, Mech, Armour and Air. AA, Snipers and other specialists are best configed as SF groups so you can control their numbers easily.
- Work out a starting Order of Battle (ORBAT) for each faction. For example, OPFOR has 3 battalions of light infantry supported by 3 attack helicopters, 1 artillery battery and a special forces group. BLUFOR are a company of mech inf with 4 support helicopters and 2 fast jets for close air support. Jot this down on a notepad for reference. The player group and any supporting assets should be subset of the BLUFOR ORBAT. This is lends a lot of flavour and credibility to the campaign without needing mountains of text and also massively helps with tracking campaign progress later.
Preparation
- Create a mission in the editor. As a minimum you need to place one playable unit and a marker named respawn_west.
- Place down an [Military Placement (Military Objectives)] and [Military Placement (Civilian Objectives)] with debug on. Hit Preview and screenshot the results. This provides a useful reference of all the Objectives on the map. If there are any massive gaps in areas where players are likely to go, you can fill them in with one of the premade [Military Placement (Custom Objectives)] like road blocks, field camps, heli FARPs, or use the Random Objective Placement option.
4. Define TAOR zones on the map for each faction group. For Op TH, I placed 3 very large rectangles covering East, Centre and West of the map (coloured Orange, Red and Brown for easy reference) and a fourth Blue rectangle covering the start base for BLUFOR.
5. Plonk remaining Mil Placement, OPCOM and Logistics modules, selecting the size/type/mission/supply level and TAOR/Blacklists as per the planned ORBAT for each faction. Run another debug preview and screenshot it - this provides a snapshot of the campaign start state and is helpful for writing Op Orders and INTSUMs.
Mission & Tasks
1. Pick a Mission for A Coy to kick things off - Op TH follows a pretty standard mission cycle of Recce, Attack, Consolidate, Repeat. "Missions" are not the same as "game sessions". It could take several sessions to complete a single Mission.
2. Each Mission has a number of fairly generic patrol tasks for the platoon - listed as Available Taskings in the SITREP threads and/or (with latest ALiVE) as actual Tasks in the game.
3. Boundaries & LOE are very important for controlling the mission (and actually used the same way in real life).
4. Op Orders, SITREPs and INTSUMs pretty much write themselves. For a regular month long campaign you'd only need one and just update Taskings occasionally to move things along. Getting people to write patrol reports also helps (latest ALiVE now has persistent Reporting in game for this, sadly not yet exported to the website but it's coming).
Tweaks
1. As the campaign progressed I made a few tweaks. Mostly this involved reducing the Mil Placement group levels (cos persistence wasn't working properly) and increasing the BLUFOR TAOR to simulate A Coy expanding our zone of control. Updating missions in this way takes all of 5 mins tops.
2. Keeping a record of player gear if you don't want or don't fully trust Persistence to work is easily done on a spreadsheet or forum post (see the LOGSITREP posts). This can also be an good way of limiting some kit for a period of time.
If we did this as a regular campaign, I think it'd be fun to get a couple of people to play an Int Cell. It'd be their job to build up a picture of enemy dispositions and activity from patrol reports, and suggest appropriate Tasks to HQ.
