weyne/dcs_liberation
1
0
Fork 0
mirror of https://github.com/dcs-liberation/dcs_liberation.git synced 2025-11-10 14:22:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Skynet properties override

RndName 2022-04-06 19:32:58 +02:00
parent 855abb535e
commit 49df22b21c
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Custom-campaigns.md

@ -450,6 +450,25 @@ If no iads_config is defined in the campaign.yaml the "by range" option will be
The advanced assets like Comms, Power and C2 can be placed like any other ground object using the placeholder unit defined in this table [Unit Type Quick Reference](#unit-type-quick-reference-1) or via a [Map Object](#map-objects). When Map objects are used the system will generate a static dummy M4 Soldier next to the object. This is required so that skynet has a unit to control and track the alive/death state of it. This unit does not serve any purpose beside this. The kill of a map object is strill tracked by destroying the object and not the soldier.
#### Skynet Plugin
Liberation adds the [Skynet Plugin](https://github.com/walder/Skynet-IADS) to the created dcs mission if the user enables the plugin in the campaign settings. This plugin is enabled by default in Liberation V6.0 as it is heavily integrated into the Liberation system which created the IADS Network. Skynet allows to set specific options for SAM Systems which can be overwritten in the unit.yaml for the Search Radar of the SAM Systems. Which SAM Systems are supported by Skynet and which Search Radar is used for wich SAM system can be found in this file: [skynet-iads-supported-types.lua](https://github.com/walder/Skynet-IADS/blob/develop/skynet-iads-source/skynet-iads-supported-types.lua)
To overwrite specific skynet properties the following options can be set in the unit.yaml of the Search Radar (Patriot SR as example):
```yaml
class: SearchRadar
price: 22
variants:
SAM Patriot STR: null
skynet_properties: # Override skynet default properties
can_engage_harm: true
can_engage_air_weapon: true # https://github.com/walder/Skynet-IADS/tree/develop#engage-air-weapons
go_live_range_in_percent: 100
harm_detection_chance: 90
engagement_zone: SkynetIADSAbstractRadarElement.GO_LIVE_WHEN_IN_KILL_ZONE # https://github.com/walder/Skynet-IADS/tree/develop#engagement-zone
autonomous_behaviour: SkynetIADSAbstractRadarElement.AUTONOMOUS_STATE_DCS_AI # https://github.com/walder/Skynet-IADS/tree/develop#autonomous-mode-behaviour
```
Documentation about each setting can be found at the Skynet GitHub page which is linked above.
#### Anti Air GroundObjects
SAM locations are split into four types: long range, medium range, short range, and AAA. Each type of position will prefer to be filled by its exact type, but if the faction has no air defenses of that type available the generator will continue to downgrade the site until it finds a match. For example, a medium range SAM may be used in place of a long range SAM. _Upgrades_ are not allowed.