As far as I know, mOTFv hooks into winsock's send() and recv() functions, using a rather generic technique. This means such a DLL will be mIRC-version independent, but if send() and recv() are used to send/receive encrypted text (which is the case for SSL connections of course), the technique will fail.
On the other hand, my DLL hooks into functions deep inside mIRC, at a place where there is no difference between messages sent as plain text, and messages sent over SSL. This technique is far from generic; it needs specific offsets into the mIRC binary, and that makes it so version-dependent.
at any rate, that sounds like a nice idea including a few API calls in your dll.
Okay, I'll do that then - I'll send you a message when it's done.
