You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem?
It's nice to use a cba_settings.sqf file on the server for default settings, as this allows it to be configured in a Git repo and used on multiple servers. Unfortunately, using this file means admins can't dynamically change server settings during missions.
Solution you'd like:
Allow admins to change server settings during missions, even if they were loaded from a cba_settings.sqf file. The change should persist until the server shuts down (each time the server starts, it should re-load the defaults from cba_settings.sqf).
Alternatives you've considered: @veteran29 suggested using a XEH_PreInit script in an addon that reads the default settings from a different file and sets them; this allows them to be altered during missions, but they'll reset to defaults on next server start (as desired). However, since there's no way to control initialization order of addons, it's possible that other addons could initialize first, find that there is no value set for the given setting, and use the setting's default value instead.
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem?
It's nice to use a
cba_settings.sqf
file on the server for default settings, as this allows it to be configured in a Git repo and used on multiple servers. Unfortunately, using this file means admins can't dynamically change server settings during missions.Solution you'd like:
Allow admins to change server settings during missions, even if they were loaded from a
cba_settings.sqf
file. The change should persist until the server shuts down (each time the server starts, it should re-load the defaults fromcba_settings.sqf
).Alternatives you've considered:
@veteran29 suggested using a XEH_PreInit script in an addon that reads the default settings from a different file and sets them; this allows them to be altered during missions, but they'll reset to defaults on next server start (as desired). However, since there's no way to control initialization order of addons, it's possible that other addons could initialize first, find that there is no value set for the given setting, and use the setting's default value instead.
The text was updated successfully, but these errors were encountered: