Difference between revisions of "Adding Admins (SourceMod)"
m |
m |
||
| Line 4: | Line 4: | ||
Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file. | Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file. | ||
| − | ''' | + | SourceMod provides three methods of authentication by default: |
| + | *''Steam ID'' (unique to a Steam account) | ||
| + | *''IP Address'' (semi-unique to a given computer, better for LANs) | ||
| + | *''Name'' (requires a password, and is this unique to that password) | ||
=Levels= | =Levels= | ||
| Line 90: | Line 93: | ||
"BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, kick, ban | "BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, kick, ban | ||
</pre> | </pre> | ||
| + | |||
| + | =Passwords= | ||
| + | For passwords to work, the server administrator must change the "PassInfoVar" line in <tt>addons/sourcemod/configs/core.cfg</tt>. For example: | ||
| + | <pre>"PassInfoVar" "_sm1337"</pre> | ||
| + | |||
| + | Next, if an admin has a password, he or she must set the password via the ''setinfo'' command in the client console. For example, using the examples above, <tt>BAILOPAN</tt> would need to type: | ||
| + | <pre>setinfo "_sm1337" "Gab3n"</pre> | ||
| + | |||
| + | To automate this upon connecting to a server, you can create an "autoexec.cfg" file in your client <tt>cstrike</tt> folder. This will be located under <tt>SteamApps\ACCOUNT\Counter-Strike Source\cstrike\cfg</tt>. For example: | ||
| + | *<tt>C:\program files\steam\steamapps\bailopan\counter-strike source\cstrike\cfg</tt> | ||
| + | |||
| + | You can also set the password upon connecting. For steam and IP authentication, your admin privileges will be automatically assigned if the password is correct. For name based authentication, your password must be correct before you change your name, or else you will be kicked from the server. | ||
[[Category:SourceMod Documentation]] | [[Category:SourceMod Documentation]] | ||
Revision as of 14:23, 24 July 2007
SourceMod has as very detailed and flexible administration system, and it can be quite daunting to users. To simplify things, there are a number of "flags" which specify generic permissions administrators can have.
Aside from that, there are (currently) two provided ways of storing admins. One via a simplified flat file, and another via a more complex tree-based file.
SourceMod provides three methods of authentication by default:
- Steam ID (unique to a Steam account)
- IP Address (semi-unique to a given computer, better for LANs)
- Name (requires a password, and is this unique to that password)
Contents
Levels
First, let's quickly run down the provided levels:
Name Flag Purpose reservation a Reserved slot access. generic b Generic admin; required for admins. kick c Kick other players. ban d Ban other players. unban e Remove bans. slay f Slay/harm other players. map g Change the map or major gameplay features. cvar h Change most cvars. config i Execute config files. chat j Special chat privileges. vote k Start or create votes. password l Set a password on the server. rcon m Use RCON commands. cheats m Change sv_cheats or use cheating commands. root z Magically enables all flags.
Immunity
There is no immunity flag. Instead, there are three types of immunity:
- Default immunity; immunity from admins who do not have default immunity.
- Global immunity; immunity from admins who do not have global or default immunity.
- Specific immunity; immunity from a specific group (see advanced section).
Simple Admins
The easiest way to add administrators is through configs/admins_simple.ini. This is a flat file which requires two parameters per line: authentication info, and flags.
Three examples are provided:
"STEAM_0:1:16" "bce" //kick, ban, slay for this steam ID "127.0.0.1" "z" //all permissions for this ip "BAILOPAN" "abc" "Gab3n" //name BAILOPAN, password "Gab3n": gets reservation, kick, ban
Passwords
For passwords to work, the server administrator must change the "PassInfoVar" line in addons/sourcemod/configs/core.cfg. For example:
"PassInfoVar" "_sm1337"
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, BAILOPAN would need to type:
setinfo "_sm1337" "Gab3n"
To automate this upon connecting to a server, you can create an "autoexec.cfg" file in your client cstrike folder. This will be located under SteamApps\ACCOUNT\Counter-Strike Source\cstrike\cfg. For example:
- C:\program files\steam\steamapps\bailopan\counter-strike source\cstrike\cfg
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.
