Just want to try and get an idea of how many have actually added custom admin groups at this point to their bots.

Using the following groups atm on my bots
Administrator
Moderator
Raidleader

Raidleader, raidmoderator, spammer (to spam other friendly orgs if we plan some raids and want them join us).

I haven't yet, but I plan on adding a group called Callers when I get around to writing a somewhat more advanced target managment type module.

i for one removed super admin from the bot and changed code so that super admin commands can be run only by $super_admin['name'] guys, admins hardcoded. better this way if you want to have some level of control over who gets super admin or not.

i have.  although i couldn't seem to add the group via chat (can delete group without problem,) i manually added a generals group, which i assign more control over the bot than a normal member, yet less than an admin.  Also edited the blacklist mod to a point where any member can add, but only generals and higher can delete.  I can imagine other good uses for this in the future.

I originally used the raidleader group for this, but !online produced the RAIDLEADER tag next to names where, well there are no raidleaders in org bot.  Creating a group generals fixed this.

Somewhere though, when the bot restarts, even though i deleted the RL group, it gets put back into the admin_group list, and appears (blank due to no members) when viewing !admin.  I am assuming it's one of the mods that has a "if doesn't exist, create" line.  Would be nice to prevent that, but it's not a big deal.

With custom rights management in 0.3/0.4 i'm currently contemplating just ditching custom groups altogether and allowing people to rename the access levels as they see fit, although guest, member and owner will be unchanged.