Ok, I didn't test this because I don't have time right now... but what happens when someone has a script that /sets a variable and your alias sets it as a different variable name and then the user's script tries to check it later? It would be checking the wrong variable. Also, what happens when a script sets a variable multiple times? Will this just keep making more and more copies of the variable rather than changing it?
As I said, I didn't test it, so maybe these problems are already addressed by the alias. However, if they aren't, then this alias is likely to cause more problems for the "naive" user who runs someone else's script that isn't designed to work hand-in-hand with your alias and just assumes that /set works the normal way.
Making copies of the variable is stoppable if you specify the "-o" when you /set, if the -o is there the script will over-write the variable instead. It's designed to prevent mal functionality of a pre scripted mirc client, if an user tries to change something without knowing what they're doing.
A downside would be the obligatory usage of -o by the author, every time you set variables and do not wish to create copies.
But it's a small price to pay for more security.
I made this animation so you can understand what it's function is:
LinkI appreciate skepticism, it motivates me. I hope the gif is at least understandable.
