1. A way to split the script in many smaller files instead of keeping it all in one huge file.
I have a class that is used by the main script and I'd like to keep this class in a separate file, but if I do this:
<script>myclass.nut</script>
<script>myscript.nut</script>
the main script refuses to work (specifically the functions that are using this class). It looks like scripts doesn't 'see' each other.
You can split scripts over multiple files using:
dofile( "Script.nut" );
An example would be:
function onScriptLoad( )
{
Print( "Example Script" );
dofile( "IRC.nut" );
}
2. Ability to connect squirrel scripts to remote servers - the same principle as it is now with mirc scripts:
[ Location A: Some computer + Script X ] ----> [ Location B: Server (+ optional Script Y) ]
I know about the .dll for mirc and this server but... that's not for squirrel :p
I think your missing the whole point, the idea in adding Squirrel to the server is for server-side scripting.
3. Currently not so important in my eyes: loading/unloading scripts dynamically (without changing server.conf).
Like, if today is wednesday (or the weather is rainy) i'm going to use Script1, but on the other days - Script2.
EDIT: With this it will be possible to reload scripts without restarting the server.
You can use "load_script <name>", "unload_script <name>" and finally "reload_scripts" (without quotes) all 3 commands you type directly like you do with "onConsoleInput" commands.
Hopefully i've answered most of your questions correctly.
- AdTec_224