mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
Updated Custom campaigns (markdown)
@@ -69,6 +69,89 @@ When choosing preferred aircraft, although the property is optional, it is best
|
||||
|
||||
A best practice to follow is to set up one base per side as a transit hub. This is preferably a large airfield near the rear of the conflict (not easily captured or destroyed), that has the ability to produce ground units (has a factory), has a cargo aircraft squadron, and optionally has a port. Depending on the location of this base it may also be a good home for AEW&C and refueling squadrons (and a BARCAP squadron to defend those other squadrons).
|
||||
|
||||
### Common issues with a custom campaign yaml file and their solutions
|
||||
|
||||
#### 'air-to-ground' is not a valid FlightType
|
||||
|
||||

|
||||
|
||||
The following tasks can only be set as secondary tasks, not primary ones:
|
||||
* air-to-air
|
||||
* air-to-ground
|
||||
|
||||
Incorrect:
|
||||
```
|
||||
- primary: air-to-ground
|
||||
secondary: any
|
||||
aircraft:
|
||||
- VFA-113
|
||||
```
|
||||
|
||||
Correct:
|
||||
```
|
||||
- primary: SEAD
|
||||
secondary: air-to-ground
|
||||
aircraft:
|
||||
- VFA-113
|
||||
```
|
||||
|
||||
#### 'primary'
|
||||
|
||||

|
||||
|
||||
The yaml file contains a dash before 'secondary' or other field which is not 'primary'.
|
||||
|
||||
Incorrect:
|
||||
```
|
||||
- primary: SEAD
|
||||
- secondary: air-to-ground
|
||||
aircraft:
|
||||
- VFA-113
|
||||
```
|
||||
|
||||
Correct:
|
||||
```
|
||||
- primary: SEAD
|
||||
secondary: air-to-ground
|
||||
aircraft:
|
||||
- VFA-113
|
||||
```
|
||||
|
||||
#### <<class 'game.theater.controlpoint.Carrier'>: Naval-1>
|
||||
|
||||

|
||||
|
||||
The yaml file doesn't have squadrons defined.
|
||||
|
||||
#### 'NoneType' object is not iterable
|
||||
|
||||

|
||||
|
||||
The campaign yaml file contains a squadron with an 'aircraft' block, but no aircraft (or squadrons).
|
||||
|
||||
Incorrect:
|
||||
```
|
||||
- primary: SEAD
|
||||
secondary: air-to-ground
|
||||
aircraft:
|
||||
- primary: BAI
|
||||
secondary: any
|
||||
aircraft:
|
||||
- VMFA-251
|
||||
```
|
||||
|
||||
Correct:
|
||||
```
|
||||
- primary: SEAD
|
||||
secondary: air-to-ground
|
||||
aircraft:
|
||||
- VFA-113
|
||||
- primary: BAI
|
||||
secondary: any
|
||||
aircraft:
|
||||
- VMFA-251
|
||||
```
|
||||
|
||||
## Designing campaigns in the mission editor
|
||||
|
||||
When creating a campaign it may be easiest to start with an existing campaign in the same theater and modify it to suit your needs. If starting from scratch, ensure that Combined Joint Task Forces Blue and Combined Joint Task Forces Red are assigned to the blue and red coalitions respectively, as these will be used to define many of the campaigns properties.
|
||||
|
||||
Reference in New Issue
Block a user