(01-12-2014, 05:16 AM)Taugeshtu Wrote: [...] Objection. Should plugin author decide to change plugin's name [...]
If they decide to change the name, they will most likely change other functionality, too, so it makes sense to actually update all the code that interfaces to that plugin. If it hurts so much, you can store the plugin name in a global variable and use that.
The other day I was considering a slight change in how things are - the plugins would have two names, one "internal" exactly for the purposes of interplugin communication and perhaps to identify the plugins if we ever get a "plugin repository"; those names would be restricted in what characters they can use and how long they are etc. Then there'd be "NiceName", a name visible to the server admins, so that the plugin can be called whatever it wants to, and change that name without affecting the functionality. This actually came from the bewilderment about cPlugin:SetName() - what is that function supposed to even do? Why set a name for a plugin that already has a name?
(01-12-2014, 05:16 AM)Taugeshtu Wrote: [...] What would really bring good benefit to this is perhaps "OnPluginsLoaded" hook [...]
Already implemented: http://mc-server.xoft.cz/LuaAPI/OnPluginsLoaded.html