Restores handling of TheaterGroundObject targets in antishipingress.py
This is needed when anti-ship missions are planned against other ship groups than NavalControlPoints (carrier groups or LHA strike groups).
* Added a separate Doctrine page in settings with the following new options:
- Minimum number of aircraft for autoplanner to plan OCA packages against
- Airbase threat range (nmi)
- TARCAP threat buffer distance (nmi)
- AEW&C threat buffer distance (nmi)
- Theater tanker threat buffer distance (nmi)
Implemented handling for the OPFOR autoplanner aggressiveness in objectivefinder.py vulnerable_control_points().
* * Added three new options in Settings:
- Autoplanner plans refueling flights for Strike packages
- Autoplanner plans refueling flights for OCA packages
- Autoplanner plans refueling flights for DEAD packages
Fixed a bug in faction.py where F-16Ds were not correctly removed from the faction when the F-16I/F-16D mod was not selected.
* Renamed Maximum frontline length -> Maximum frontline width.
* WRL Faction Updates
I've updated all factions to have the same exact air assets to streamline the ability to use my factions anywhere. The difference in my factions is the units used in frontlines, SAMs, and so on. I still have to use custom factions to ensure my missions are played as I designed them. People can customize them from there. The new WRL mixed faction is going to be used in all wargame scenarios and some Sinai map stuff I've been looking at making.
The manual for the legacy warthog usually calls these VHF 1/2 and UHF,
or VHF AM/FM and UHF. The AM/FM nomenclature is what I usually hear
people call them and it's clearer, so go with that.
For the A-10C II, that manual hasn't been updated for the AN/ARC-210
yet, so I'm not really sure what that ought to be called. The UFC calls
it COM 1 though, so I went with that. The alternative would be something
like VHF/UHF for the 210 and UHF for the 164, but I don't know if that's
actually better. Could be completely explicit and call them by their
full names, but that's probably less clear to people that aren't
fiddling with the radio implementation constantly (and even I confuse
the 164 and the 186 all the damn time).
* A-6A Intruder with Adecarcer's hardpoint options from A-7E mod
Enabled Adecarcer's modified hardpoint options for the A-6A Intruder mod, now also including weapons from the A-7E Corsair II mod. Please note that the A-7E mod will need to be installed if one wants to use those weapons.
* Moved the import "from pydcs_extensions import WeaponsA7E" to within the VSN_A6A pylon objects to help solve the "cannot import from partially initialized module" error.
* Import pydcs_extensions.a7e before pydcs_extensions.a6a to help solve the "cannot import from partially initialized module" error.
* Added inject_weapons(WeaponsA7E) in a6a.py
The old DCS AI F-15E is sticking around because the two have very
different weapon sets for now, so it's probably better to use the AI-
only one for squadrons that don't expect players.
I've avoided renaming the old one (we probably should name it "... (AI)"
for clarity) because the rename will break save compat. I have added a
_new_ name that new campaigns can use though.
https://github.com/dcs-liberation/dcs_liberation/issues/3028
