The users.ini file in your addons/amx/config folder is where players are given admin priviledges under AMX. It contains the different levels of admin access for a default install. Below are some examples of how to set up admin access for your admins.
The first part of the users.ini file is labeled "Access Flags". These letters will define what commands your admins will have access to:
The next part of the users.ini is labeled "Account Flags". These options control how the user is authenticated:
The last part is only required if your server is a listen serverDedicated Server:
The
server runs in a text console and was a seperate download apart from
the client. Or it has been run from the Dedicated Server entry in Steam.
Listen Server:
You start up your client and then start the server from the in-game menu, then others connect to you.. This will allow you to have admin access while running the server.
The format of the entry for each admin is this:
This is not the best way to grant admin access. It requires the client to set a password on their end. Many players can do this, however many do not grasp the concept of editing config files let alone with the correct info. It's a burden on the person setting up the access and the person receiving it in the end, and there is no added security with this method over access by SteamID.
Above is what you do on the server's side. The client must have the password entered on their side also. To do that, create a file in your mod (ie. cstrike, dod) folder called userconfig.cfg if you don't already have one. Have the client put setinfo _pw "password" in it. For example:
The password field and password should match what you have on the server. For more info on this, go here.
You would want to use this method only if you are connecting to a server on a LANLocal Arena Network. On a LAN without internet access, players will not have unique SteamID's. So this method allows you to assign admin rights to your computer's address instead. If the IP is dynamic, then this could change though so keep that in mind.
This is the method I prefer. Admin access is set up for the clients with this one line. The client doesn't have to do anything. Once you get the player's SteamID, that's all that is needed. You don't even need a password since your SteamID is yours and no one else can have it unless your CD-Key gets out.
I am going to use my preferred method shown above. While a reserved slot does not allow players to perform admin commands on others, it is still set up like any other admin would be set up, but with just one flag.
Now if all the players mentioned above were in the same users.ini file it would look like this:
I like to use comments in config files and use of the TAB key keeps things formatted nicely too. Sometimes you can forget who some people are if they change their player name a lot. So comments at the end of a line can be useful in adding more details about the person. Use a semi-colon ";" at the beginning of a comment in .ini files. What ever is after the ";" is ignored by AMX.