You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can see in this picture: http://puu.sh/7eEwQ.png that my "Path" plugin is considered a plugin with an error, but that's because it's just activated.
I haven't looked too much into it, but I'm guessing it's because the core already editted the settings.ini but MCServer didn't load Path since it has to be reloaded first.
The text was updated successfully, but these errors were encountered:
I'm afraid there's no easy way around this - there's no way to distinguished between a plugin that hasn't been loaded due to an error and due to just having been activated.
Perhaps the Core could store a list of plugins that it had just activated, and check that list before claiming an error; however, that won't help with plugins being just-loaded by other means (if we ever get that loadplugin console command)
You can see in this picture: http://puu.sh/7eEwQ.png that my "Path" plugin is considered a plugin with an error, but that's because it's just activated.
I haven't looked too much into it, but I'm guessing it's because the core already editted the settings.ini but MCServer didn't load Path since it has to be reloaded first.
The text was updated successfully, but these errors were encountered: