mirror of
https://github.com/dcs-liberation/dcs_liberation.git
synced 2025-11-10 14:22:26 +00:00
Updated Custom campaigns (markdown)
parent
84237b96e6
commit
08cd1389d7
@ -85,7 +85,7 @@ To specify that an airbase should be owned by the player when the campaign is in
|
||||
|
||||
### Front lines
|
||||
|
||||
Front lines are defined by placing a CJTF Blue M-113 at an airfield and defining a route to the connected control point. The front line will follow the _waypoints_ of the vehicle group (not the path, so using on-road waypoints will not cause the front line to follow roads automatically), so waypoints should be placed at each location that the front line should turn to avoid terrain. The route should end near the airfield that the front line connects to. The route beginning and end points will be used as the origin and destination endpoints for convoys, so each end point of the route should be placed on a road. The beginning and ending waypoints will associate with the nearest airfields when the campaign is generated.
|
||||
Front lines are defined by placing a CJTF Blue M-113 at an airfield and defining a route to the connected control point. The front line will follow the _waypoints_ of the vehicle group (not the path, so using on-road waypoints will not cause the front line to follow roads automatically), so waypoints should be placed at each location that the front line should turn to avoid terrain. The route should end near the airfield that the front line connects to. The beginning and ending waypoints will automatically snap to the nearest airfields when the campaign is generated.
|
||||
|
||||
**Important:** Care should be taken to route the frontline around exclusion zones. If the center of the frontline location lies in an exclusion zones, frontline units may not spawn correctly. You can view the exclusion zones in the Liberation UI by enabling the display option "Map Debug Mode"
|
||||
|
||||
@ -103,7 +103,7 @@ Then the generator will create between 2 and 5 (evenly weighted) additional defe
|
||||
|
||||
This means that if the campaign designer wishes to avoid randomly positioned base defenses, they must define at least:
|
||||
|
||||
* 1 EWR location
|
||||
* 7 EWR location
|
||||
* 7 air defense locations (SAMs and SHORADs differ by unit type but share placement locations)
|
||||
* 6 garrison locations
|
||||
|
||||
@ -117,6 +117,8 @@ To define a potential EWR location, place a CJTF Blue EWR 55G6.
|
||||
|
||||
One EWR will always be placed at each control point.
|
||||
|
||||
To define a required EWR location, place a CTJF Red EWR 1L13. Required EWRs will always be generated.
|
||||
|
||||
#### Air defenses
|
||||
|
||||
To define a potential air defense location, place a CJTF Blue S-300PS SR 64H6E within a 2 NM radius of the control point. Units placed outside that radius will be regular objective locations rather than base defenses.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user