Dan Albert c65ac5a7cf Move mission range data into the aircraft type. ...

The doctrine/task limits were capturing a reasonable average for the
era, but it did a bad job for cases like the Harrier vs the Hornet,
which perform similar missions but have drastically different max
ranges. It also forced us into limiting CAS missions (even those flown
by long range aircraft like the A-10) to 50nm since helicopters could
commonly be fragged to them.

This should allow us to design campaigns without needing airfields to be
a max of ~50-100nm apart.

2021-07-17 16:34:13 -07:00

..

tasks

Move mission range data into the aircraft type.

2021-07-17 16:34:13 -07:00

__init__.py

Replace existing campaign planner with an HTN.

2021-07-12 13:02:23 -07:00

aircraftallocator.py

Move mission range data into the aircraft type.

2021-07-17 16:34:13 -07:00

garrisons.py

Account for planned missions for breakthrough.

2021-07-13 13:50:50 -07:00

missionproposals.py

Move mission range data into the aircraft type.

2021-07-17 16:34:13 -07:00

missionscheduler.py

Check for available aircraft as task precondition.

2021-07-13 16:26:15 -07:00

objectivefinder.py

Reduce mission planning dependence on Game.

2021-07-13 15:20:42 -07:00

packagebuilder.py

Move mission range data into the aircraft type.

2021-07-17 16:34:13 -07:00

packagefulfiller.py

Move mission range data into the aircraft type.

2021-07-17 16:34:13 -07:00

theatercommander.py

Check for available aircraft as task precondition.

2021-07-13 16:26:15 -07:00

theaterstate.py

Fix type checker issue.

2021-07-13 17:08:37 -07:00