This change in evaluation behaviour is related to the TABCOMP fix in mIRC 6.3x. It was simply using the result of the evaluation which in some cases may be $null. I will change the evaluation behaviour back in the next version so that it leaves the item intact if it evaluates to $null.