Author Topic: Have you added more admin groups to your bot? (Read 31074 times)

Khalem · « **on:** October 23, 2005, 06:35:20 pm »

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

Alreadythere · « **Reply #1 on:** October 23, 2005, 09:03:24 pm »

Voted "RL only", but not sure if I won't go around and add some more admin groups in our org bot. Got to see if I need more then 3 levels of access rights really.

Derroylo · « **Reply #2 on:** October 23, 2005, 10:55:07 pm »

Using the following groups atm on my bots
Administrator
Moderator
Raidleader

Nesi · « **Reply #3 on:** November 27, 2005, 12:30:52 pm »

got:
Raidleader (for the obvious:))
Pointsleader (So non SA's can add points)
Trackbotuser (wouldent you like to know hehe)

kuznechik · « **Reply #4 on:** November 27, 2005, 01:22:05 pm »

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

Wanuarmi · « **Reply #5 on:** November 27, 2005, 11:18:01 pm »

I added raidleader as "leader" and had to modify alot of scripts :/

Glarawyn · « **Reply #6 on:** December 21, 2005, 08:40:42 pm »

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.

Glarawyn · « **Reply #7 on:** January 18, 2006, 06:46:53 pm »

Added another group...one player in the org needed access to my shout command but nothing else, so created a group for him.

axl · « **Reply #8 on:** April 21, 2006, 02:00:38 pm »

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.

jjones666 · « **Reply #9 on:** September 05, 2006, 05:26:17 pm »

Just to bump this one, my timer module sends to specific members of admin groups (ie, all from group Zodsnet), the other admin groups I created (Hellcom and HCadmin) are useful to see online/offline status of other people having access to the bot (using modified !admin list).

Cheers,

-jj-

Dracutza · « **Reply #10 on:** November 25, 2006, 10:37:45 am »

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.

Khalem · « **Reply #11 on:** November 25, 2006, 11:55:51 am »

How admin stuff works is one of the big todo's i'm still working on for the next major release.

The reason raidleader gets readded is that on startup, the bot makes sure that the "hard coded" admin levels of admin, superadmin and raidleader are there by deleting and reinserting those 3.

In 0.4 custom and hard coded levels will entirely separated, however this also means it will be impossible to delete ranks you don't use, although i will probably make empty ranks not show up in the list.

Khalem · « **Reply #12 on:** November 25, 2006, 10:16:16 pm »

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.