Change Details

Currently, mission parameters are always initialized if defined in mission config. The function `BIS_fnc_initParams` is automatically executed `postInit` with no way to prevent it from doing so. It would be very welcome if the function would check for the presence of a missionNamespace variable and if that one is true exit before initializing the parameters. ``` if (missionNamespace getVariable ["BIS_fnc_noParameterInitialization", false]) exitWith {false}; ``` This variable could be set in `preInit` by the mission creator. This would allow for a customized system to handle mission parameters in singleplayer as there is no native way of manipulating parameter values there.

Currently, mission parameters are always initialized if defined in mission config in multipayer and `singleplayer`. The function `BIS_fnc_initParams` is automatically executed `postInit` with no way to prevent it from doing so. As we don't have a native way to changing parameter values in `singleplayer` it would be nice if we had a way to telling `BIS_fnc_initParams` to exit early in `singleplayer`. (Multiplayer behaviour should not be changed) If the function would check for the presence of a missionNamespace variable and if that one is true exit before initializing the parameters. ``` if (!isMultiplayer && {missionNamespace getVariable ["BIS_fnc_noParameterInitialization", false]}) exitWith {false}; ``` This variable could be set in `preInit` by the mission creator. This would allow scenario creators to implement a custom UI in `singleplayer` to allow players to customize the mission parameters without them being first executed with default parameters.

Currently, mission parameters are always initialized if defined in mission config in multipayer and `singleplayer`. The function `BIS_fnc_initParams` is automatically executed `postInit` with no way to prevent it from doing so. As we don't have a native way to changing parameter values in `singleplayer` it would be nice if we had a way to telling `BIS_fnc_initParams` to exit early in `singleplayer`. (Multiplayer behaviour should not be changed) It would be very welcome if the function would check for the presence of a missionNamespace variable and if that one is true exit before initializing the parameters. ``` if (!isMultiplayer && {missionNamespace getVariable ["BIS_fnc_noParameterInitialization", false]}) exitWith {false}; ``` This variable could be set in `preInit` by the mission creator. This would allow for a customized system to handle mission parameters in singleplayer as there is no native way of manipulating parameter values therescenario creators to implement a custom UI in `singleplayer` to allow players to customize the mission parameters without them being first executed with default parameters.