Updated max distance to be configurable (#29)
Publish Release / build (push) Successful in 12s

Partly addresses #24

Does not fully fix thoughReviewed-on: #29

Co-authored-by: dutchie031 <timrorije@gmail.com>
This commit was merged in pull request #29.
This commit is contained in:
2026-08-18 18:23:07 +00:00
committed by dutchie031
parent 63a1ea44db
commit 970f049440
3 changed files with 11 additions and 1 deletions
+4
View File
@@ -24,6 +24,10 @@
PR #28
- Fixed Pre-Activated stages not always drawing or pre-activating correctly.
PR #28
- Addressed #24
CAP max commit range is now configurable in the config.lua file.
Issue remains open in order to apply further fine grained tuning.
PR #29
## [0.12.0] 2026-06
+6
View File
@@ -29,6 +29,12 @@ SpearheadConfig = {
-- unit: feet
maxAlt = 28000, -- default 28000
--The "maxDistance" that's set on the CAP tasking for the aircraft to commit to a target.
--This is the distance from the aircraft to the target that the aircraft will commit to engaging
--This is shared for CAP, Intercept and Sweep missions for now.
-- unit: nautical miles
maxCommitRange = 35, -- default 35
-- DELAYS.
-- Delays work as follow.
-- When an aircraft lands alive and well it will be rearmed and ready to go.
+1 -1
View File
@@ -34,7 +34,7 @@ function CapConfig.new()
self._minDurationOnStation = 1200
self._maxDurationOnStation = 2700
self._maxDeviationRange = 35 * 1852 -- in meters
self._maxDeviationRange = (tonumber(SpearheadConfig.CapConfig.maxCommitRange) or 35) * 1852 -- in meters
self._rearmDelay = tonumber(SpearheadConfig.CapConfig.rearmDelay) or 600
self._repairDelay = tonumber(SpearheadConfig.CapConfig.repairDelay) or 600
self._deathDelay = tonumber(SpearheadConfig.CapConfig.deathDelay) or 1800