I have a problem with that rule simply because I don't believe it's specific enough. While I have thought about abusing it, I haven't. See, technically, declaring a constant is a single command. However, constants can be declared like so...
#Constant MyCommand : Do : Print "Hello World" : Loop
Then, just use
MyCommand anywhere you like and it will do all the above. So, since declaring a constant is "a single command", one could, in theory, put limitless commands as part of the #Constant declaration. Like so...
#Constant MyCommand : Command 1 : Command 2 : Command 3 :...: Command n
Still technically only a single command (because everything after the #Constant becomes the constant), but I think clearly not within the intention of the rules. I even had concerns using this technique for several commands in order to squeeze them in, but on another line that was "already full". So, pre-compiled, the code was "legal" (even in the "intention of the rules" sense). However, once compiled, the #Constant did it's find/replace thingy, and there were lines longer than 25 commands (and other lines with suddenly fewer commands). I think some would say that's a loop-hole, and I wouldn't outright disagree (but I would defend myself by stating it has never been made clear). Inversely, that kind of ruling could lead to another rules quandry. After compile, the Constant declaration is "remmed out" and "by the rules", remmed out lines are not counted towards the 20 lines.
So - anyway - that's why I don't like that rule so much.

Open MMORPG: It's your game!