This may or may not be regarded as an actual bug, but please bear with me.
If I am pm'ing in a query window while running my XDCC server (effectively the same as /msg'ing back and forth) and someone says xdcc <anything>, it closes the query window (very annoying) and proceeds to spit it back at them like this:
<user1> xdcc blah
[query window closes and script sends this msg]
<user2> Unrecognized command blah. Type "/msg user2 XDCC Help" for help.
I understand this is the way it is designed to work, in a channel where you want to use /msg trigggers the window closing would be a good thing. But throw into the mix the autoresponder, and it suddenly becomes an annoyance *and* a vulnerability. Obviously this is not something you ordinarily have to worry about pm'ing with friends (as anyone you could call friend wouldn't purposely force your window shut), but I did happen upon it. Is there a way to disallow using /msg for XDCC? Is there a way to disable all xdcc autoresponders?
I know the xdcc server with /msg trigger has been a much requested feature for quite a while before being built in, but I actually want it turned off so I don't get my window closed upon the first word being xdcc, and I don't want that autoresponder, at least for /msg. Also, this might be considered a slight vulnerability, as a friend and I (just the two of us mind) were able to solicit a flood from my invision script by repeatedly barraging it in query windows with xdcc blah - the XDCC help response appeared to have little or no delay between responses so it was easily floodable. So, ultimately my question is whether the /msg xdcc server functionality can be turned off, or tweaked to the point that the window is not closed and eliminating the /msg xdcc autoresponder or buffering the time between the responses. Thank you for your time and consideration, and thank you for such a wonderful script!
