Medical - Add hooks for (de)serializing medical state (#11255)

Author: LinkIsGrim

addons/medical/functions/fnc_deserializeState.sqf

@@ -128,4 +128,6 @@ if (_currentState in ["Unconscious", "CardiacArrest"] && {_targetState in ["Defa
 // Manually activate if non-defaults are present
 [_unit] call EFUNC(medical_engine,checkForMedicalActivity);
 
+[QGVAR(deserialize), [_unit, _state]] call CBA_fnc_localEvent;
+
 _state call CBA_fnc_deleteNamespace;

addons/medical/functions/fnc_serializeState.sqf

@@ -60,6 +60,8 @@ _state setVariable [VAR_MEDICATIONS, _medications];
 private _currentState = [_unit, GVAR(STATE_MACHINE)] call CBA_statemachine_fnc_getCurrentState;
 _state setVariable [QGVAR(statemachineState), _currentState];
 
+[QGVAR(serialize), [_unit, _state]] call CBA_fnc_localEvent;
+
 // Serialize & return
 private _json = [_state] call CBA_fnc_encodeJSON;
 _state call CBA_fnc_deleteNamespace;

docs/wiki/framework/medical-framework.md

@@ -265,3 +265,28 @@ ace_medical_const_medicalActivity = true;
 unit setVariable ["ace_medical_medicalActivity", true]  
 ```
 Once medical activity has been enabled, you can't disable it. In other words: if you execute `unit setVariable ["ace_medical_medicalActivity", true]`, you can't disable medical activity for that specific AI anymore. If you run `ace_medical_const_medicalActivity = true;`, you can no longer set it to `false` and all AI will have their medical activity enabled.
+
+## 6. Persisting medical state between missions
+
+A unit's medical state can be saved to JSON by calling `ace_medical_fnc_serializeState`. This can then be persisted in `profileNamespace` or your preferred flavor of persistence:
+```sqf
+private _state = player call ace_medical_fnc_serializeState;
+
+profileNamespace setVariable ["MyPlayerMedicalState", _state];
+saveProfileNamespace;
+```
+
+After a mission restart, `ace_medical_fnc_deserializeState` can be called:
+```sqf
+private _state = profileNamespace getVariable ["MyPlayerMedicalState", ""];
+
+[player, _state] call ace_medical_deserializeState;
+```
+
+## 6.1 Extending with custom handling
+
+You can save additional data or add custom handling by hooking into the events:
+| Event Name | Params | Description |
+| ---------- | ------ | ----------- |
+| ace_medical_serializeState | Unit, Namespace | Raised locally after ACE Medical's serialization has taken place |
+| ace_medical_deserializeState | Unit, Namepsace | Raised locally after ACE Medical's deserialization has taken place |