back on topic:
//if ($1 == (!game || $3)) echo -a what?
is already ambiguous in mIRC it doesn't have to behave as
if ($1 == [ !game || $3 ] )
sort of speaking.
Well it doesn't
have to, it would just be a bad idea to change the semantics of common operators by making || behave like some kind of list-creation operator and == behave like a contains/is-subset operator in certain circumstances. It's technically feasible of course for mIRC to parse and interpret things any way it chooses. But it would be ugly as sin and confusing to anyone who's ever written anything in any other programming language or who simply understands and expects || and == to remain consistent throughout the language.
