You should learn kick player by
userID.
Player could change name so it's harder to track.
Player userID not change until player re-connect to server.
Code:
] status
hostname: 'Bacardi
version : 1.37.8.5/13785 1250/8012 secure [A:1:2425885697:16835]
udp/ip : 192.168.1.21:27015
os : Windows
type : listen
map : de_dust2 at: 182 x, 2439 y, -56 z
connected to loopback
players : 1 humans, 9 bots (20/0 max) (not hibernating)
# userid name uniqueid connected ping loss state rate adr
# 2 1 "'Bacardi" STEAM_1:1:14163588 00:15 16 0 active 786000 loopback
# 3 "Paul" BOT active 64
# 4 "Bill" BOT active 64
# 5 "Jerry" BOT active 64
# 6 "Colin" BOT active 64
# 7 "Matt" BOT active 64
# 8 "Ron" BOT active 64
# 9 "Pat" BOT active 64
#10 "Tom" BOT active 64
#11 "Norm" BOT active 64
#end
] users
<slot:userid:"name">
0:2:"'Bacardi"
1:3:"Paul"
2:4:"Bill"
3:5:"Jerry"
4:6:"Colin"
5:7:"Matt"
6:8:"Ron"
7:9:"Pat"
8:10:"Tom"
9:11:"Norm"
10 users
Code:
rcon kickid 2
sm_kick #2
You can also kick player by aim to him.
sm_kick @aim