[re-verse]

I'm having a problem with immunity not working.

Here is a sample from my admins.cfg and admin_groups.cfg

admins.cfg - a snippet
Admins
{
"re-Verse"
{
"auth" "steam"
"identity" "STEAM_#####3"
"group" "owners"
"immunity" "99"
}
"Dumb"
{
"auth" "steam"
"identity" "STEAM_######3"
"group" "owners"
"immunity" "95"
}
"Sweet Lew"
{
"auth" "steam"
"identity" "STEAM_###########"
"group" "shack"
}

"Maddog Delphi"
{
"auth" "steam"
"identity" "STEAM_#####"
"group" "maddog"
"immunity" "1"


and now a bit from groups

"maddog"
{
"flags" "bcfghijklm"
"immunity" "20" //low immunity value
}

}


Seems any mention of imminuty, in admingroups or admin is ignored, and anyone from any immunity level can slay/kick anyone from any other immunity level.

Any ideas? I'd love some help.

[BAILOPAN]

Can you give an example of a command and the two players it involves such that immunity breaks?

[BigBaller]

Im having same sort of problems.

Users are able to slay/beacon me. (seems to me the fun commands?) My immunity is set to 99 in the admins_simple.ini and their immunity levels are set to 2 in the admins_simple.ini.

I am on build 1904

[BAILOPAN]

Can you attach your file please?

[BigBaller]

Here are all my files pertaining to admin (that have changes from the base install)

[DaxMan]

Hi,
I have the same problem with immunity. It doesnt work.
Attaced you will find my cfg files.
Can somebody help me ?

/DaxMan

[BAILOPAN]

BigBaller: Please file a bug report and attach the same files. I don't see anything immediately wrong, it's probably better if this issue moves to our TODO list so it doesn't get lost in the forums.

[megatokyo]

Having the same problem... could just be my stupidity though

/**
 * USE THIS SECTION TO DECLARE DETAILED ADMIN PROPERTIES.
 *
 * Each admin should have its own "Admin" section, followed by a name.
 * The name does not have to be unique.
 *
 * Available properties: (Anything else is filtered as custom)
 *      "auth"          - REQUIRED - Auth method to use.  Built-in methods are:
 *                        "steam"  - Steam based authentication
 *                        "name"   - Name based authentication
 *                        "ip"    - IP based authentication
 *                        Anything else is treated as custom.
 *                     Note: Only one auth method is allowed per entry.
 *
 *      "identity"      - REQUIRED - Identification string, for example, a steamid or name.
 *                     Note: Only one identity is allowed per entry.
 *
 *      "password"      - Optional password to require.
 *      "group"         - Adds one group to the user's group table.
 *      "flags"         - Adds one or more flags to the user's permissions.
 *        "immunity"        - Sets the user's immunity level (0 = no immunity).
 *                          Immunity can be any value.  Admins with higher 
 *                          values cannot be targetted.  See sm_immunity_mode 
 *                          to tweak the rules.  Default value is 0.
 *
 * Example:
    "BAILOPAN"
    {
        "auth"            "steam"
        "identity"        "STEAM_0:0:194ya zfg894197"
        "flags"            "abcdef"
    }
 *
 */
Admins
{
    "Anubis1055"
    {
        "auth"            "steam"
        "identity"        "STEAM_xxxxxxxx"
        "flags"            "z"
        "immunity"        "0"
    }
    "Megatokyo"
    {
        "auth"            "steam"
        "identity"        "STEAM_xxxxxxxx"
        "flags"            "z"
        "immunity"        "99"
    }
}

[necrosect]

Bailopan (and BigBaller):
I might be wrong but hasn't he assigned to the "z" tag to both groups which would allow either to target the other regardless of immunity?

And the same goes for megatokyo you've assigned the "z" (read: root) tag to both admins meaning irrelevant of immunity they can target each other.

To get around this i would give for megatokyo's:
Anubis: "flags" "abcdefghijklmn"
remembering to include and custom one's you have defined (if any). This will give him complete access without overriding the immunity level.

[necrosect]

Sorry to double post but I think DaxMan has the same problem as well (hadn't noticed before).
I'm not sure if this is the standard way of doing it but I'd stick to using one of admins.cfg or admins_simple.ini to stop accidently assigning flags. Although in admin_groups.cfg you have correctly not assigned the "z" tag, you go on in admins.cfg to individually assign it to each of the admins which I think is giving you your problem