Simplify Map Light Interactions

[PabstMirror]

Currently each flashlight has 2 mutually exclusive child actions
This just shortens the depth of the action tree and puts the toggle action on the flashlight itself.
(The 4th level can be hard to reach on some interface sizes)

@voiperr - If you were planning on adding other actions besides on/off or have any other objections to this please let me know.

before

after

[jokoho48]

what about color switching? didnt have the KSF-1 3 color modes?
else 👍

[voiperr]

The intent was to eventually give colour modes (and filter switching) to the appropriate flashlights, but this was contingent on eventually getting the flashlights to be equippable as weapons.

This change is fine for now, just keep in mind it will be reverted if we ever implement equippable flashlights.

[PabstMirror]

It is possible to add children but have the parent still have a working statement, like this:

[voiperr]

I'm fine with that, but is it consistent with how the rest of ACE's actions work? The parent node never performs functions in Explosives, for instance.

[jokoho48]

if i am right of cause the microDAGR have a sub action under configure if i am righ

[jonpas]

I'm fine with that, but is it consistent with how the rest of ACE's actions work? The parent node never performs functions in Explosives, for instance.

I think I saw plans to change that somewhere.

[MikeMatrix]

This will always return something, so the previous _statement = {}; initialization isn't required here.

[commy2]

This is excellent. Simplify, simplify, simplify!