Forums Bug Reports mIRC gets confused over CTCP parameters.

If you initiate a CTCP request with a parameter that's the same as the CTCP request, mIRC can't tell the difference between that a CTCP request with no parameter at all when using $1.

CTCP sends queries in all-capitals, so the most I can do is use if ($1 === REQUEST) {} and hope the user doesn't send a parameter that's also all-capitals.
Tried that. It didn't work.

I don't understand, if there is no parameter, only $1 will be filled and you can check that $2 is $null, or that $0 is more than 1 to know that. What's the bug exactly? Can you give a code which reproduces the issue?

$1 is the CTCP event name in a CTCP event, not the first parameter. The first "parameter" of a CTCP event would actually be $2, not $1.

for example, in a CTCP PING:

//ctcp $me PING 1234567

$1 = PING
$2 = 1234567

If there is "no parameter", then $2 will be $null, as pointed out.