in mirc 6.12 these commands worked fine, but look at the output in mirc 6.14...

reload -rs47 $+(",$mircdirsystem\ppro\pp305.mrc,")

* Reloaded script 'C:\mIRC Power Pack\system\ppro\pp305.mrc'

unload -rs $+(",$mircdirsystem\ppro\pp305.mrc,")

* /unload: no such file 'C:\mIRC'
* Unloaded script 'C:\mIRC Power Pack\system\ppro\pp305.mrc'

when you manually run /unload it seems to work even though it initially gives you an error.

but if you have /unload commands triggering every x seconds when using timers, mirc constantly spams error messages the whole time... this causes horrible lag in mirc if the timer is less than 5 secs. the script is basically usesless because it can't get past the errors.

Nothing wrong with /unload here. You may have an /unload alias: type
//!echo > $isalias(unload).fname
to find it

i don't have an /unload alias, which i also confirmed with the command you sent.

the script i am unloading in my example is located in a folder with spaces:

C:\mIRC Power Pack\system\ppro\pp305.mrc

/unload works fine in mirc 6.12, but not in mirc 6.14.

can anyone confirm this problem?

/unload bug example:

put this in your normal remotes file...

on *:load: {
echo -s Loaded!
}
on *:unload: {
echo -s Unloaded!
}
alias unloadtest {
unload -rs $+(",$mircdirhaha\test.mrc,")
}

save changes.

now...

manually create this full path, and an empy test script named test.mrc:

c:\m i r c 6 1 4\haha\test.mrc

notice the spaces in the name: m i r c 6 1 4 (single spaces only).

so, haha is a subfolder of mirc, and we are loading test.mrc from the haha folder.

just create an empty text file and call it test.mrc, then put it in the haha folder.

now manually load test.mrc (/load or file -> load)

run this command: /unloadtest

output on the first run: * Unloaded script 'C:\m i r c 6 1 4\haha\test.mrc'

run this command a second time: /unloadtest

output on ALL subsequent runs: * /unload: no such file 'C:\m i r c 6 1 4\haha\test.mrc'

you shouldn't have to check to see if a script is loaded before you unload it, that was never a condition previously. but even if that is the case now, the error isn't reporting that it isn't loaded, it is reporting that there is no such file.

i've only had problems when calling unload in some file, which, in the on :unload:, loaded some file, which in the on :load:, unloaded the first file. it would then give the '* /unload: no such file" error.

it turns out that once a script is unloaded, you can't run /unload again or you will constantly get the '* /unload: no such file" error.

i never had to do this before, but now, any time i want to unload a script, i first have to test to see if it is loaded before i attempt to unload it.

the only way i've found to determine if a script is loaded is to edit the script, find a unique alias inside, like /example - then test it with: $isalias(example). if that comes back $true, only then can i safely run /unload.

what is that all about?

this test was never required before. you could run /unload a million times without one error.

even worse is the fact that the error message is totally incorrect: 'no such file' - which makes you think the file isn't even there. a better error message would be something like: 'no such script loaded'.

if this is not a bug and instead the way they want /unload to work, then you shouldn't have to dig through scripts trying to find an alias to test, they should give you a new idntifier such as $isloaded() --- or something.

and how would you go about testing $isalias() in a script that has no aliases at all (such as scripts that handle events and/or raws only)?

if $script(file) { unload -rs "file" }

helpful, thank you.

it still doesn't make sense that you have to test before unloading now...