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

Setting not forceable when _isGlobal = true #506

Closed
Rall3n opened this issue Sep 21, 2016 · 6 comments
Closed

Setting not forceable when _isGlobal = true #506

Rall3n opened this issue Sep 21, 2016 · 6 comments
Labels
Milestone

Comments

@Rall3n
Copy link

Rall3n commented Sep 21, 2016

Arma 3 Version: 1.62 (stable)
CBA Version: 3.0.0 (stable)

Mods:

  • @CBA_A3
  • @ace3
  • @WIP (Testing)

Description:
Settings is not giving me the option to force a setting, even if _isGlobal parameter is set to true.

[ "variablename", "CHECKBOX", "description", "WIP", false, true ] call CBA_Settings_fnc_init;

Steps to reproduce:

  • Create setting and set _isGlobal parameter to true.
  • Start game.
  • Go into editor and check settings menu.

Where did the issue occur?

  • Editor (Singleplayer)

RPT log file:

@commy2
Copy link
Contributor

commy2 commented Sep 21, 2016

The _isGlobal settings should always be forced. I think they are only displayed on the server (and the client in SP). It should be impossible to change them as dedicated client.

@Rall3n
Copy link
Author

Rall3n commented Sep 21, 2016

I thought it would be possible to change and save them in the mission file from the editor. I know there is the save feature to save a setting template on the local machine.

@commy2
Copy link
Contributor

commy2 commented Sep 21, 2016

Yeah. isGlobal settings cannot be forced by the mission, but are always overwritten by the server...
This should be addressed here: #437
And therefore be fixed in the next version.

@Rall3n
Copy link
Author

Rall3n commented Sep 21, 2016

That's good to hear. Then I have to wait for the newest version of CBA.

@commy2
Copy link
Contributor

commy2 commented Sep 21, 2016

Plan is to release it when 1.64 comes. So in a week. We have to wait for #500 which needs the update and is needed after the update...

@commy2 commy2 added the Feature label Sep 23, 2016
@commy2 commy2 added this to the 3.1 milestone Sep 23, 2016
@commy2 commy2 assigned commy2 and unassigned commy2 Sep 23, 2016
@commy2
Copy link
Contributor

commy2 commented Sep 23, 2016

done #437

@commy2 commy2 closed this as completed Sep 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants