1MB memory can actually be replace by 3 or 4 plugins. Less useless extra memory = more room for plugins to be loaded. H-Ext isn't focused on just server only. It also support the client as well. So the users can actually use the same plugin for either server or client side and host or for some specific plugins can be only used on client side such as sight jacker.
I'm pretty sure the final and few previous S-Ext did covered all of the memory leaks.
Plus allow the developers to use their preferred compilier version instead of "must be" specific compilier version. We are still trying to figure out with C# lanuage to work with our API interfaces. Yes it can read from our H-Ext, but in reverse method, it is just stubborn to export the interfaces that H-Ext's requirement in order to work properly.
- Supportive C language expanson (Basically support C, C++, C#, etc Add-ons)
For time being, yes it is using static linking (Except for our loader system). However it will be slowly remove and using optimized ulitlity library we have create to replace it. The plugins can use this to reduce the extra functionality and ability to optimize without the standard library and CRT.







Bookmarks