AlliedModders Wiki - User contributions [en]

Adding Admins (SourceMod)

2009-03-18T21:53:08Z

Recon0: /* Detailed Admins */

__FORCETOC__
SourceMod has as very detailed and flexible administration system, and it can be quite daunting to users. To simplify things, there are a number of "flags" which specify generic permissions administrators can have.

Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file.

SourceMod provides three methods of authentication by default:
*''Steam ID'' (unique to a Steam account)
*''IP Address'' (semi-unique to a given computer, better for LANs)
*''Name'' (requires a password)

=Quick Start=
On the server, open cstrike/addons/sourcemod/configs/admins_simple.ini

In a new line, add the following, replacing yoursteamid (use your client's console '''status''' command to retrieve your steamid - formatted as STEAM_n:o:p)

'''"yoursteamid" "99:z"'''

Save

Restart Server

Connect to Server with Client

Enter sm_admin into console, and return to game. You should see admin menu.

=Levels=
First, let's quickly run down the provided levels:
:{| cellpadding="5"
|- class="t2th"
| Name
| Flag
| Purpose
|- class="t2td"
| reservation
| a
| Reserved slot access.
|- class="t2td"
| generic
| b
| Generic admin; required for admins.
|- class="t2td"
| kick
| c
| Kick other players.
|- class="t2td"
| ban
| d
| Ban other players.
|- class="t2td"
| unban
| e
| Remove bans.
|- class="t2td"
| slay
| f
| Slay/harm other players.
|- class="t2td"
| changemap
| g
| Change the map or major gameplay features.
|- class="t2td"
| cvar
| h
| Change most cvars.
|- class="t2td"
| config
| i
| Execute config files.
|- class="t2td"
| chat
| j
| Special chat privileges.
|- class="t2td"
| vote
| k
| Start or create votes.
|- class="t2td"
| password
| l
| Set a password on the server.
|- class="t2td"
| rcon
| m
| Use RCON commands.
|- class="t2td"
| cheats
| n
| Change sv_cheats or use cheating commands.
|- class="t2td"
| root
| z
| Magically enables all flags.
|}

=Immunity=
In SourceMod, immunity is a flexible system based on ''immunity levels''. Every admin can have an arbitrary immunity value assigned to them. Whether an admin can target another admin depends on who has a higher immunity value.

For example, say Admin #1 has an immunity level of "3" and Admin #2 has an immunity level of "10." Admin #2 can target Admin #1, but Admin #1 cannot target Admin #2. The numbers are completely arbitrary, and they can be any number equal to or higher than 0. Note that 0 always implies no immunity.

By default, admins with the same immunity value can target each other. This can be changed via <tt>sm_immunity_mode</tt> in <tt>cfg/sourcemod.cfg</tt>.

=Passwords=
For passwords to work, the server administrator must change the "PassInfoVar" line in <tt>addons/sourcemod/configs/core.cfg</tt>. For example:
<pre>"PassInfoVar" "_sm1337"</pre>

Next, if an admin has a password, he or she must set the password via the ''setinfo'' command in the client console. For example, using the examples above, <tt>BAILOPAN</tt> would need to type:
<pre>setinfo "_sm1337" "Gab3n"</pre>

To automate this upon connecting to a server, you can create an "autoexec.cfg" file in your client <tt>cstrike</tt> folder. This will be located under <tt>SteamApps\ACCOUNT\Counter-Strike Source\cstrike\cfg</tt>. For example:
*<tt>C:\program files\steam\steamapps\bailopan\counter-strike source\cstrike\cfg</tt>

You can also set the password upon connecting. For steam and IP authentication, your admin privileges will be automatically assigned if the password is correct. For name based authentication, your password must be correct before you change your name, or else you will be kicked from the server.

=Simple Admins=
The easiest way to add administrators is through <tt>configs/admins_simple.ini</tt>. This is a flat file which requires two parameters per line: authentication info, and flags. The flag string is somewhat flexible and can have the following information:
*An optional immunity level value, followed by a colon (':');
*A flag string, '''or''';
*A group name, preceded by an '@' symbol

Three examples are provided:
<pre>
"STEAM_0:1:16" "bce" //generic, kick, unban for this steam ID. no immunity
"!127.0.0.1" "5:z" //all permissions for this ip, immunity level = 5
"BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, generic, kick
</pre>

=Detailed Admins=
Alternatively, you can add admins via <tt>configs/admins.cfg</tt>, a more advanced file stored in a KeyValues format. Each admin is its own block inside a main "Admin" block. You can create and / or modify <tt>admins.cfg</tt> files with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager]. The format is as follows:

<pre>Admins
{
"Admin Name"
{
"auth" "[steam|name|ip]"
"identity" "[unique id]"
"[option1]" "[value1]"
"[option2]" "[value2]"
/* .... */
}
}</pre>

Available options are:
*<tt>auth</tt>: Required. Must be one of <tt>steam</tt>, <tt>name</tt>, or <tt>ip</tt> (unless there is a custom auth method), and instructs SourceMod how to interpret the <tt>identity</tt> value.
*<tt>identity</tt>: Required. Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Optional. Specifies the password the user must enter (see above section on passwords).
*<tt>group</tt>: Optional. Specifies a group name the user should inherit if available. More than one "group" line can be specified. There should be no '@' symbol as there is no ambiguity.
*<tt>flags</tt>: Optional. Default access flags the user should receive.
*<tt>immunity</tt>: Optional: Default immunity level the user should receive.

The admin name is optional (it can be blank). It is not used internally and is intended for convenience usage by 3rd party tools.

Example:
<pre>Admins
{
"BAILOPAN"
{
"auth" "steam"
"identity" "STEAM_0:1:2345"
"flags" "abcdef"
"immunity" "5"
"group" "Awesome Admins"
}

"Blue Crab"
{
"auth" "steam"
"identity" "STEAM_0:1:666666"
"flags" "z"
"immunity" "99"
}
}</pre>

=See Also=
*[[Adding Groups (SourceMod)]]
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]

Adding Groups (SourceMod)

2009-03-18T21:52:33Z

Recon0: /* File Format */

This article explains how to add and configure groups through <tt>configs/admin_groups.cfg</tt>. This file is parsed and loaded via <tt>admin-flatfile.smx</tt>.

=Introduction=
Groups are a convenient method of applying similar properties and permissions to multiple administrators. For example, let's say you wish for 15 administrators to all have the same permissions and immunity. In this case, you'd set up a group for these admins, after which changing the permissions for all member admins can be done via one location.

=File Format=
Groups are specified as blocks within a master "Group" block. Each group must have a unique name. If the name is not unique, the permissions will simply be extended/overwritten from the permissions of the existing group. That is to say, if a group exists in both the config file and an external source (say, SQL), then the permissions will end up being combined/overwritten in the order of parsing. You can create and / or modify <tt>admin_groups.cfg</tt> files with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager].

The group blocks appear in this format:
<pre>
Groups
{
"Group Name"
{
"[option1]" "[value1]"
"[option2]" "[value2]"
/* ... */
Overrides
{
"[override1]" "[allow|deny]"
"[override2]" "[allow|deny]"
/* ... */
}
}
}
</pre>

All options are optional (that is, they do not need to be explicitly defined). Similarly, the "Overrides" section is completely optional and may be omitted. The full options list contains:
*<tt>flags</tt>: Flag string that users of the group will inherit.
*<tt>immunity</tt>: If a numerical value, specifies the immunity value users will inherit if higher than their current immunity value. If preceded by an '@' symbol, then it specifies a group that the user will always be immune from.

The "Overrides" section allows specific commands or groups of commands to be completely allowed or denied to members of the group. This is a very powerful section. For example, you can opt to not give members the "map" flag, but allow them access to <tt>sm_map</tt>. Conversely, you could opt to give members the "map" flag, but deny them access to <tt>sm_map</tt>.

Command groups are explained further in the [[Overriding Command Access (SourceMod)]] article.

Combined example of a group with overrides:
<pre>
Groups
{
"Basic Admin"
{
"flags" "abc" //reservation, generic admin, kick
"immunity" "1" //low immunity value

Overrides
{
"sm_map" "allow" //Let them use sm_map even without the flag
":CSDM" "deny" //deny any commands from the CSDM group
}
}
}</pre>

=Inheritance=
Groups cannot be nested; that is to say, one group cannot inherit permissions from another group. However, an administrator can inherit any number of groups. The permissions will be <tt>additive</tt>, meaning that they will be assumed if and only if they result in more permissions being granted.

For example, if a user has flags <tt>bcd</tt> and a group assigns flags <tt>ae</tt>, inheritance would result in that user having the flags <tt>abcde</tt>. Similarly, a group's immunity value will only be inherited if it is larger than the user's current immunity value.

The only case this changes is with group-specific overrides. If a command is specifically allowed to group A and denied in group B, and a user inherits both groups A and B, whether or not the user can use the command will depend on the order of inheritance. If A is inherited first, the command will be allowed. If B is inherited first, the command will be denied.

Lastly, it is worth noting that once a user inherits permissions from a group, changes to the group will not affect the active permissions. This is an optimization. In order for changes to groups to affect that user, their administrative permissions must be entirely reset (either by a disconnect, or via <tt>sm_reloadadmins</tt>, which effectively reloads all permissions anyway).

=See Also=
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]

Adding Admins (SourceMod)

2009-03-18T21:51:59Z

Recon0: /* Detailed Admins */

__FORCETOC__
SourceMod has as very detailed and flexible administration system, and it can be quite daunting to users. To simplify things, there are a number of "flags" which specify generic permissions administrators can have.

Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file.

SourceMod provides three methods of authentication by default:
*''Steam ID'' (unique to a Steam account)
*''IP Address'' (semi-unique to a given computer, better for LANs)
*''Name'' (requires a password)

=Quick Start=
On the server, open cstrike/addons/sourcemod/configs/admins_simple.ini

In a new line, add the following, replacing yoursteamid (use your client's console '''status''' command to retrieve your steamid - formatted as STEAM_n:o:p)

'''"yoursteamid" "99:z"'''

Save

Restart Server

Connect to Server with Client

Enter sm_admin into console, and return to game. You should see admin menu.

=Levels=
First, let's quickly run down the provided levels:
:{| cellpadding="5"
|- class="t2th"
| Name
| Flag
| Purpose
|- class="t2td"
| reservation
| a
| Reserved slot access.
|- class="t2td"
| generic
| b
| Generic admin; required for admins.
|- class="t2td"
| kick
| c
| Kick other players.
|- class="t2td"
| ban
| d
| Ban other players.
|- class="t2td"
| unban
| e
| Remove bans.
|- class="t2td"
| slay
| f
| Slay/harm other players.
|- class="t2td"
| changemap
| g
| Change the map or major gameplay features.
|- class="t2td"
| cvar
| h
| Change most cvars.
|- class="t2td"
| config
| i
| Execute config files.
|- class="t2td"
| chat
| j
| Special chat privileges.
|- class="t2td"
| vote
| k
| Start or create votes.
|- class="t2td"
| password
| l
| Set a password on the server.
|- class="t2td"
| rcon
| m
| Use RCON commands.
|- class="t2td"
| cheats
| n
| Change sv_cheats or use cheating commands.
|- class="t2td"
| root
| z
| Magically enables all flags.
|}

=Immunity=
In SourceMod, immunity is a flexible system based on ''immunity levels''. Every admin can have an arbitrary immunity value assigned to them. Whether an admin can target another admin depends on who has a higher immunity value.

For example, say Admin #1 has an immunity level of "3" and Admin #2 has an immunity level of "10." Admin #2 can target Admin #1, but Admin #1 cannot target Admin #2. The numbers are completely arbitrary, and they can be any number equal to or higher than 0. Note that 0 always implies no immunity.

By default, admins with the same immunity value can target each other. This can be changed via <tt>sm_immunity_mode</tt> in <tt>cfg/sourcemod.cfg</tt>.

=Passwords=
For passwords to work, the server administrator must change the "PassInfoVar" line in <tt>addons/sourcemod/configs/core.cfg</tt>. For example:
<pre>"PassInfoVar" "_sm1337"</pre>

Next, if an admin has a password, he or she must set the password via the ''setinfo'' command in the client console. For example, using the examples above, <tt>BAILOPAN</tt> would need to type:
<pre>setinfo "_sm1337" "Gab3n"</pre>

To automate this upon connecting to a server, you can create an "autoexec.cfg" file in your client <tt>cstrike</tt> folder. This will be located under <tt>SteamApps\ACCOUNT\Counter-Strike Source\cstrike\cfg</tt>. For example:
*<tt>C:\program files\steam\steamapps\bailopan\counter-strike source\cstrike\cfg</tt>

You can also set the password upon connecting. For steam and IP authentication, your admin privileges will be automatically assigned if the password is correct. For name based authentication, your password must be correct before you change your name, or else you will be kicked from the server.

=Simple Admins=
The easiest way to add administrators is through <tt>configs/admins_simple.ini</tt>. This is a flat file which requires two parameters per line: authentication info, and flags. The flag string is somewhat flexible and can have the following information:
*An optional immunity level value, followed by a colon (':');
*A flag string, '''or''';
*A group name, preceded by an '@' symbol

Three examples are provided:
<pre>
"STEAM_0:1:16" "bce" //generic, kick, unban for this steam ID. no immunity
"!127.0.0.1" "5:z" //all permissions for this ip, immunity level = 5
"BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, generic, kick
</pre>

=Detailed Admins=
Alternatively, you can add admins via <tt>configs/admins.cfg</tt>, a more advanced file stored in a KeyValues format. Each admin is its own block inside a main "Admin" block. You can create and / or modify admins.cfg files with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager]. The format is as follows:

<pre>Admins
{
"Admin Name"
{
"auth" "[steam|name|ip]"
"identity" "[unique id]"
"[option1]" "[value1]"
"[option2]" "[value2]"
/* .... */
}
}</pre>

Available options are:
*<tt>auth</tt>: Required. Must be one of <tt>steam</tt>, <tt>name</tt>, or <tt>ip</tt> (unless there is a custom auth method), and instructs SourceMod how to interpret the <tt>identity</tt> value.
*<tt>identity</tt>: Required. Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Optional. Specifies the password the user must enter (see above section on passwords).
*<tt>group</tt>: Optional. Specifies a group name the user should inherit if available. More than one "group" line can be specified. There should be no '@' symbol as there is no ambiguity.
*<tt>flags</tt>: Optional. Default access flags the user should receive.
*<tt>immunity</tt>: Optional: Default immunity level the user should receive.

The admin name is optional (it can be blank). It is not used internally and is intended for convenience usage by 3rd party tools.

Example:
<pre>Admins
{
"BAILOPAN"
{
"auth" "steam"
"identity" "STEAM_0:1:2345"
"flags" "abcdef"
"immunity" "5"
"group" "Awesome Admins"
}

"Blue Crab"
{
"auth" "steam"
"identity" "STEAM_0:1:666666"
"flags" "z"
"immunity" "99"
}
}</pre>

=See Also=
*[[Adding Groups (SourceMod)]]
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]

Adding Groups (SourceMod)

2009-03-18T21:51:42Z

Recon0: /* File Format */

This article explains how to add and configure groups through <tt>configs/admin_groups.cfg</tt>. This file is parsed and loaded via <tt>admin-flatfile.smx</tt>.

=Introduction=
Groups are a convenient method of applying similar properties and permissions to multiple administrators. For example, let's say you wish for 15 administrators to all have the same permissions and immunity. In this case, you'd set up a group for these admins, after which changing the permissions for all member admins can be done via one location.

=File Format=
Groups are specified as blocks within a master "Group" block. Each group must have a unique name. If the name is not unique, the permissions will simply be extended/overwritten from the permissions of the existing group. That is to say, if a group exists in both the config file and an external source (say, SQL), then the permissions will end up being combined/overwritten in the order of parsing. You can create and / or modify admin_groups.cfg files with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager].

The group blocks appear in this format:
<pre>
Groups
{
"Group Name"
{
"[option1]" "[value1]"
"[option2]" "[value2]"
/* ... */
Overrides
{
"[override1]" "[allow|deny]"
"[override2]" "[allow|deny]"
/* ... */
}
}
}
</pre>

All options are optional (that is, they do not need to be explicitly defined). Similarly, the "Overrides" section is completely optional and may be omitted. The full options list contains:
*<tt>flags</tt>: Flag string that users of the group will inherit.
*<tt>immunity</tt>: If a numerical value, specifies the immunity value users will inherit if higher than their current immunity value. If preceded by an '@' symbol, then it specifies a group that the user will always be immune from.

The "Overrides" section allows specific commands or groups of commands to be completely allowed or denied to members of the group. This is a very powerful section. For example, you can opt to not give members the "map" flag, but allow them access to <tt>sm_map</tt>. Conversely, you could opt to give members the "map" flag, but deny them access to <tt>sm_map</tt>.

Command groups are explained further in the [[Overriding Command Access (SourceMod)]] article.

Combined example of a group with overrides:
<pre>
Groups
{
"Basic Admin"
{
"flags" "abc" //reservation, generic admin, kick
"immunity" "1" //low immunity value

Overrides
{
"sm_map" "allow" //Let them use sm_map even without the flag
":CSDM" "deny" //deny any commands from the CSDM group
}
}
}</pre>

=Inheritance=
Groups cannot be nested; that is to say, one group cannot inherit permissions from another group. However, an administrator can inherit any number of groups. The permissions will be <tt>additive</tt>, meaning that they will be assumed if and only if they result in more permissions being granted.

For example, if a user has flags <tt>bcd</tt> and a group assigns flags <tt>ae</tt>, inheritance would result in that user having the flags <tt>abcde</tt>. Similarly, a group's immunity value will only be inherited if it is larger than the user's current immunity value.

The only case this changes is with group-specific overrides. If a command is specifically allowed to group A and denied in group B, and a user inherits both groups A and B, whether or not the user can use the command will depend on the order of inheritance. If A is inherited first, the command will be allowed. If B is inherited first, the command will be denied.

Lastly, it is worth noting that once a user inherits permissions from a group, changes to the group will not affect the active permissions. This is an optimization. In order for changes to groups to affect that user, their administrative permissions must be entirely reset (either by a disconnect, or via <tt>sm_reloadadmins</tt>, which effectively reloads all permissions anyway).

=See Also=
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]

Adding Groups (SourceMod)

2009-03-18T21:50:32Z

Recon0: /* File Format */

This article explains how to add and configure groups through <tt>configs/admin_groups.cfg</tt>. This file is parsed and loaded via <tt>admin-flatfile.smx</tt>.

=Introduction=
Groups are a convenient method of applying similar properties and permissions to multiple administrators. For example, let's say you wish for 15 administrators to all have the same permissions and immunity. In this case, you'd set up a group for these admins, after which changing the permissions for all member admins can be done via one location.

=File Format=
Groups are specified as blocks within a master "Group" block. Each group must have a unique name. If the name is not unique, the permissions will simply be extended/overwritten from the permissions of the existing group. That is to say, if a group exists in both the config file and an external source (say, SQL), then the permissions will end up being combined/overwritten in the order of parsing. Group configuration files can be created and modified with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager].

The group blocks appear in this format:
<pre>
Groups
{
"Group Name"
{
"[option1]" "[value1]"
"[option2]" "[value2]"
/* ... */
Overrides
{
"[override1]" "[allow|deny]"
"[override2]" "[allow|deny]"
/* ... */
}
}
}
</pre>

All options are optional (that is, they do not need to be explicitly defined). Similarly, the "Overrides" section is completely optional and may be omitted. The full options list contains:
*<tt>flags</tt>: Flag string that users of the group will inherit.
*<tt>immunity</tt>: If a numerical value, specifies the immunity value users will inherit if higher than their current immunity value. If preceded by an '@' symbol, then it specifies a group that the user will always be immune from.

The "Overrides" section allows specific commands or groups of commands to be completely allowed or denied to members of the group. This is a very powerful section. For example, you can opt to not give members the "map" flag, but allow them access to <tt>sm_map</tt>. Conversely, you could opt to give members the "map" flag, but deny them access to <tt>sm_map</tt>.

Command groups are explained further in the [[Overriding Command Access (SourceMod)]] article.

Combined example of a group with overrides:
<pre>
Groups
{
"Basic Admin"
{
"flags" "abc" //reservation, generic admin, kick
"immunity" "1" //low immunity value

Overrides
{
"sm_map" "allow" //Let them use sm_map even without the flag
":CSDM" "deny" //deny any commands from the CSDM group
}
}
}</pre>

=Inheritance=
Groups cannot be nested; that is to say, one group cannot inherit permissions from another group. However, an administrator can inherit any number of groups. The permissions will be <tt>additive</tt>, meaning that they will be assumed if and only if they result in more permissions being granted.

For example, if a user has flags <tt>bcd</tt> and a group assigns flags <tt>ae</tt>, inheritance would result in that user having the flags <tt>abcde</tt>. Similarly, a group's immunity value will only be inherited if it is larger than the user's current immunity value.

The only case this changes is with group-specific overrides. If a command is specifically allowed to group A and denied in group B, and a user inherits both groups A and B, whether or not the user can use the command will depend on the order of inheritance. If A is inherited first, the command will be allowed. If B is inherited first, the command will be denied.

Lastly, it is worth noting that once a user inherits permissions from a group, changes to the group will not affect the active permissions. This is an optimization. In order for changes to groups to affect that user, their administrative permissions must be entirely reset (either by a disconnect, or via <tt>sm_reloadadmins</tt>, which effectively reloads all permissions anyway).

=See Also=
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]

Adding Admins (SourceMod)

2009-03-18T21:47:02Z

Recon0:

__FORCETOC__
SourceMod has as very detailed and flexible administration system, and it can be quite daunting to users. To simplify things, there are a number of "flags" which specify generic permissions administrators can have.

Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file.

SourceMod provides three methods of authentication by default:
*''Steam ID'' (unique to a Steam account)
*''IP Address'' (semi-unique to a given computer, better for LANs)
*''Name'' (requires a password)

=Quick Start=
On the server, open cstrike/addons/sourcemod/configs/admins_simple.ini

In a new line, add the following, replacing yoursteamid (use your client's console '''status''' command to retrieve your steamid - formatted as STEAM_n:o:p)

'''"yoursteamid" "99:z"'''

Save

Restart Server

Connect to Server with Client

Enter sm_admin into console, and return to game. You should see admin menu.

=Levels=
First, let's quickly run down the provided levels:
:{| cellpadding="5"
|- class="t2th"
| Name
| Flag
| Purpose
|- class="t2td"
| reservation
| a
| Reserved slot access.
|- class="t2td"
| generic
| b
| Generic admin; required for admins.
|- class="t2td"
| kick
| c
| Kick other players.
|- class="t2td"
| ban
| d
| Ban other players.
|- class="t2td"
| unban
| e
| Remove bans.
|- class="t2td"
| slay
| f
| Slay/harm other players.
|- class="t2td"
| changemap
| g
| Change the map or major gameplay features.
|- class="t2td"
| cvar
| h
| Change most cvars.
|- class="t2td"
| config
| i
| Execute config files.
|- class="t2td"
| chat
| j
| Special chat privileges.
|- class="t2td"
| vote
| k
| Start or create votes.
|- class="t2td"
| password
| l
| Set a password on the server.
|- class="t2td"
| rcon
| m
| Use RCON commands.
|- class="t2td"
| cheats
| n
| Change sv_cheats or use cheating commands.
|- class="t2td"
| root
| z
| Magically enables all flags.
|}

=Immunity=
In SourceMod, immunity is a flexible system based on ''immunity levels''. Every admin can have an arbitrary immunity value assigned to them. Whether an admin can target another admin depends on who has a higher immunity value.

For example, say Admin #1 has an immunity level of "3" and Admin #2 has an immunity level of "10." Admin #2 can target Admin #1, but Admin #1 cannot target Admin #2. The numbers are completely arbitrary, and they can be any number equal to or higher than 0. Note that 0 always implies no immunity.

By default, admins with the same immunity value can target each other. This can be changed via <tt>sm_immunity_mode</tt> in <tt>cfg/sourcemod.cfg</tt>.

=Passwords=
For passwords to work, the server administrator must change the "PassInfoVar" line in <tt>addons/sourcemod/configs/core.cfg</tt>. For example:
<pre>"PassInfoVar" "_sm1337"</pre>

Next, if an admin has a password, he or she must set the password via the ''setinfo'' command in the client console. For example, using the examples above, <tt>BAILOPAN</tt> would need to type:
<pre>setinfo "_sm1337" "Gab3n"</pre>

To automate this upon connecting to a server, you can create an "autoexec.cfg" file in your client <tt>cstrike</tt> folder. This will be located under <tt>SteamApps\ACCOUNT\Counter-Strike Source\cstrike\cfg</tt>. For example:
*<tt>C:\program files\steam\steamapps\bailopan\counter-strike source\cstrike\cfg</tt>

You can also set the password upon connecting. For steam and IP authentication, your admin privileges will be automatically assigned if the password is correct. For name based authentication, your password must be correct before you change your name, or else you will be kicked from the server.

=Simple Admins=
The easiest way to add administrators is through <tt>configs/admins_simple.ini</tt>. This is a flat file which requires two parameters per line: authentication info, and flags. The flag string is somewhat flexible and can have the following information:
*An optional immunity level value, followed by a colon (':');
*A flag string, '''or''';
*A group name, preceded by an '@' symbol

Three examples are provided:
<pre>
"STEAM_0:1:16" "bce" //generic, kick, unban for this steam ID. no immunity
"!127.0.0.1" "5:z" //all permissions for this ip, immunity level = 5
"BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, generic, kick
</pre>

=Detailed Admins=
Alternatively, you can add admins via <tt>configs/admins.cfg</tt>, a more advanced file stored in a KeyValues format. Each admin is its own block inside a main "Admin" block. You can create and modify admins.cfg files with [http://forums.alliedmods.net/showthread.php?t=81160 KVManager]. The format is as follows:

<pre>Admins
{
"Admin Name"
{
"auth" "[steam|name|ip]"
"identity" "[unique id]"
"[option1]" "[value1]"
"[option2]" "[value2]"
/* .... */
}
}</pre>

Available options are:
*<tt>auth</tt>: Required. Must be one of <tt>steam</tt>, <tt>name</tt>, or <tt>ip</tt> (unless there is a custom auth method), and instructs SourceMod how to interpret the <tt>identity</tt> value.
*<tt>identity</tt>: Required. Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Optional. Specifies the password the user must enter (see above section on passwords).
*<tt>group</tt>: Optional. Specifies a group name the user should inherit if available. More than one "group" line can be specified. There should be no '@' symbol as there is no ambiguity.
*<tt>flags</tt>: Optional. Default access flags the user should receive.
*<tt>immunity</tt>: Optional: Default immunity level the user should receive.

The admin name is optional (it can be blank). It is not used internally and is intended for convenience usage by 3rd party tools.

Example:
<pre>Admins
{
"BAILOPAN"
{
"auth" "steam"
"identity" "STEAM_0:1:2345"
"flags" "abcdef"
"immunity" "5"
"group" "Awesome Admins"
}

"Blue Crab"
{
"auth" "steam"
"identity" "STEAM_0:1:666666"
"flags" "z"
"immunity" "99"
}
}</pre>

=See Also=
*[[Adding Groups (SourceMod)]]
*[[Overriding Command Access (SourceMod)]]

[[Category:SourceMod Documentation]]