[Bacardi]

Then, with admins.cfg you can add multiple groups to one player.

With admin_simple.ini, you can give only one group, so you need create "whole groups" with all overrides.

But use either.

*edit
admin_simple.ini

//
// READ THIS CAREFULLY! SEE BOTTOM FOR EXAMPLES
//
// For each admin, you need three settings:
//  "identity"        "permissions"        "password"
//
// For the Identity, you can use a SteamID or Name.  To use an IP address, prepend a ! character.
// For the Permissions, you can use a flag string and an optional password.
//
// PERMISSIONS:
//  Flag definitions are in "admin_levels.cfg"
//  You can combine flags into a string like this:
//  "abcdefgh"
//
//  If you want to specify a group instead of a flag, use an @ symbol.  Example:
//  "@Full Admins"
//
//    You can also specify immunity values.  Two examples:
//    "83:abcdefgh"            //Immunity is 83, flags are abcdefgh
//    "6:@Full Admins"        //Immunity is 6, group is "Full Admins"
//
//    Immunity values can be any number.  An admin cannot target an admin with 
//    a higher access value (see sm_immunity_mode to tweak the rules).  Default 
//  immunity value is 0 (no immunity).
//
// PASSWORDS:
//  Passwords are generally not needed unless you have name-based authentication.
//  In this case, admins must type this in their console:
//
//   setinfo "KEY" "PASSWORD"
//
//  Where KEY is the "PassInfoVar" setting in your core.cfg file, and "PASSWORD"
//  is their password.  With name based authentication, this must be done before
//  changing names or connecting.  Otherwise, SourceMod will automatically detect
//  the password being set.
//
////////////////////////////////
// Examples: (do not put // in front of real lines, as // means 'comment')
//
//   "STEAM_0:1:16"        "bce"                //generic, kick, unban for this steam ID, no immunity
//   "!127.0.0.1"        "99:z"                //all permissions for this ip, immunity value is 99
//   "BAILOPAN"            "abc"    "Gab3n"        //name BAILOPAN, password "Gab3n": gets reservation, generic, kick
//
////////////////////////////////
"STEAM_0:1:16"        "@Group 1" // somebody

[Kjaer]

Originally Posted by Excel Gamers Currently nothing as I have not really used sourcebans and configured it yet.

If you're using sourcebans you're going to have to delete the admin_simple.ini contents. If you encounter problems with sourcebans with assigning groups and admins you'll have to create the groups through the webpanel and assign them that way as well.

[Excel Gamers]

I have finally configured it all. In the sourcebans.cfg I disabled server admin override so that I can do it how you have shown me. Thank you very much for all your help.

[sinblaster]

BACARDI whats the benifit of adding overides to admin_groups instead of admin_overides?

[Bacardi]

Originally Posted by sinblaster BACARDI whats the benifit of adding overides to admin_groups instead of admin_overides?

You know what privilege/commands you give for lower admins by admin group+overrides, you need less use admin flags, or without admin flags.

Admin flag can hold lot of commands, depend what plugins you have installed on server.
Example "f" (slay) = sm_slap, sm_slay, sm_burn, sm_beacon, sm_freeze, sm_drug etc. etc.
- (and immunities, if could only plugin developers start use CheckCommandAccess instead admin flag bits)


You could give only few command instead all or give adminflag at all.
Or disable few commands even you give admin flag.

Groups
{
 //-------- SKIPPING THIS PART ---------
    "Group x"
    {
        Overrides
        {
            "sm_slay"    "deny"    // No slay
            "sm_slap"    "deny"    // No slap
        }
        "flags"    "bf"
    }
}

And no, there is nothing wrong use admin_overrides.cfg if you know what you are doing.
- Override specific commands to one adminflag and give player.

Use method what feels easier.
Can't really explain well these because my bad english. Only for testing these overrides you get better answers.

[daad]

Hello, I am working with three HL2DM servers and am looking to switch from Mani to Sourcemod for my admins. I currently run sourcemod with Mani so that I can run some sm only plugins. I wish to limit my lower admins to kick,ban (by steam id only) and mapchange only with no immunity. I and the other server owner run sourcemod with 99:z as a default. We use Mani for everyone else right now. It looks like I have to give generic flag to all, however that gives other player abuse settings (slay,burn,etc...) I am not a coder or scripter but can follow examples. I hope I have posted in the proper place can can get some help. I saw this thread being fresh so started here. Tnx for anyones help, Daad