You may only need some scripts on certain networks.
if ($network == networkname) { do stuff }
think if u had 20 scripts for 1 network then 20 for another etc etc would be a pain of keeping track of which network the script was loaded for.
Why would you have 20 scripts for one network, and 20 for another? I just can't see the point of that. Infact, why do you even need to unload it at all? If you use something like if ($network == networkname) then you should be able to get things to only execute on one network, then you could keep them loaded all the time and connect as usual. As scripts do not do anything when mIRC is closed, loaded or unloaded, I don't see why you'd need to unload scripts on disconnect. CPU usage shouldn't be an issue really...
To separate the connect/disconnect events for each network, just put them in different remote files and name the .mrc files 'NetworkName'. You can then easily access them from the 'View' menu of
ALT+R.
As
this post says:
"Would it be easy to write a script for my idea?
If it's something that is very easy to do with scripts, chances are it won't be built into mIRC. (This isn't always the case, but should be considered when posting your idea.)"My 2 cents.
Regards,