I did not say it "works" at all...quite the opposite, in fact, and I explained why. Here's are better examples.
- Suppose you wrote to $mircini and added another filename to the end of [rfiles]. That was very well done! Good job. However, does that mean that you did the equivalent of /load -rs filename.mrc? No, not at all. When mIRC exits, it will rewrite the $mircini file with its current settings, blowing away your changed rfiles section anyway. And obviously, writing to that section is not at all the same thing as loading a remote script file.
- Suppose you are a beta tester for someone's script. They send you a file, you save it directly into your mIRC directory where you keep such files, choosing to overwrite the previous version with the new version. All's well so far, but why doesn't the new script work? You complain to the script's author and he tells you to /unload the old one first, then load the new one. But you find that when you /unload the current file, it overwrites the new copy with the old version, so you have to ask the author to send it again. The author gets all pissed off that you can't manage your files very well and strikes you from his beta list, putting you on his permanent UtterIgnore list.
Well, perhaps that wasn't such a good example; I should have picked an example where the author was a bit more PATIENT with his beta testers or who should have learned the value of the /reload command!!! It doesn't matter, it probably wasn't a very good script anyway. - When you make changes to Windows' ini files, it asks you to reboot your computer to make the changes active.
Ok, that's a bad example too. mIRC doesn't require you to reboot your computer if you want to change your nick, so it's not much like Windows' registry management at all. - If you
Oh nevermind. I never said it worked in v6.03.
