AlliedModders Wiki - User contributions [en]

Adding Admins (SourceMod)

2016-04-23T13:56:23Z

Avi12: /* Quick Start */

__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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 <code>/addons/sourcemod/configs/admins_simple.ini</code>

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

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=Passwords=
Using the passwords method is '''optional'''.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax:

< > - Required

[ ] - Optional

/ - Or
<pre>
"<Steam ID/!IP/Stean name>" "[immunity level:]<flag/@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-23T09:08:25Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=Passwords=
Using the passwords method is '''optional'''.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax:

< > - Required

[ ] - Optional

/ - Or
<pre>
"<Steam ID/!IP/Stean name>" "[immunity level:]<flag/@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-23T09:07:49Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=Passwords=
Using the passwords method is '''optional'''.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax:

< > - Required

[ ] - Optional

/ | - Or
<pre>
"<Steam ID/!IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-23T09:06:00Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=Passwords=
Using the passwords method is '''optional'''.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax - the content inside < > is required, but optional inside [ ]:
<pre>
"<Steam ID/!IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T15:25:52Z

Avi12: /* Passwords */

__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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=Passwords=
Using the passwords method is '''optional'''.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax - the content inside < > is required, but optional inside [ ]:
<pre>
"<Steam ID/IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T15:21:42Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's syntax - the content inside < > is required, but optional inside [ ]:
<pre>
"<Steam ID/IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T15:21:06Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's template - the content inside < > is required, but optional inside [ ]:
<pre>
"<Steam ID/IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T15:20:44Z

Avi12: /* Simple 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 string's template - the content inside <> is required, but optional inside []:
<pre>
"<Steam ID/IP/Stean name>" "[immunity level:]<flag|@group>" ["password"]
</pre>

Examples:
<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
"Gaben" "@Admins" //name Gaben, group Admins
</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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T14:58:32Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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:

* - Required
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T14:58:02Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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>

* - Required

Available options:
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-22T14:56:40Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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>

Required options are marked in *

Available options:
*<tt>auth</tt> *: 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> *: Unique value that allows SourceMod to find this admin given an authentication method and the given value.
*<tt>password</tt>: Specifies the password the user must enter (see [[#Passwords|passwords]]).
*<tt>group</tt>: 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>: Default access flags the user should receive.
*<tt>immunity</tt>: 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]]

{{LanguageSwitch}}

Adding Groups (SourceMod)

2016-04-02T09:26:00Z

Avi12:

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 Groups (SourceMod)

2016-04-02T09:22:05Z

Avi12: /* 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)

2016-04-01T19:42:55Z

Avi12: /* Passwords */

__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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person must set the password via the ''setinfo'' command in the client console. For example, using the examples above, the player <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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 [[#Passwords|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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-01T19:14:16Z

Avi12: /* Passwords */

__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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

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

Next, if an admin has a password, the person 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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 [[#Passwords|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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-01T17:28:35Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 [[#Passwords|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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-01T16:33:50Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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 [[#Passwords|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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-01T16:27:32Z

Avi12: /* 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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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]]

{{LanguageSwitch}}

Adding Admins (SourceMod)

2016-04-01T16:07:34Z

Avi12: /* Quick Start */

__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.

There are currently two provided ways of storing admins. One is via the admin-flatfile.smx plugin that is enabled by default. This plugin provides two files: a simplified flat file, and another more complex tree-based file. The other way to store admins is using [[SQL Admins (SourceMod)|SQL]].

SourceMod provides three methods of authentication:
*''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 [modfolder]/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 Steam ID - formatted as STEAM_n:o:p)

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

Save the file, then type <code>sm_reloadadmins</code> in the server console. Connect to the server with the game client. Enter sm_admin in the client console, and then return to the game. You should see the 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 and ignores immunity values.

|- class="t2td"
| custom1
| o
| Custom Group 1.
|- class="t2td"
| custom2
| p
| Custom Group 2.
|- class="t2td"
| custom3
| q
| Custom Group 3.
|- class="t2td"
| custom4
| r
| Custom Group 4.
|- class="t2td"
| custom5
| s
| Custom Group 5.
|- class="t2td"
| custom6
| t
| Custom Group 6.
|}

=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>.

'''Admins with the z flag are not subject to immunity checks.''' This means they can always target anyone.

=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 game folder. This will be located under <tt>SteamApps\common\[game]\[gameabbr]\cfg</tt>. For example:
*<tt>C:\Program Files\Steam\steamapps\common\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]]

{{LanguageSwitch}}

SourceMod

2016-03-21T20:35:08Z

Avi12: /* Initial Project */

=Introduction=
SourceMod is a [[SourceMM|Metamod:Source]] plugin for [[Half-Life 2]]. It provides comprehensive scripting for the Source engine and mods written using the Source SDK. It has features for administration systems, commands, console variables, events, network messages, timed actions, math and string routines, entity modification, and more. It also features a safely versioned, object oriented API usable from "extensions" written in C++. The extension API can be used to add scripting language callbacks and native features.

SourceMod scripts are written in the SourcePawn language, which is derived from [[Pawn]]. Some of the differences include:
*Passing functions as "objects," instead of by name
*Natively packed and tagged strings
*Dynamic local variables
*A '<tt>decl</tt>' operator for creating uninitialized variables
*A new virtual machine and JIT, both rewritten in C++
*A new file format

=History=
==Initial Project==
SourceMod was officially announced on October 7th, 2004, as a successor to [[AMX Mod X]] for the Half-Life 1 engine. It was targetted as a complete rewrite of AMX Mod X, with the following fundamental changes:
*Use of multiple (pluggable) scripting languages
*JavaScript support
*Unloadability
*An object-oriented module API

The Source SDK was released on December 1st, 2004. A few weeks later, SourceMod released its source code on December 25th. Then, development began to stagnate. The concept of multiple languages was over-ambitious and improper. The system was largely too complex and too unorganized for developers to understand. Most importantly, the integral calling abstraction layer, designed to let Core talk to plugins without knowing the target scripting layer, was never viable. Because of this and the inherent complexity of MetaEng, scripts were not testable.

By May of 2005, SourceMod had become completely abandoned. The codebase was scrapped for a rewrite, called "Core 2." This was also quickly abandoned. This timeline and the details therein are explained on the SourceMod [http://www.sourcemod.net/devlog/?p=88 Dev Log]. The remaining members of the SourceMod team went back to AMX Mod X.

==SourceHook==
By January of 2005, it was apparent that Valve's API would not be sufficient for plugin development in C++. SourceMod and AMX Mod X Developer Pavol "PM OnoTo" Marko started working on an API for safely hooking virtual functions via vtables.

By March of 2005, it was apparent that this technology would be more useful as a separate project. Thus, SourceHook broke from SourceMod and the [[SourceMM|Metamod:Source]] project was started. Metamod:Source was first released on May 26, 2005.

==Current Project==
In March of 2006, a public survey was held to determine if the community still wanted SourceMod. Since the response was good, the project was restarted, but in secret, to avoid the same public relations mistakes. From March to September, SourcePawn was written, which included:
*A new JIT, written completely in C++
*A new virtual machine and API, written in C++ with object oriented API
*A new file format
*Various new language features

From November 2006 to January 2007, SourceMod evolved into a usable scripting platform based on SourcePawn. As of March 16, 2007, it contained enough scripting-level features to be usable, and builds were made available to the public.

SourceMod remains an ongoing development project which now runs on over 38% of all Source servers.

=Development Team=
*See the [http://www.sourcemod.net/credits.php credits page].

=Future Plans=
As of the time of writing, SourceMod version 1.4.2 has been released and version 1.5 is under development. New API functionality and game support is added to SourceMod with every update.

=License=
SourceMod is licensed under the [[GNU General Public License]].

=See Also=
*[[Introduction to SourcePawn]]
*[[Introduction to SourceMod Plugins]]

=External Links=
*[http://www.sourcemod.net/ SourceMod Website]
*[http://www.metamodsource.net/ Metamod:Source Website]

[[Category:Half-Life_2]]
[[Category:SourceMod]]

SourceMod

2016-03-21T20:33:32Z

Avi12: /* Initial Project */

=Introduction=
SourceMod is a [[SourceMM|Metamod:Source]] plugin for [[Half-Life 2]]. It provides comprehensive scripting for the Source engine and mods written using the Source SDK. It has features for administration systems, commands, console variables, events, network messages, timed actions, math and string routines, entity modification, and more. It also features a safely versioned, object oriented API usable from "extensions" written in C++. The extension API can be used to add scripting language callbacks and native features.

SourceMod scripts are written in the SourcePawn language, which is derived from [[Pawn]]. Some of the differences include:
*Passing functions as "objects," instead of by name
*Natively packed and tagged strings
*Dynamic local variables
*A '<tt>decl</tt>' operator for creating uninitialized variables
*A new virtual machine and JIT, both rewritten in C++
*A new file format

=History=
==Initial Project==
SourceMod was officially announced on October 7th, 2004, as a successor to [[AMX Mod X]] for the Half-Life 1 engine. It was targetted as a complete rewrite of AMX Mod X, with the following fundamental changes:
*Use of multiple (pluggable) scripting languages
*JavaScript support
*Unloadability
*An object-oriented module API

The Source SDK was released on December 1st, 2004. A few weeks later, SourceMod released its source code on December 25th. After this, development began to stagnate. The concept of multiple languages was over-ambitious and improper. The system was largely too complex and too unorganized for developers to understand. Most importantly, the integral calling abstraction layer, designed to let Core talk to plugins without knowing the target scripting layer, was never viable. Because of this and the inherent complexity of MetaEng, scripts were not testable.

By May of 2005, SourceMod had become completely abandoned. The codebase was scrapped for a rewrite, called "Core 2." This was also quickly abandoned. This timeline and the details therein are explained on the SourceMod [http://www.sourcemod.net/devlog/?p=88 Dev Log]. The remaining members of the SourceMod team went back to AMX Mod X.

==SourceHook==
By January of 2005, it was apparent that Valve's API would not be sufficient for plugin development in C++. SourceMod and AMX Mod X Developer Pavol "PM OnoTo" Marko started working on an API for safely hooking virtual functions via vtables.

By March of 2005, it was apparent that this technology would be more useful as a separate project. Thus, SourceHook broke from SourceMod and the [[SourceMM|Metamod:Source]] project was started. Metamod:Source was first released on May 26, 2005.

==Current Project==
In March of 2006, a public survey was held to determine if the community still wanted SourceMod. Since the response was good, the project was restarted, but in secret, to avoid the same public relations mistakes. From March to September, SourcePawn was written, which included:
*A new JIT, written completely in C++
*A new virtual machine and API, written in C++ with object oriented API
*A new file format
*Various new language features

From November 2006 to January 2007, SourceMod evolved into a usable scripting platform based on SourcePawn. As of March 16, 2007, it contained enough scripting-level features to be usable, and builds were made available to the public.

SourceMod remains an ongoing development project which now runs on over 38% of all Source servers.

=Development Team=
*See the [http://www.sourcemod.net/credits.php credits page].

=Future Plans=
As of the time of writing, SourceMod version 1.4.2 has been released and version 1.5 is under development. New API functionality and game support is added to SourceMod with every update.

=License=
SourceMod is licensed under the [[GNU General Public License]].

=See Also=
*[[Introduction to SourcePawn]]
*[[Introduction to SourceMod Plugins]]

=External Links=
*[http://www.sourcemod.net/ SourceMod Website]
*[http://www.metamodsource.net/ Metamod:Source Website]

[[Category:Half-Life_2]]
[[Category:SourceMod]]

Installing SourceMod

2015-11-22T16:11:37Z

Avi12:

{{Languages|Installing_SourceMod}}

Installing SourceMod is very simple, and it can be added with almost no configuration changes.

=Prerequisites=
A GUI Web Browser to retrieve Metamod and SourceMod compressed archives.
A tool to copy archive to your dedicated server host.

SourceMod requires [[Metamod:Source]] 1.9.0 or higher (it is recommended that the latest version is used). [http://www.metamodsource.net/ Click here] to visit the Metamod:Source homepage. Instructions to install SourceMM manually can be found [[Installing Metamod:Source|here]].

SourceMod will run on almost any mod built using the Source SDK.

Valve sometimes makes changes in their games that break SourceMod between releases. When this happens, you may need to install snapshot versions of Metamod and SourceMod. You can see if this is required on the [[Required Versions (SourceMod)|Required Versions]] page.

=Uploading/Installing=
==Local Server==
To install [http://www.sourcemod.net/downloads.php SourceMod] locally, simply extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike, <tt>dod</tt> for Day of Defeat, et cetera).

==Remote Server==
To install SourceMod remotely, first extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your local computer (for example, your Desktop). You will see an <tt>addons</tt> folder.

Using a tool such as [https://encrypted.google.com/#q=FTP FTP], locate your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike:Source, <tt>dod</tt> for Day of Defeat:Source, et cetera). Underneath this folder, you should have an <tt>addons</tt> folder (if not, Metamod:Source is probably not installed). From your local <tt>addons</tt> folder, upload the entire contents to your remote <tt>addons</tt> folder. When done, your remote <tt>addons</tt> folder should have a <tt>sourcemod</tt> folder.

If you have trouble with these steps, you need to get acquainted with FTP and server management. However, you can also ask your server provider for help. Some providers also have web interfaces for managing your server.

Alternatively, if you copied the tar.gz to your srcds directory, execute the following from the cstrike sub directory:
tar -xzf ../sourcemod-1.1.0.tar.gz

=Checking the Install=
Your folder layout should look like:
*<tt>[mod]</tt> - Your mod's folder
**<tt>addons</tt>
***<tt>metamod</tt> - Metamod:Source
***<tt>sourcemod</tt> - SourceMod

Once SourceMod is uploaded/copied and configured with Metamod:Source, restart your server completely. If it is local, shut it down and restart it. If it is remote, you may need to ask your server provider for help. However, it is often safe to issue a "quit" command via [[rcon]], since most providers will automatically restart your server.

First, in your [[server console]] (not client console), type:
<pre>meta list</pre>

If the install worked, you will see something like:
<pre>] meta list
Listing 1 plugin:
[01] SourceMod (1.1.0.2489) by AlliedModders LLC</pre>

You should then be able to use the SourceMod root console command, which can be invoked with simply:
<pre>sm</pre>

For example:
<pre>] sm version
SourceMod Version Information:
SourceMod Version: 1.1.0.2489
SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.1.0-svn)
SourcePawn API: v1 = 4, v2 = 2
Compiled on: Sep 5 2008 02:02:12
http://www.sourcemod.net/
</pre>

Lastly, assuming you have already setup your administration user (if not, see [[Adding Admins (SourceMod)|this page]]), you can test the in game menu by joining the server, and in the client console type the following:
<pre>sm_admin</pre>
You should see a menu popup with all you options.

=Troubleshooting=
If the install failed, you will generally see one of four symptoms.

==Metamod reports NOFILE or FAILED==
If "meta list" replies with something like this:
<pre>] meta list
Listing 1 plugin:
[01] <NOFILE></pre>

Most likely, either the files are not located in the correct place, or the file could not be loaded. For more information, use the following command (except use the correct list number):
<pre>meta info 1</pre>

==Metamod lists no plugins==
If "meta list" replies with something like this:
<pre>] meta list
Listing 0 plugins:</pre>

There are several causes of this error.

# The most common cause is that sourcemod.vdf can't be located in the addons/metamod folder. Verify that sourcemod.vdf is present in this folder.
# If sourcemod.vdf is present, make sure you are using the correct build of Sourcemod (zip = windows, tar.gz = linux).

==Metamod says nothing==
If "meta list" has no reply at all, Metamod:Source is not properly installed. [[Installing Metamod:Source|This wiki page]] may provide you with clues on how to solve this problem.

[[Category:SourceMod Documentation]]

Installing SourceMod

2014-08-01T08:43:58Z

Avi12: /* Checking the Install */

{{Languages|Installing_SourceMod}}

Installing SourceMod is very simple, and it can be added with almost no configuration changes.

=Prerequisites=
A GUI Web Browser to retrieve Metamod and SourceMod compressed archives.
A tool to copy archive to your dedicated server host.

SourceMod requires [[Metamod:Source]] 1.9.0 or higher (it is recommended that the latest version is used). [http://www.metamodsource.net/ Click here] to visit the Metamod:Source homepage. Instructions to install SourceMM manually can be found [[Installing Metamod:Source|here]].

SourceMod will run on almost any mod built using the Source SDK.

=Uploading/Installing=
==Local Server==
To install SourceMod locally, simply extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike, <tt>dod</tt> for Day of Defeat, et cetera).
[http://www.sourcemod.net/downloads.php Download Here]

==Remote Server==
To install SourceMod remotely, first extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your local computer (for example, your Desktop). You will see an <tt>addons</tt> folder.

Using a tool such as [https://encrypted.google.com/#q=FTP FTP], locate your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike:Source, <tt>dod</tt> for Day of Defeat:Source, et cetera). Underneath this folder, you should have an <tt>addons</tt> folder (if not, Metamod:Source is probably not installed). From your local <tt>addons</tt> folder, upload the entire contents to your remote <tt>addons</tt> folder. When done, your remote <tt>addons</tt> folder should have a <tt>sourcemod</tt> folder.

If you have trouble with these steps, you need to get acquainted with FTP and server management. However, you can also ask your server provider for help. Some providers also have web interfaces for managing your server.

Alternatively, if you copied the tar.gz to your srcds directory, execute the following from the cstrike sub directory:
tar -xzf ../sourcemod-1.1.0.tar.gz

=Checking the Install=
Your folder layout should look like:
*<tt>[mod]</tt> - Your mod's folder
**<tt>addons</tt>
***<tt>metamod</tt> - Metamod:Source
***<tt>sourcemod</tt> - SourceMod

Once SourceMod is uploaded/copied and configured with Metamod:Source, restart your server completely. If it is local, shut it down and restart it. If it is remote, you may need to ask your server provider for help. However, it is often safe to issue a "quit" command via [[rcon]], since most providers will automatically restart your server.

First, in your [[server console]] (not client console), type:
<pre>meta list</pre>

If the install worked, you will see something like:
<pre>] meta list
Listing 1 plugin:
[01] SourceMod (1.1.0.2489) by AlliedModders LLC</pre>

You should then be able to use the SourceMod root console command, which can be invoked with simply:
<pre>sm</pre>

For example:
<pre>] sm version
SourceMod Version Information:
SourceMod Version: 1.1.0.2489
SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.1.0-svn)
SourcePawn API: v1 = 4, v2 = 2
Compiled on: Sep 5 2008 02:02:12
http://www.sourcemod.net/
</pre>

Lastly, assuming you have already setup your administration user (if not, see [[Adding Admins (SourceMod)|this page]]), you can test the in game menu by joining the server, and in the client console type the following:
<pre>sm_admin</pre>
You should see a menu popup with all you options.

=Troubleshooting=
If the install failed, you will generally see one of four symptoms.

==Metamod reports NOFILE or FAILED==
If "meta list" replies with something like this:
<pre>] meta list
Listing 1 plugin:
[01] <NOFILE></pre>

Most likely, either the files are not located in the correct place, or the file could not be loaded. For more information, use the following command (except use the correct list number):
<pre>meta info 1</pre>

==Metamod lists no plugins==
If "meta list" replies with something like this:
<pre>] meta list
Listing 0 plugins:</pre>

There are several causes of this error.

# The most common cause is that sourcemod.vdf can't be located in the addons/metamod folder. Verify that sourcemod.vdf is present in this folder.
# If sourcemod.vdf is present, make sure you are using the correct build of Sourcemod (zip = windows, tar.gz = linux).

==Metamod says nothing==
If "meta list" has no reply at all, Metamod:Source is not properly installed. [[Installing Metamod:Source|This wiki page]] may provide you with clues on how to solve this problem.

[[Category:SourceMod Documentation]]

Installing SourceMod

2014-08-01T08:37:20Z

Avi12: /* Remote Server */

{{Languages|Installing_SourceMod}}

Installing SourceMod is very simple, and it can be added with almost no configuration changes.

=Prerequisites=
A GUI Web Browser to retrieve Metamod and SourceMod compressed archives.
A tool to copy archive to your dedicated server host.

SourceMod requires [[Metamod:Source]] 1.9.0 or higher (it is recommended that the latest version is used). [http://www.metamodsource.net/ Click here] to visit the Metamod:Source homepage. Instructions to install SourceMM manually can be found [[Installing Metamod:Source|here]].

SourceMod will run on almost any mod built using the Source SDK.

=Uploading/Installing=
==Local Server==
To install SourceMod locally, simply extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike, <tt>dod</tt> for Day of Defeat, et cetera).
[http://www.sourcemod.net/downloads.php Download Here]

==Remote Server==
To install SourceMod remotely, first extract the <tt>.zip</tt> (Windows) or <tt>.tar.gz</tt> (Linux) package to your local computer (for example, your Desktop). You will see an <tt>addons</tt> folder.

Using a tool such as [https://encrypted.google.com/#q=FTP FTP], locate your mod folder (i.e. <tt>cstrike</tt> for Counter-Strike:Source, <tt>dod</tt> for Day of Defeat:Source, et cetera). Underneath this folder, you should have an <tt>addons</tt> folder (if not, Metamod:Source is probably not installed). From your local <tt>addons</tt> folder, upload the entire contents to your remote <tt>addons</tt> folder. When done, your remote <tt>addons</tt> folder should have a <tt>sourcemod</tt> folder.

If you have trouble with these steps, you need to get acquainted with FTP and server management. However, you can also ask your server provider for help. Some providers also have web interfaces for managing your server.

Alternatively, if you copied the tar.gz to your srcds directory, execute the following from the cstrike sub directory:
tar -xzf ../sourcemod-1.1.0.tar.gz

=Checking the Install=
Your folder layout should look like:
*<tt>[mod]</tt> - Your mod's folder
**<tt>addons</tt>
***<tt>metamod</tt> - Metamod:Source
***<tt>sourcemod</tt> - SourceMod

Once SourceMod is uploaded/copied and configured with Metamod:Source, restart your server completely. If it is local, shut it down and restart it. If it is remote, you may need to ask your server provider for help. However, it is often safe to issue a "quit" command via [[rcon]], since most providers will automatically restart your server.

First, in your [[server console]] (not client console), type:
<pre>meta list</pre>

If the install worked, you will see something like:
<pre>] meta list
Listing 1 plugin:
[01] SourceMod (1.1.0.2489) by AlliedModders LLC</pre>

You should then be able to use the SourceMod root console command, which can be invoked with simply:
<pre>sm</pre>

For example:
<pre>] sm version
SourceMod Version Information:
SourceMod Version: 1.1.0.2489
SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.1.0-svn)
SourcePawn API: v1 = 4, v2 = 2
Compiled on: Sep 5 2008 02:02:12
http://www.sourcemod.net/
</pre>

Lastly, assuming you have already setup your administration user, you can test the in game menu by joining the server, and in the client console type the following:
<pre>sm_admin</pre>
You should see a menu popup with all you options.

=Troubleshooting=
If the install failed, you will generally see one of four symptoms.

==Metamod reports NOFILE or FAILED==
If "meta list" replies with something like this:
<pre>] meta list
Listing 1 plugin:
[01] <NOFILE></pre>

Most likely, either the files are not located in the correct place, or the file could not be loaded. For more information, use the following command (except use the correct list number):
<pre>meta info 1</pre>

==Metamod lists no plugins==
If "meta list" replies with something like this:
<pre>] meta list
Listing 0 plugins:</pre>

There are several causes of this error.

# The most common cause is that sourcemod.vdf can't be located in the addons/metamod folder. Verify that sourcemod.vdf is present in this folder.
# If sourcemod.vdf is present, make sure you are using the correct build of Sourcemod (zip = windows, tar.gz = linux).

==Metamod says nothing==
If "meta list" has no reply at all, Metamod:Source is not properly installed. [[Installing Metamod:Source|This wiki page]] may provide you with clues on how to solve this problem.

[[Category:SourceMod Documentation]]