The library will use the SuperLib imported by GS if the GS import SuperLib before LibServerGS.
Yes, but also import SuperLib if it cannot find it, that's the problem.
The library use some methods from SuperLib and I think it is sound to not inline those as that defeats the main purpose of SuperLib - only fix the same bug once.
This makes sense for big project you handle, not for a library that should have its code frozen.
If i link my program with the library, and i use SuperLib myself, it's great, the library will use the one from the program, so all its functions are now running the update version of SuperLib my program is using. No problemo.
But if i link a program that doesn't use SuperLib : now the library import SuperLib version 36, and content download will always get v36 as dependency : no more update code, and a dependency version that will get old soon.
So, in order to keep an update SuperLib version for this lib for a program that don't use SuperLib, you will be force to update the library too.
All this for what? Having latest SuperLib version in use, but the program itself still don't use it.
I agree Story makes sense for admin port tools compatibility that are using it, but that could be done by the GS, not handle by the lib itself.
But i could live with extra symbol and handling of Story, but SuperLib trouble me more.
If i build a GS with SuperLib, it will be a great addition.
But if i build a GS without SuperLib, the addition of SuperLib will grant nothing to my program, i just see that as adding bloat for no reason (not that SuperLib is bloat for me, but it's a huge library, and if you don't use it, any extra lines that have no usage are just bloat).
That lib is great, as anyone making a GS need just to import it and add the event handling and admin tools have access to GS API.
Even better, your GS can add some functions for the admin port and expose them too (like a function that return stats...).
That library should be use by all GS authors : it's a little addition in their code, for a great benefit : the lib itself gave high capability to server owner. Something any GS author should expect their GS to run on.
But "the little addition" for a GS that doesn't use SuperLib is no more something i would see as "little".
It's your library ; your work, if you really want link it with SuperLib, fine. It will be a great library for GS using SuperLib. I think it could have been the same for GS that doesn't use SuperLib. Making it a mandatory library for any GS.