Thanks this is due to /ban not being consistent in checking whether you are an op/oper. I have changed this behaviour for the following commands: /ban, /pop, /omsg, /onotice, /wallop. These will now check whether you are either an op or an oper.
The auto-op/voice/protect features, which trigger only if you are an op, could also be changed in the same way - however I am not sure if that would be appropriate.
Also, the @ prefix for remote events, which triggers only if you are an op, could also be made to trigger if you are an oper - however, again, I am not sure if that would be appropriate.
Ps. The website was experiencing some issues yesterday - it looks like it is back to normal :-)
