Why Stealth.dll?

 In the past I have seen various different types of individuals attempting to either change or disable mIRCs CTCP version reply. These individuals have attempted the most ridiculous of things, such as the use of sockets. There are some who have succeeded using mIRC scripting itself by using mIRCs debug capabilities/aliases. While using mIRCs own capabilities to disable this CTCP version reply, you are processing unnecessary information while just trying to disable just one thing (i.e. processing all RAW events when you just want to catch that VERSION).
 The method that this DLL uses is simple. In fact, its so simple that even a caveman could do it. Why has nobody ever done it this way before? I am not sure, the entire process took about 60 seconds to find out what I needed, and 3 minutes to make the initial rough draft of the DLL.

How does Stealth.dll disable mIRCs version reply?

 mIRC has a hardcoded CTCP version reply. Lets look at this pseudo code:
    if (stricmp(string, VERSION)==0) Socket(User, mIRC %s Khaled Mardam-Bey);

 So Stealth changes it to something like this:

    if (stricmp(string,        )==0) Socket(User, mIRC %s Khaled Mardam-Bey);

 Basically mIRCs hardcoded reply is nullified and only the one that is scripted will be the only one used. Simple, no? The DLL does not stay loaded; when its first loaded it does what it needs to do, and its then unloaded automatically.

Why disable mIRC's version reply?

 Why are you downloading this DLL? Me personally, I ignore all CTCP requests so it does not make a difference. Stealth started when I saw all the ridiculous attempts that there were out there. I mean really, a dll with sockets to disable the reply, are you serious?
 
 
 
Why release the source code?

 Because it's so easy that even a caveman could do it. On a serious note, it's being released so other individuals can learn how these type of things are done.
 
 
Those other folks who made DLLs that utilized sockets:
 
 You are doing it wrong. 
 