Plugins can be loaded from the deployed version of the bot; at this point we know what version they are, or they can be loaded from random scary places, at which point we don't.
It'd be nice if !plugin.list could identify "modified" plugins, i.e. ones not shipped with the distribution.
(Note: Choob Prime currently is loading most plugins from file:// instead of choob-plugin://. Actually, thinking about it, do we want to have to redeploy to pick up plugins? 2773fef2654a8ee90d1c1d446cc478b973ec2b3b allows us to use choob-plugin but allow modifications too, argh.)
Since the current code loads choob-plugin: from the filesystem first, then from embedded resources, what is the most important thing here? Is it the use of the meta-scheme, or the use of embedded resources?
Plugins can be loaded from the deployed version of the bot; at this point we know what version they are, or they can be loaded from random scary places, at which point we don't.
It'd be nice if !plugin.list could identify "modified" plugins, i.e. ones not shipped with the distribution.
(Note: Choob Prime currently is loading most plugins from file:// instead of choob-plugin://. Actually, thinking about it, do we want to have to redeploy to pick up plugins? 2773fef2654a8ee90d1c1d446cc478b973ec2b3b allows us to use choob-plugin but allow modifications too, argh.)