You can load scripts into a different namespace or interpreter if you want to avoid name conflicts, but the scripts will have to be written to handle their new environment.
The thing is that i want to use the script as a service for several teams on quakenet. So every script should have their own settings, and i want to avoid installing a new eggdrop for every team that will use it.
Its like the warmanager script, but much more functions.
So i dunno whats the best. To make a new namespace for each script, or to make it dynamic to support several channels/settings.
Making a single script support several channels would of course be much better. Less hassle dealing with binds etc. (some binds are not stackable, so the script loaded last would "win")
But that doesn't mean using your own namespace is a bad idea.