M0tah FLhook 1.6.0 plugin?
-
Well, it’s easier for me to make plugins out of the individual features, since I’m not very familiar with the way the plugin interface was implemented. Also, if I did make a version that was compatible with plugins it might not be binary compatible with them, meaning you might have to recompile them for it to work (which is only possible with plugins that include their source code).
…difficult to make into plugins for the current version…
I don’t think that making plugins of the features is any harder than normal when you use the flak_common plugin to do so - that’s one of the reasons I made it.
-
but really it would be an idea to work on, i recently started using your version again, and it runs so efficient (like 0 server load with 0-1 on, and it stays around 5-10 with 5-12 on, compared to the 20 load with w0dka’s, makes me also wonder what you did different…
-
Well, just by how the plugin version works it’s going to be less efficient than having a FLHook that has the features natively implemented. In a native implementation, all of the code that’s in callback functions is in one function, allowing the compiler to optimize the code more. However, with plugins all the code for different features is contained in seperate functions, which makes the code more organized but less efficient.