Introduction
The TAC userlist allows the server admin to designate different passwords and access levels to as many players as the admin likes. The easiest way to start this instruction is to provide some frequently asked questions and the answers to them:
TAC Userlist Frequently Asked Questions
In TAC, can I have a username with a space or other strange characters in it?
Yes. The TAC Userlist fully accepts all characters. The only characters that may not be used in an admin name is " and { }How many admin classes are there in TAC?
Unlimited. The server admin can create 999999 different admin classes, if he so wishes, all with different abilities.Can I have an admin class that is automatically verified on connection to the server and does not have to type in a SAD password?
Yes. This is one of the options that are selectable to an admin class but is only advisable if the player has a static (fixed) ip for security reasons.
- Can I have an admin password that will work for any player?
- Yes. We call this a Group Admin Password.
Do I have to use the userlist if I dont want to?
No. Like everything else in TAC, it is fully customizable. You can simply change one option to disable it.
Setting up the TAC Userlist
When you have installed TAC the TACUserlist.cs file SHOULD have extracted into the tribes/TAC directory. If it is not there then move it there now.
$UserList::Activated = 0;
This item designates whether you are using the userlist or not. If a value of 0 (default) is set here then the userlist will be totally ignored. Place a value of 1 here if you wish to use the userlist.$UserList::MaxClasses = 6;
This item specifies the total number of admin "classes" you are going to allow on your server. (IMPORTANT: If this is incorrect this will cause major problems and the userlist will not work)$UserList::MaxUsers = 2;
This item specifies the total number of players that have admin passwords in your userlist. Having an incorrect number here will cause the userlist to cease functioning and this is the most common cause of admin verification problems. If you ever have any problems....look here first :)
- $UserList::MaxGroups = 1;
- This item specifies the total number of group passwords that has been defined in the userlist.
Setting up the TAC Admin Classes
Listed below is a sample admin class. As you can see it would be number 3 in the list.
$UserList::AdminName[1] = "RefAdmin";
$UserList::AdminIsImmune[1] = false;
$UserList::AdminGeneral[1] = true;
$UserList::AdminServerSettings[1] = false;
$UserList::AdminCanAdminPlayer[1] = true;
$UserList::AdminReferee[1] = true;
$Userlist::AdminAutoLogin[1] = false;For each admin setting you will need to specify true or false to each of the seven options. In this case, a "RefAdmin" only has access to be able to use the general admin settings, admin players and use the referee options. He cannot password the server and is not immune to anti-TK effects. I will now explain in detail each setting.
$UserList::AdminName
Obviously, this simply specifys the name of the admin class. If it is called "RefAdmin" as above, then the player would be designated a ref admin in the userlist. (refer below)$UserList::AdminIsImmune
Allowing a class to be "immune" will make any member of that class invulnerable to purgatory, kicking, warning, gagging or banning. They will still suffer the effects of reverse damage and muting though.$UserList::AdminGeneral
Basic General Admin abilities. This class can change missions, set the time limit and change the server damage mode as well as player specific effects such as putting a player in purgatory, kicking, warning, gagging a player or changing a players team. Note: If a class is to be set up that has more than just AdminGeneral abilities, the class should always include AdminGeneral Access as well.$UserList::AdminServerSettings
This class has access to password the server and change other server settings.$UserList::AdminReferee
An admin with this access can use tournament or league modes, may force the start of a match, may set team names and skins and generally have full control over a match.$Userlist::AdminAutoLogin
This class is automatically logged in upon connecting to the server. They do not need to type in a SAD password although they do still have one and can still use it if they somehow get de-adminned.OK, so hopefully you now have your admin classes set up :)
Setting up the TAC Users
Listed below is a two sample admin users. As you can see, they would be number 1 and 5 on the list respectively.
$UserList::UserName[1] = "Wizard TPG";
$UserList::UserPass[1] = "mypass";
$UserList::UserLevel[1] = "SuperAdmin";
$UserList::UserIP1[1] = "139.130.79.150";
$UserList::UserIP2[1] = "198.142.*.*";
$UserList::UserIP3[1] = "203.*.*.*";$UserList::UserName[5] = "[TPG]SaNTa[DTM]";
$UserList::UserPass[5] = "rudolf";
$UserList::UserLevel[5] = "RefAdmin";
$UserList::UserIP1[5] = "*.*.*.*";Upon connection to a server, a players username is checked against the list for a possible match. If the name matches it will then be checked for a matching ip address. This means that BOTH the username and the ip address must match for a player's admin to verify correctly. (Before we go any further, it should be noted that as IPX network users on a lan to not have an ip address, the userlist will not work for them.)
$UserList::UserName
This has to be EXACT. Any characters except " may be used. Spaces will work fine in the username.$UserList::UserPass
The players password they will use in the server to login. eg. SAD("mypass");. Unless a player is in an admin class that has AdminAutoLogin they will not get their admin features until they log in.$UserList::UserLevel
The admin class name we defined earlier.$UserList::UserIP1, $UserList::UserIP2 & $UserList::UserIP3
Only UserIP1 is REQUIRED. UserIP2 and UserIP3 can be added if the player has a number of different ip ranges (ie. different isps). * is used as a wildcard in the ip address ranges. eg. 203.152.*.* is the same as 203.152.50.23 or 203.152.84.4
Setting up the TAC Groups
Listed below is a sample admin group password.
$UserList::GroupPass[1] = "refpass";
$UserList::GroupLevel[1] = "RefAdmin";This list allows the server admin to define a password that ANY player can use, irrespective of name or ip address. WARNING: Use this feature at your own risk as it IS a security risk to distribute a global group password.
$UserList::GroupPass
The password. All the group passwords MUST be different.$UserList::GroupLevel
The admin class name we defined earlier.
So now we got all that sorted out. There is a couple of inbuilt SAD passwords to display special information about the players user status
SAD("deadmin");
This will simply remove ALL admin abilitys and return you to a normal player. An admin doing this can relogin using his/her normal SAD.SAD("mystats");
Displays a text readout of your current admin abilities.
Tricon and telnet adminning
Adminning through tricon and telnet will still only allow you to grant admin and superadmin status.
If a player is granted admin through tricon he/she will get AdminGeneral access.
If a player is granted superadmin through tricon he/she will recieve all access listed above. This should not be given out lightly.