From a658e41c547bcab13b1057679893dcc2d06b8d95 Mon Sep 17 00:00:00 2001
From: Raffson <Raffson@users.noreply.github.com>
Date: Sun, 21 Jul 2024 22:09:55 +0200
Subject: [PATCH] Use EngageTargetsInZone for SEAD Sweep instead

Seems to perform better, AI wonders less off to places it shouldn't...
---
 .../aircraft/waypoints/seadsweepingress.py                | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/game/missiongenerator/aircraft/waypoints/seadsweepingress.py b/game/missiongenerator/aircraft/waypoints/seadsweepingress.py
index 4f8c2275..f06eefd7 100644
--- a/game/missiongenerator/aircraft/waypoints/seadsweepingress.py
+++ b/game/missiongenerator/aircraft/waypoints/seadsweepingress.py
@@ -2,8 +2,8 @@ from dcs.point import MovingPoint
 from dcs.task import (
     OptECMUsing,
     ControlledTask,
-    EngageTargets,
     Targets,
+    EngageTargetsInZone,
 )
 
 from game.utils import nautical_miles
@@ -19,9 +19,9 @@ class SeadSweepIngressBuilder(PydcsWaypointBuilder):
 
         waypoint.add_task(
             ControlledTask(
-                EngageTargets(
-                    # TODO: From doctrine.
-                    max_distance=int(
+                EngageTargetsInZone(
+                    position=self.flight.flight_plan.tot_waypoint.position,
+                    radius=int(
                         nautical_miles(
                             self.flight.coalition.game.settings.sead_sweep_engagement_range_distance
                         ).meters