In some yet unknown circumstances variables can't be written to/read from MissionProfileNamespace while being in initServer environment/mission execution step.
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- Windows 11
- Category
- General
Steps To Reproduce
Mission with the issue:
Steps to reproduce issue with non-loadble variables:
- Start game.
- Start listen server with mission via 3DEN or mpmissions way.
- Start mission.
- Call call TEST_fnc_saveServer - this will call the saveMissionProfileNamespace and put it's content into systemChat bar;
- Close the game entirely.
- Do steps 1-3 again.
- 1 Expected: isMissionProfileNamespaceLoaded: true, allVariables missionProfileNamespace returns all stored variables
- 2 Actual: isMissionProfileNamespaceLoaded: false, allVariables missionProfileNamespacereturns empty array or just callnum, callstring
Steps to reproduce issue with non-writable variables:
- Start game.
- Start listen server with mission via 3DEN or mpmissions way.
- Start mission.
- Call call TEST_fnc_saveServer - this will call the saveMissionProfileNamespace and put it's content into systemChat bar;
- 1 Expected: allVariables missionProfileNamespace returns all stored variables - serverID, callnum, callstring, initservernum, initserverstring
- 2 Actual: allVariables missionProfileNamespace returns some of the stored variables - callnum, callstring , the ones that were saved via simple call, not initServer one