Well... apart from the fact that you\'re missing a closing } at the end of it... most commands won\'t work if your nick isn\'t set up as a bot admin, but you give no indication of HOW to set up your nick as a bot admin. Even just to use the commands command you need to have your nick set up as an op... and again, you give no indication of how to set up your nick as an op (except an admin command which is inaccessible if you don\'t know how to set up your nick as an admin). Some of the commands listed incommands are admin-only (most of them, in fact), which defeats the point of giving ops a command listing (which doesn\'t specify which commands are admin-only); admin nicks can\'t get a command listing (it\'s op-only). Some commands are not listed (op,halfop, voice); adding or removing somebody as an op/halfop/voice does nothing (there\'s no on join event to automatically op/halfop/voice them).say will only let you say one word (it should be $$2- rather than $$2, also you only need $2- because since it triggers on \"say *\" it\'ll not trigger if somebody simply says \"say\", it\'ll want a space and something after that to trigger). You have an extra $+ in the kickban line. There\'s still the inherent insecurity of granting bot control by nick that Cypher87 mentioned, plus using a variable for each nick to store who is what you\'ll have the variables section full of variables after a bit... I\'d suggest either using a single variable (ie. %admins holding all admin nicks) and tokens, or access levels (which would be safer as well if you match it by ident@host rather than by nick). And finally, as I\'ve already mentioned, I dislike the use of as a command prefix, because people with non-English keyboards will NOT be able to type it directly, they\'ll need to copypaste or do keyboard-acrobatics (I forget the alt+numbers combination, I copypasted it)... you really should use the more common ! or . as a command prefix, there\'s a reason they\'re widely used :)