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

Fix Server not reading modules #1598

Merged
merged 3 commits into from
Jun 13, 2015
Merged

Fix Server not reading modules #1598

merged 3 commits into from
Jun 13, 2015

Conversation

PabstMirror
Copy link
Contributor

Critical:
InitSettingsFromModules in only called from a PFEH bellow if (!hasInterface) exitWith {};,
so dedicated servers never read modules.

Also, fixes a possible issue where the server has synced GVAR(settings), but not finished syncing all the modules. Clients could raise SettingsInitialized before all module setting have been recieved. Server now sets a bool publicVariable after reading all modules.

@PabstMirror PabstMirror added the kind/bug-fix Release Notes: **FIXED:** label Jun 13, 2015
@PabstMirror PabstMirror added this to the 3.1.0 milestone Jun 13, 2015
@nicolasbadano
Copy link
Contributor

Totally true, and definitely an improvement but...

I'm thinking now that if "SettingsInitialized" shouldn't be thrown only after the init from module thing has finished on the server. TBH this whole settings system is giving me headaches atm.

@ViperMaul
Copy link
Contributor

Keep your thoughts on this one. This PR is important for most communities. I'd like to see it get finished in time.

nicolasbadano added a commit that referenced this pull request Jun 13, 2015
@nicolasbadano nicolasbadano merged commit c168afe into master Jun 13, 2015
@nicolasbadano nicolasbadano deleted the serverModulesFirst branch June 13, 2015 15:01
@nicolasbadano
Copy link
Contributor

I've read it more carefully, and @PabstMirror addressed my concern already. Perfect!

Bottom line:

1 - Server inits settings from config
2 - Server inits modules
3 - Clients launch the "SettingsInitialized" event locally when the above is ready and received.

Brilliant! That's exactly what we need. Initing features on "SettingsInitialized" should be now much more reliable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug-fix Release Notes: **FIXED:**
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants