Forums Scripts & Popups Help in preventing Unloading of a remote script.

I am trying to write code to prevent the unloading of a remote script where I have core functions of my over all script located can anyone tell me why this dosnt work and help with a fix.

on *:UNLOAD: {
if ($script == $mircdir\Core\Core.mrc) { echo -a 4 SYSTEM ERROR YOU CAN NOT REMOVE CORE }
load -rs $mircdirCore\Core.mrc
}

Regarding the reason your code isn't working, is due to the discrepenancy between the script name that is being recognized under $script and the script name used in the load command.

Try this version


I left the $mircdir out of the code purposely, so that the unload event will work and reload the correct file as long as it's in the Core sub-directory.. This means that someone could put it in C:\WINDOWS\CORE and it would still work.

P.S.: You had the 4 for the colour in the echo in the wrong location.

I tried the verison you gave below and the results where the same .

I typed this in status /unload -rs Core.mrc and the script was unloaded with no messages.

* Unloaded script 'Core.mrc'

I made this for someone on here some time ago, just paste it at the beginning of each file you want to protect.

AFAIK $script is always an absolute pathname so it could never equal "Core\Core.mrc" no matter where it was. Of course there's no need to be checking $script anyway since the UNLOAD event will only trigger for the script it's in.

The real question is whether a scripter should unconditionally prevent a script from being unloaded. By reloading a script on unload it's effectively impossible to uninstall or otherwise remove that script short of disabling remotes first or deleting it from mirc.ini prior to starting mIRC. Not exactly user-friendly. At the very most it should provide a $input() to ask if the user really intended to remove the script (although even that seems redundant to me - of course they want to remove it, that's why they're /unload'ing it).

I don't believe it's possible to directly load/reload a script through it's UNLOAD event. It would seem to be an intentional design choice on Khaled's part. If absolutely necessary it can be done with timers or by alias'ing the /unload command itself but it's a messy way to do things and as I said above it's just bad practice in general to stop a script from being unloaded. The OP should really ask himself if he wants to piss off his users like that.

Actually its not that I wish to prevent the script from being unloaded at all, The reason behind this particular Remote from unloading is due to the affect it has on other Remotes. Since it is the main (Core) file for the entire script. It holds all alias and script basic Functions the rest of the remotes can be removed from the script using a dialog, this is mainly a script designed for those with limited or no IRC experience on the server which I frequent.

I still would agree with starbucks_mafia. Preventing a script from being unloaded isn't a good thing. If you need to do that, then do as he mentioned and use an input to verify that the user wants to remove it. You can put a note right in there stating that removing it will prevent all of your other scripts from working properly.

Keep in mind that those inexperienced users may want to remove your script and your automatic reload will prevent them from doing so and they won't know how to get rid of it.

One option you could consider would be to have the yes/no dialog as shown above. It would tell the user that unloading will cause problems, etc. If the user chooses 'no' (to unloading) then the script is reloaded for them. If the user chooses 'yes' (to unloading), your script could automatically unload all related scripts that would fail to work without that core script file.



-genius_at_work