05-11-2015, 09:42 AM
(This post was last modified: 05-11-2015, 11:47 AM by Shadowraix.)
(05-11-2015, 07:28 AM)xoft Wrote: Actually, you'll have to ask @FakeTruth, that's a convention inherited from him.
The problem is, we can't really change it now, because the plugins are already written with this. It would be possible to provide a "compatibility layer", simply doing the equivalent of
cPluginManager = PluginManagerThis would work in most cases, but some plugins take param-checking seriously and do things like
if (tolua.type(a_Param) == "cPlayer") thenThese would break.
Also, there are some people on the team who oppose the Java codestyle (CamelCase classes, almostCamelCase functions).
Hmm...Would it be practical to make a Lua file that when its required it returns a big string making this compatibility layer? Then in the initialize function I can just call loadstring?
Or, if there's an easy way for me to edit the source to do that, I could do so for my own personal use if I could be directed to the API files. My C++ knowledge is sub-optimal but if its just renaming things it wouldn't be too hard for me.
Edit:
I've been looking at the info.lua article. Do sub commands support permissions now? The article states that it doesn't, but I don't know if things have changed since then. If so, might want to update the article.