mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
a2630fc75f
Putting the ingress point directly on one end of the FLOT means that AI flights won't start searching and engaging targets until they reach that point. If the front line has advanced toward the flight's departure airfield, it might overfly targets on its way to the IP. Instead, place an IP for CAS the same way we place any other IP. The AI will fly to that and start searching from there. This also: * Removes the midpoint waypoint, since it didn't serve any real purpose * Names the FLOT boundary waypoints for what they actually are Fixes https://github.com/dcs-liberation/dcs_liberation/issues/2231.
29 lines
797 B
Python
29 lines
797 B
Python
from __future__ import annotations
|
|
|
|
from datetime import timedelta
|
|
from typing import Type
|
|
|
|
from .formationattack import (
|
|
FormationAttackBuilder,
|
|
FormationAttackFlightPlan,
|
|
FormationAttackLayout,
|
|
)
|
|
from ..flightwaypointtype import FlightWaypointType
|
|
|
|
|
|
class SeadFlightPlan(FormationAttackFlightPlan):
|
|
@staticmethod
|
|
def builder_type() -> Type[Builder]:
|
|
return Builder
|
|
|
|
def default_tot_offset(self) -> timedelta:
|
|
return -timedelta(minutes=1)
|
|
|
|
|
|
class Builder(FormationAttackBuilder[SeadFlightPlan, FormationAttackLayout]):
|
|
def layout(self) -> FormationAttackLayout:
|
|
return self._build(FlightWaypointType.INGRESS_SEAD)
|
|
|
|
def build(self, dump_debug_info: bool = False) -> SeadFlightPlan:
|
|
return SeadFlightPlan(self.flight, self.layout())
|