How to Kick and Ban Players on Your Quake Live Server ​
You remove players through the console of your server in the dashboard, or directly in the game if you hold admin or moderator rights there.
Note
To learn how to grant rights to yourself and other players, see Add Admin.
Find the client ID ​
All of the commands below expect the client ID — the number the server assigns to a connected player.
Connect to your server
Connect to your server in the game and open the console there.List the players
Enter the following command:/playersThe output shows every connected player with their client ID and their SteamID64.
Note
In the console of your server you enter the commands without a leading /. In the game you use the same commands with a leading /, for example /tempban 3.
Remove a player ​
Quake Live has no dedicated kick command. To remove a player, use tempban instead:
tempban 3The player is removed from the server and cannot rejoin until the current map ends. After that, access is open again.
Warning
Widely circulated forms such as kick <PlayerName> do not work on a Quake Live server — there is no kick command, neither in the server console nor in the game. A kick is only available as a player vote (callvote kick or callvote clientkick). As an admin you remove players with tempban or ban.
Ban a player ​
ban 3The player is removed immediately and locked out permanently. The ban is stored in the file /baseq3/access.txt, in the same format as the admin rights:
76561198012345678|banLift a ban ​
If the player is still connected or is trying to reconnect, you can lift the ban directly from the console:
unban 3For a player who is not on the server, remove the entry from the file instead:
Stop the server
Stop your server via the dashboard.Connect via SFTP
Connect to your server via SFTP.Edit access.txt
Open the following file and delete the line containing the affected SteamID64 with the suffix|ban:/baseq3/access.txtStart the server
Save the file and start your server.
Important
Only edit access.txt while the server is stopped. The server rewrites the list before every map load — changes made while the server is running are lost in the process.
Command overview ​
| Command | Description |
|---|---|
/players (in game) | Show connected players with their client ID and SteamID64 |
tempban <client ID> | Remove a player from the server until the map ends |
ban <client ID> | Ban a player permanently |
unban <client ID> | Lift a ban |
mute <client ID> | Mute a player |
unmute <client ID> | Unmute a player |
put <client ID> <red|blue|spectator> | Move a player to a team or to the spectators |
lock [team] / unlock [team] | Lock or unlock teams |
pause / unpause | Pause and resume the match |
forceshuffle | Shuffle the teams |
opsay <text> | Send a message to all players as the server operator |
map <map> <factory> | Change the map and the game mode |
quit | Shut down the server |
Restrict kick votes ​
Players can put each other up for a vote with callvote kick. You can prevent that.
Stop the server
Stop your server via the dashboard.Open server.cfg
Open the following file via SFTP:/baseq3/server.cfgDisable the vote
Forg_voteFlagsyou add up the values of the votes you want to block. Kick votes have the value16:set g_voteFlags "16"If you want to disable voting entirely, set the following instead:
set g_allowVote "0"Start the server
Save the file and start your server.
Values for g_voteFlags
| Value | Blocked vote |
|---|---|
1 | map |
2 | map_restart |
4 | nextmap |
8 | gametype (factory argument for callvote map) |
16 | kick |
32 | timelimit |
64 | fraglimit |
128 | shuffle |
256 | teamsize |
512 | cointoss/random |
1024 | loadouts |
2048 | end-game voting |
4096 | ammo (global) |
8192 | timers (item) |
To block kick and map votes, for example, you calculate 16 + 1 = 17.