mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
4993353184
The UI won't stop you from aborting a flight that is already home, but that should also result in it re-completing again on the next tick. https://github.com/dcs-liberation/dcs_liberation/issues/1680
40 lines
919 B
Python
40 lines
919 B
Python
from __future__ import annotations
|
|
|
|
from datetime import datetime, timedelta
|
|
from typing import TYPE_CHECKING
|
|
|
|
from dcs import Point
|
|
|
|
from .flightstate import FlightState
|
|
from ..starttype import StartType
|
|
|
|
if TYPE_CHECKING:
|
|
from game.sim.gameupdateevents import GameUpdateEvents
|
|
|
|
|
|
class Completed(FlightState):
|
|
@property
|
|
def cancelable(self) -> bool:
|
|
return False
|
|
|
|
def on_game_tick(
|
|
self, events: GameUpdateEvents, time: datetime, duration: timedelta
|
|
) -> None:
|
|
return
|
|
|
|
@property
|
|
def is_waiting_for_start(self) -> bool:
|
|
return False
|
|
|
|
def estimate_position(self) -> Point:
|
|
return self.flight.arrival.position
|
|
|
|
@property
|
|
def spawn_type(self) -> StartType:
|
|
# TODO: May want to do something different to make these uncontrolled?
|
|
return StartType.COLD
|
|
|
|
@property
|
|
def description(self) -> str:
|
|
return "Completed"
|