Address issues from the original F3 repo

[shadow-fa]

Needs to be discussed:

• Param for assigning flashlights to PCs/NPCs Param for assigning flashlights to PCs/NPCs ferstaberinde/F3#748

• Night and day mode Night and day mode ferstaberinde/F3#659

• Survivable Crashes Survivable Crashes ferstaberinde/F3#732

Low priority:

• What to do with Debug What to do with Debug ferstaberinde/F3#514 Tracked separately What to do with Debug #162

Wont fix:

• Removal of F3 AI Skill Removal of F3 AI Skill ferstaberinde/F3#777

Partially resolved:

• Casualties Cap: accept multiple sides as input ferstaberinde/F3#693
  It's trivial to just create a new array using f_var_groups_*
  TODO: Maybe add an example to the documentation/wiki

Resolved:

• Incorrect GL smoke for NATO and NATO Pacific loadouts ferstaberinde/F3#790
  Fixed by PR Minor NATO assignGear fixes #6 and Fix incorrect smoke color #76
• AssignGear: Improper argument can be fed to BIS_fn_selectRandom ferstaberinde/F3#780
  Works as intended. Only results in an error if the mission maker edits the file incorrectly
• CasCap: Use BIS_fnc_endMissionServer ferstaberinde/F3#779
  This has already been fixed by using f_fnc_mpEnd
• Casualties Cap: Multiple endings possible ferstaberinde/F3#776
  Fixed by PR mpEnd: avoid triggering of multiple endings #78

[SamLex]

F3 AI Skill
Isn't this still very useful for changing AI skill from parameters?

Cas cap: sides
I think the solution mentioned in that issue is cleaner: passing all groups from the relevant sides (can easily be done with f_var_groups_*)

Cas cap: multi-end
I think would be better solved with a more general change to mpEnd to not trigger an ending if one has already been started.

Player flashlights
This shoulds great; I would have really liked this on Tuesday as I wanted night missions but in some missions players didn't have NVGs (for good reasons) but also didn't have flashlights.

A potential issues with this though is that I think there is some guns that can't have a flashlight attachment, potentially causing a scenario where the host sets the time to night and uses this but then no one can see as they don't have flashlights.

Survivable Crashes
I like the idea of this, potentially even enabled by default to reduce the impact of transport helo crashes, but integrating it into BIS revive would need to be explored.

Day/night mode
Similar to player flashlights, seems like an ok idea. Might be worth doing at the same time as the proposed assign gear refactor (#49) if it happens, with maybe looking at a more general method for having parameter selectable gear variants as one for standard, light, day and night will become a large maintenance problem with the current system.

Debug
I assume this is referring to the DEBUG prints sprinkled throughout the code.

I think it has some limited uses, so should stay, but I think it needs a more formal approach taken, such as always logging function parameters and important variables. I think the original thread also has some valid points about sideChat; would it be possible to do something with briefing? I know there is a 'Log' tab but not sure how to access it.