Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global settings forced on server instead of in mission by default #580

jonpas opened this issue Jan 25, 2017 · 1 comment


None yet
3 participants
Copy link

commented Jan 25, 2017

Arma 3 Version: 1.66 (stable)
CBA Version: 3.1.2 (dev 9b824dc1b497b2a549b28c4b7a016d5f692df7e0)


  • @CBA_A3
  • @acre2


  • Global settings are forced on server by default instead of in mission (requiring a server admin to un-force the setting on server to allow mission maker to set it in mission).
  • Should probably be forced in mission by default and only forced on server if set so.
  • @PabstMirror pointed out a possible bug in
    GET_FORCED(serverSettings,_setting) || {(!GET_FORCED(missionSettings,_setting)) && {(isMultiplayer && {NAMESPACE_GETVAR(GVAR(defaultSettings),_setting,[]) param [7, false]})}};

Steps to reproduce:

  • Load some default global settings.
  • See they are forced on server instead of in mission.

Where did the issue occur?

  • Dedicated

RPT log file:

  • Not applicable

Point of observation is "Force" column:


This comment has been minimized.

Copy link

commented Feb 1, 2017

I was about to ask this myself however I found a workaround in the meantime by using in the postInit ["server"] call CBA_settings_fnc_clear;

@commy2 commy2 added this to the 3.3 milestone Mar 20, 2017

@commy2 commy2 self-assigned this Mar 20, 2017

@commy2 commy2 added the Bug label Mar 20, 2017

@commy2 commy2 referenced this issue Mar 20, 2017


improve settings #606

@commy2 commy2 closed this in #606 Apr 8, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.