continue iads_config clarification

RndName 2022-11-08 19:19:48 +01:00
parent f6d8d9c0e8
commit 0c3094ad6f

@ -89,18 +89,18 @@ Primary nodes are:
* Command Center
* Naval Unit (Carrier)
What should **not** be added to that list as primary node:
* AWACS
AWACs are not required to be defined. They are added automatically.
Secondary nodes which should **not** be added to that list as primary node:
* Connection Nodes
* Power Sources
* Point Defense
These nodes (except AWACS which will be added automatically) will be added to the connected primary Nodes. Example of such a connection where `SAM1` has a connection to `CN1` and `PS1`:
These secondary nodes will be added as a list to the primary node which they are connected to. Example of such a connection where the primary node `SAM1` has a connection to the secondary nodes `ConnectionNode1` and `PowerSource1`:
```yaml
iads_config:
- SAM1: # Group name of the SAM, EWR or Command Center used in the campaign.miz
- CN1 # All connected nodes (Comms, Power, PointDefense)
- PS1 # Exact name of the connected group used in the campaign.miz
- SAM1: # Group name of the primary Node (SAM, EWR or Command Center) used in the campaign.miz
- ConnectionNode1 # All connected secondary nodes (Comms, Power) as list
- PowerSource1 # Exact name of the group used in the campaign.miz otherwise it will not be recognized
```
Every primary node can have 0..N connections (Comms, Power Source, Point Defense) which have to be added as a list to the primary node with the exact group name used in the campaign.miz. If no connections are added to a primary node it will participate to the IADS Network without requiring Comms or Power (equal to the functionality of the Basic mode). It is not possible to connect two Connection Nodes with each other. Every connection has to be between one Primary Node (see above) and a non-Primary Node.