Minedetector - Improvement: Add setting to boost radius of detectors

[OverlordZorn]

When merged this pull request will:

• add CBA Settings: Boost Radius
• New Function: getDetectorRadius - returns radius based on settings
• New Function: updateDetectorRadius - updates radius inside cached hashmap upon setting change
• PostInit: Added CBA Eventhandler to call updateDetectorRadius

Motivation:

In some missions combined with some Mods, like IEDD Notebook, IEDs can be hard to spot.

Besides the ACE Mine Detectors with their rather short radius of 2.5 meters and the Vanilla Minedetector with its 15 meters + Radar screen, there is no inbetween.

This enables mission makers to finetune the players experience and provides something in the middle ground.

[johnb432]

Imo the settings contradict #11347 somewhat: you have a setting that forces everything to be the same, but in mentioned PR you make them different?
I don't see a point in the settings.

[OverlordZorn]

Imo the settings contradict #11347 somewhat: you have a setting that forces everything to be the same, but in mentioned PR you make them different? I don't see a point in the settings.

Reasoning:

I've ran campaigns/missions with some IED mods like IEDD Notebook where the ace mine detectors where not practical cause the IEDs were that well hidden.

The only alternative i had was to give the players the vanilla mine detector. With some hacky commands i was able to at least disable the sidepanel overlay.

That is why i propose the setting.

If you're unhappy with the way the values are applied, then yea, its kinda awkward. I was considering a "modifier" setting/slider instead but that didnt felt right ether.

As an alternative, I can offer to make it an "boost" which adds range to the existing config radius.

[Drofseh]

I think a single setting that applies a coefficient would be fine.

[OverlordZorn]

I think a single setting that applies a coefficient would be fine.

im currently changing it to a "add boost" setting, can also condense it down to a single setting.

Im a bit hessitant to make it a coefficient due to it being an abritary number in "percentage".
by adding a boost people can add a "range" in meters, which i think is easier to grasp. but im open for other opinions here.

[Drofseh]

X + Y and X * Y are equally arbitrary.
I'd prefer the multiplier because then you know all detectors have been scaled by the same relative amount.

With a 2x multiplier a 2.5m detector has become 5m and a 5m detector has become 10m. The better detector is still has twice the radius of the worse detector.

With an addative boost of +2.5m the 2.5m detector has still become 5m, but the 5m detector is now only 7.5m, so instead of having double the radius it only has a 50% larger radius over the worse detector.

[OverlordZorn]

hemtt run timed out

HTTPError: Response code 403 (rate limit exceeded)
    at Request.<anonymous> (D:\a\_actions\arma-actions\hemtt\v1\dist\main\index.js:6913:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_NON_2XX_3XX_RESPONSE',

[PabstMirror]

just wondering now if we need a whole new category for this one setting
we could do something like
[format ["ACE %1", LELSTRING(explosives,Menu)], localize LSTRING(Category)],
and put it under [ace explosives, mine detector]

[OverlordZorn]

We could, im just not a fan of having to search for a setting in an indirectly related category.