Updated Squadrons and pilots (markdown)

Starfire13 2025-04-06 20:51:16 +10:00
parent 7ae1d38e9e
commit 603f9c198b

@ -2,7 +2,7 @@
Each aircraft in the mission will be assigned one pilot. Each pilot belongs to a squadron. Pilots are assigned to aircraft using the flight edit dialog (later they will be assignable when creating flights).
**Note:** Multi-crew aircraft get only one pilot. Non-pilot air crews are not modeled in Liberation. Other player slots will still be available in game.
**Note:** Multi-crew aircraft get only one pilot. Non-pilot air crews are not modeled in Retribution. Other player slots will still be available in game.
Pilots can be killed. When the aircraft the pilot is flying is destroyed the pilot will be killed and a new pilot will need to replace them in the squadron. Completing missions will increase the skill level of AI pilots.
@ -15,7 +15,7 @@ Optionally (off by default), new pilots will be recruited to the squadron each t
### Players
Each pilot can be set as either a player or AI pilot. Instead of creating client slots in flights as in previous versions of Liberation, pilots are set as players and those pilots are assigned to flights.
Each pilot can be set as either a player or AI pilot. Instead of creating client slots in flights, pilots are set as players and those pilots are assigned to flights.
By default player pilots cannot be killed. This can be toggled in the difficulty options. **The aircraft is still lost when the player's aircraft is destroyed.**
@ -65,7 +65,7 @@ Optionally (off by default) squadrons have a maximum number of pilots (currently
### Predefined squadrons
Predefined squadrons are loaded from `resources\squadrons\*\*.yaml` (for built-in squadrons) and from `<DCS saved games directory>\Liberation\Squadrons\*\*.yaml` (for user-defined squadrons).
Predefined squadrons are loaded from `resources\squadrons\*\*.yaml` (for built-in squadrons) and from `<DCS saved games directory>\Retribution\Squadrons\*\*.yaml` (for user-defined squadrons).
The directory name within the squadrons directory is not important; it's just to allow organizing the squadron files. For example:
@ -117,9 +117,7 @@ The country and aircraft fields will be used to match squadrons that are found a
The `role` field is currently non-functional. The `role` field will later be shown in the UI as information for the player.
The `mission_types` field determines which mission types to assign to the squadron. The spelling of each entry in `mission_types` should match the spelling of the mission that is used in the Liberation UI. If the squadron specifies a mission type that the aircraft is not capable of, an error will be emitted in the log and the incompatible mission type will not be used for the squadron.
Note: The `mission_types` field is no longer used as of DCS Liberation 7. All squadrons will be capable of all mission types the airframe is capable of, and the auto-assignable mission types are defined by the campaign.
The `mission_types` field determines which mission types to assign to the squadron. The spelling of each entry in `mission_types` should match the spelling of the mission that is used in the Retribution UI. If the squadron specifies a mission type that the aircraft is not capable of, an error will be emitted in the log and the incompatible mission type will not be used for the squadron.
The `livery` field, if set, will be the livery used by all aircraft of this squadron. Default liveries included in DCS should match the quoted portion of the livery name in https://github.com/pydcs/dcs/blob/master/dcs/planes.py. For example, the name for the HAF 330 Thunder livery for a Greek F-16 is `HAF_ 330_Thunder`
@ -142,7 +140,7 @@ The `players` field operates the same as the `pilots` field, but the created pil
The `aircraft` field should match the variant name of the aircraft as specified in the unit data file. For more information about variant names, see https://github.com/dcs-retribution/dcs-retribution/wiki/Custom-Factions#aircraft-and-ground-unit-names.
The `bases` field is new in DCS Liberation 5.0 and can be used to override the default bases that the squadron will operate from. The defaults are set based on the aircraft type:
The `bases` field can be used to override the default bases that the squadron will operate from. The defaults are set based on the aircraft type:
Aircraft type | `shore` | `carrier` | `lha`
--- | --- | --- | ---