Page MenuHomeFeedback Tracker

Add an option to disabled mission parameters from being initalized automatically by BIS_fnc_initParams
Feedback, NormalPublic

Description

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.

Details

Severity
Feature
Resolution
Open
Reproducibility
Always
Operating System
Windows 11 x64
Category
Scripting

Event Timeline

R3vo created this task.Jan 10 2024, 5:33 PM
R3vo updated the task description. (Show Details)Jan 10 2024, 6:06 PM
R3vo edited Additional Information. (Show Details)Jan 10 2024, 6:24 PM
BIS_fnc_KK edited Additional Information. (Show Details)Jan 10 2024, 6:32 PM
BIS_fnc_KK set Ref Ticket to AIII-56183.Jan 10 2024, 6:51 PM

BIS_fnc_initParams_skip

~could you please update wiki

BIS_fnc_KK removed BIS_fnc_KK as the assignee of this task.Jan 11 2024, 1:47 PM
BIS_fnc_KK changed the task status from New to Feedback.
BIS_fnc_KK added a subscriber: BIS_fnc_KK.