From aaeb815b4f12f4874509f8a348f60f6ff837aa98 Mon Sep 17 00:00:00 2001
From: IllianiCBT <danielfarbrace@icloud.com>
Date: Fri, 22 Nov 2024 11:47:13 -0600
Subject: [PATCH] Fix reconnaissance scenario time limit parameters

Changed `timeLimitAtMost` to false and updated `timeLimitType` to `ScaledToPrimaryUnitCount` to enhance the flexibility of time limits. Added `timeLimitScaleFactor` set to 2 to ensure the time limit scales appropriately with the number of primary units.
---
 MekHQ/data/scenariotemplates/Reconnaissance Interdiction.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/MekHQ/data/scenariotemplates/Reconnaissance Interdiction.xml b/MekHQ/data/scenariotemplates/Reconnaissance Interdiction.xml
index fb699e8b6e..fd5d3412f8 100644
--- a/MekHQ/data/scenariotemplates/Reconnaissance Interdiction.xml	
+++ b/MekHQ/data/scenariotemplates/Reconnaissance Interdiction.xml	
@@ -140,8 +140,9 @@
             <destinationEdge>NONE</destinationEdge>
             <objectiveCriterion>Preserve</objectiveCriterion>
             <percentage>50</percentage>
-            <timeLimitAtMost>true</timeLimitAtMost>
-            <timeLimitType>None</timeLimitType>
+            <timeLimitAtMost>false</timeLimitAtMost>
+            <timeLimitScaleFactor>2</timeLimitScaleFactor>
+            <timeLimitType>ScaledToPrimaryUnitCount</timeLimitType>
         </scenarioObjective>
     </scenarioObjectives>
 </ScenarioTemplate>