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

Plugins tab sees other plugins that are just activated as plugins with an error #66

Open
NiLSPACE opened this issue Mar 1, 2014 · 1 comment

Comments

@NiLSPACE
Copy link
Member

NiLSPACE commented Mar 1, 2014

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.

@madmaxoft
Copy link
Member

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants