-
Notifications
You must be signed in to change notification settings - Fork 736
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
Conversation
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 |
@SilentSpike wait for the next CBA. Pabst changed some things around about this. |
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). |
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).
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.