[kfskilljoy]

Hello everyone i am having a problem with the admin_overrides.cfg. I have custom flags that i am using and when i try to add the flag to commands my admins on the server lose the ability to use that command and so does the custom flag.

Here is how the file looks :

Overrides
{
/**
* By default, commands are registered with three pieces of information:
* 1)Command Name (for example, "csdm_enable")
* 2)Command Group Name (for example, "CSDM")
* 3)Command Level (for example, "changemap")
*
* You can override the default flags assigned to individual commands or command groups in this way.
* To override a group, use the "@" character before the name. Example:
* Examples:
* "@CSDM" "b" // Override the CSDM group to 'b' flag
* "csdm_enable" "bgi" // Override the csdm_enable command to 'bgi' flags
*
* Note that for overrides, order is important. In the above example, csdm_enable overwrites
* any setting that csdm_enable previously had.
*
* You can make a command completely public by using an empty flag string.
*/

"sm_noclip" "bs"
"sm_fia" "bs"
"sm_god" "bs"
"sm_buddha" "bs"
"sm_powerplay" "bs"
"sm_pp" "bs"
"sm_colorize" "bs"
"sm_csay" "b"
"sm_msay" "b"
"sm_smite" "b"
"sm_grab" "b"
"sm_tsay" "b"
"sm_hsay" "b"
"sm_goto" "b"
"sm_tele" "b"
"sm_mute" "b"
"sm_gag" "b"
"sm_setclass" "bs"
"sm_unmute" "b"
"sm_ungag" "b"
"sm_behhh" "b"
"sm_horseman" "b"
"sm_evilpimpslap" "bs"
"sm_evilglow" "bs"
"sm_evilbeam" "bs"
"sm_evilrocket" "bs"

}

[Powerlord]

Just to be clear, you know that "sm_evilbeam" "bs" would require a user to have both b and s flags to use sm_evilbeam?

If you need more fine-grained controls, I highly suggest creating groups and assigning overrides to the groups themselves. Do note that overrides for groups are in allow/deny format rather than by admin flag.

[kfskilljoy]

Ok ill make a group thank you.

[kfskilljoy]

Ok i tried making it a group but i still got that i dont have access to the command when i set myself as that flag.

"Supporter"
{
"flags" "s"
"immunity" "3"
"Overrides"
{
"sm_noclip" "allow"
"sm_god" "allow"
"sm_buddha" "allow"
"sm_fia" "allow"
"sm_powerplay" "allow"
"sm_colorize" "allow"
"sm_goto" "allow"
"sm_tele" "allow"
"sm_evilglow" "allow"
}
}

[Powerlord]

Originally Posted by kfskilljoy Ok i tried making it a group but i still got that i dont have access to the command when i set myself as that flag. "Supporter" { "flags" "s" "immunity" "3" "Overrides" { "sm_noclip" "allow" "sm_god" "allow" "sm_buddha" "allow" "sm_fia" "allow" "sm_powerplay" "allow" "sm_colorize" "allow" "sm_goto" "allow" "sm_tele" "allow" "sm_evilglow" "allow" } }

Groups aren't assigned by flag, but rather by the admin entry in admins_simple.ini or admins.cfg.

In admins_simple.ini, it'd look like this:

"STEAM:BLAH" "@Supporter"

In admins.cfg, it'd look like this:

The group above MUST have a @ before it or it'll interpret them as flags.

    "Powerlord"
    {
        "auth" "steam"
        "identity" "STEAM:BLAH"
        "flags" "b"
        "group" "Supporter"
    }

You'll note that unlike admins_simple, I can assign myself flags and a group in admins.cfg. In fact, you can have more than one group per admin in admins.cfg.

[kfskilljoy]

I got it fixed. Thanks for the help.