Fix applying default config to session settings
cda98f moved the plugin manager to not be registered on the eventbus until after the session was opened. The session config was relying on the plugin manager applying the default config based on the session open event. This moves session loading to be prior to applying the default config, so newly added config options get properly set at startup. Fixes config panel breaking which expects the config to always have non-null values for config items with defaults. Co-authored-by: Tomas Slusny <slusnucky@gmail.com>
This commit is contained in:
@@ -241,6 +241,9 @@ public class RuneLite
|
||||
// Load user configuration
|
||||
configManager.load();
|
||||
|
||||
// Load the session, including saved configuration
|
||||
sessionManager.loadSession();
|
||||
|
||||
// Tell the plugin manager if client is outdated or not
|
||||
pluginManager.setOutdated(isOutdated);
|
||||
|
||||
@@ -255,9 +258,6 @@ public class RuneLite
|
||||
// Start client session
|
||||
clientSessionManager.start();
|
||||
|
||||
// Load the session, including saved configuration
|
||||
sessionManager.loadSession();
|
||||
|
||||
// Initialize UI
|
||||
clientUI.open(this);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user