Now you're giving an example of what wouldn't happen (atleast if you knew what this addon entails). You're suggesting that if someone finds a script that uses the $isregistered alias, and limits abilities of the script, that noone can use mirc anymore. That's not true. The alias would be geared towards scripts not "plain 'ol mirc". When you said there was nothing you can do in your example, you were entirly wrong. You could have told them that they can use the original mirc, that most likely doesnt have anything comparing the $isregistered, but just the introduction dialog.
All you're doing is creating ficticious dialog that would never happen because you dont want to see it being added.
I said it before, if you are al worried that this is going to lead to "more cracking" or less users on mirc--you're wrong. People that crack mirc, again, dont give two sh**s about wheter is was or wasn't already cracked before they apply a patch. They aren't going to "only crack it if it hasn't been already". Someone please give me an example where it would need to check first. The only time you have cracks (or majority) are:
A) You downloaded a script with the .exe included, and apon running it it installs the crack (note the exe was not previously yours, so you didn't "register" it.)
B) You download it when you have your own version, haven't registered, and apply it to the mirc installation you have.
It's not like your going to register mirc, go out and download a patch, then apply it to your already-registered-version of mirc.
Secondly you all are suggesting that user counts using mirc will drop.. That's not true. The only thing that might "drop" are the amount of people using scripted mircs, not the original. The original would remain not having someone where in the scripts file the code "if (!$isRegistered) /echo You are not registered, you cannot use this program".
I've done typing for now, when I wake up mire i'm sure i'll have a rebuttle to what you all have to say about why it shouldn't be added..
