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

Convert spectator to CBA settings #4456

Closed
wants to merge 4 commits into from
Closed

Convert spectator to CBA settings #4456

wants to merge 4 commits into from

Conversation

kymckay
Copy link
Member

@kymckay kymckay commented Sep 24, 2016

Believe I've done this correctly, running a function on setting change is a much welcome addition that fits nicely with the way I've structured spectator already.

@kymckay
Copy link
Member Author

kymckay commented Sep 24, 2016

This is also what had me confused while doing this: #4024 (comment)

What I expect to happen is: Global settings don't appear in the CLIENT section, only under SERVER and MISSION (with the Force checkbox locked to activated under MISSION).

@commy2
Copy link
Contributor

commy2 commented Sep 24, 2016

@SilentSpike wait for the next CBA. Pabst changed some things around about this.

@commy2 commy2 closed this Sep 24, 2016
@commy2 commy2 reopened this Sep 24, 2016
@PabstMirror PabstMirror modified the milestones: CBA Settings, 3.8.0 Oct 3, 2016
@kymckay
Copy link
Member Author

kymckay commented Oct 9, 2016

Tangentially related to this (conversion of the zeus settings), but is there a way to do what we currently do here using the new CBA settings.

Keep in mind this is within a module function so multiple instances could run at any point in the mission (i.e. I can't easily add a function to be ran when the setting is changed since each instance of this is associated with an individual logic initialised at an arbitrary time).

kymckay added 3 commits April 15, 2017 13:02
Same implimentation as is used in ACRE for CBA settings. A call to the
public API will prevent future changes of the CBA setting from having
an effect in order to preserve the intent of the mission maker (possible
to have differing setups on different clients, etc.)
This function doubles as a public API and for internal use (when called
with no arguments it keeps the list up to date with all the applicable settings).
kymckay added a commit that referenced this pull request Apr 15, 2017
The default values of the arrays manipulated by these functions overwrite
any changes applied before settings have finished initalising. This won't
be an issue after #4456 is merged in future.
kymckay added a commit that referenced this pull request May 5, 2017
The default values of the arrays manipulated by these functions overwrite
any changes applied before settings have finished initalising. This won't
be an issue after #4456 is merged in future.
@kymckay kymckay closed this Dec 28, 2017
@kymckay kymckay deleted the settings-spectator branch December 28, 2017 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants