Managing Remote Client Users
From SOPWiki
| Revision as of 06:17, 28 August 2007 (edit) Drunken F00l (Talk | contribs) ← Previous diff |
Current revision (18:34, 6 October 2010) (edit) (undo) Drunken F00l (Talk | contribs) (Updated permission set) |
||
| (One intermediate revision not shown.) | |||
| Line 12: | Line 12: | ||
| The 'a' means that the player is able to view the player list. To give the admin full access, put the following lines below the password line: | The 'a' means that the player is able to view the player list. To give the admin full access, put the following lines below the password line: | ||
| <source lang="text"> | <source lang="text"> | ||
| - | Players = abcdefghijklmn | + | Players = abcdefghijklmno |
| AdminInfo = ab | AdminInfo = ab | ||
| - | Chat = abcdef | + | Chat = abcdefgh |
| - | Administrative = abcdefghijklmnopq | + | Administrative = abcdefghijklmnopqrst |
| </source> | </source> | ||
| Line 23: | Line 23: | ||
| Save the file and then add the admin to the "list" text file on its own line. The list.txt file just contains a list of all the admins, each on their own line, and is used by the [[Using_the_Remote_Client#Edit_Admin|Edit Admin]] window. Only admins in this list will appear in the Edit Admin window. | Save the file and then add the admin to the "list" text file on its own line. The list.txt file just contains a list of all the admins, each on their own line, and is used by the [[Using_the_Remote_Client#Edit_Admin|Edit Admin]] window. Only admins in this list will appear in the Edit Admin window. | ||
| + | |||
| + | Any changes you make to an admin's file will take effect the next time that the admin connects. | ||
| == Permissions == | == Permissions == | ||
| + | Note that some permissions are unimplemented and are planned to be implemented later. | ||
| === Players === | === Players === | ||
| *a: Can view players (required for anything else in category) | *a: Can view players (required for anything else in category) | ||
| Line 40: | Line 43: | ||
| *m: Can set a player's health | *m: Can set a player's health | ||
| *n: Can set a player's team | *n: Can set a player's team | ||
| + | *o: Can gag players | ||
| === AdminInfo === | === AdminInfo === | ||
| Line 52: | Line 56: | ||
| *e: Can private message players | *e: Can private message players | ||
| *f: Can private message admins | *f: Can private message admins | ||
| + | *g: Can send center says | ||
| + | *h: Can send bottom says | ||
| === Administrative === | === Administrative === | ||
| Line 71: | Line 77: | ||
| *p: Can view server password (Requires view settings) | *p: Can view server password (Requires view settings) | ||
| *q: Can set server password (Requires change settings) | *q: Can set server password (Requires change settings) | ||
| + | *r: Can view banned players list | ||
| + | *s: Can make modifications to banned players list (Requires view bans) | ||
| + | *t: Can view server logs | ||
Current revision
Contents |
[edit] Creating a new User
All users have a .txt file in the {gamedir}\addons\SourceOP\users folder. To create a new user, create a new text file (.txt file). The name of the text file should be user name for the admin. For example, creating a text file called "Drunken F00l" (leave the .txt extension if you see one) will allow an admin using the user name Drunken F00l to connect.
Now, open the file. On the first line, type the password for the admin. Then, on the lines below you put the admin's permissions. There are four permission categories: Players, AdminInfo, Chat, and Administrative. In each category, there are letters that represent a permission. See here for permissions. For example, to make the admin only be able to view the player list, put the following line below the password:
Players = a
The 'a' means that the player is able to view the player list. To give the admin full access, put the following lines below the password line:
Players = abcdefghijklmno AdminInfo = ab Chat = abcdefgh Administrative = abcdefghijklmnopqrst
After adding the admin permissions, the file should look something like this:
Save the file and then add the admin to the "list" text file on its own line. The list.txt file just contains a list of all the admins, each on their own line, and is used by the Edit Admin window. Only admins in this list will appear in the Edit Admin window.
Any changes you make to an admin's file will take effect the next time that the admin connects.
[edit] Permissions
Note that some permissions are unimplemented and are planned to be implemented later.
[edit] Players
- a: Can view players (required for anything else in category)
- b: Can kick players
- c: Can ban players
- d: Can give players god
- e: Can give players noclip
- f: Can give players quad
- g: Can give players credits
- h: Can slap players
- i: Can slay players
- j: Can give players guns
- k: Can open map and view players
- l: Can drag players on map
- m: Can set a player's health
- n: Can set a player's team
- o: Can gag players
[edit] AdminInfo
- a: Can view connected admins (required for anything else in category)
- b: Can view a connected admin's info
[edit] Chat
- a: Can view player chat
- b: Can send player chat
- c: Can view admin chat
- d: Can send admin chat
- e: Can private message players
- f: Can private message admins
- g: Can send center says
- h: Can send bottom says
[edit] Administrative
- a: Can view user list (required for any user editing)
- b: Can view user passwords
- c: Can view user permissions (required to edit perimssions)
- d: Can edit user passwords
- e: Can edit user permissions
- f: Can delete users
- g: Can add users
- h: Can view player database
- i: Can edit player database (Requires view player database)
- j: Can view/send RCON
- k: Can spawn items on map
- l: Can view map list
- m: Can change map
- n: Can view settings (Cvars)
- o: Can change settings
- p: Can view server password (Requires view settings)
- q: Can set server password (Requires change settings)
- r: Can view banned players list
- s: Can make modifications to banned players list (Requires view bans)
- t: Can view server logs
