Kick or ban a player
Remove a disruptive player from the server, and decide how long they stay off.
You need clerical admin to kick.
Banning is leadership admin only.
In the menus: ESC → Direct → Tools → Online and Origin
Kicking a player
Select a row and press KICK. It kicks with the reason "Kicked by an admin"; the console form lets you write your own.
A stock kick blocks the player's address and, when available, their real game GUID from reconnecting for 10 minutes.
A server admin can change the duration with sf_kickbantime. Setting it to 0 kicks the player without a reconnect block.
Everybody on the server is told, in the chat:
The player is disconnected with a reason naming the kick, the minutes and whatever you typed.
Banning a player
A ban is permanent. It records the port-stripped address and, when available, the player's real game GUID. Either one can reject a reconnect.
The ban is saved in bannedips.cfg, restored after a server restart, and remains in /sfban list until removed.
This does not disable the StoryForce account. Changing networks alone may not evade it because the GUID can still match. To stop the account itself, use disable and restore an account.
The first line is public. Only the leadership admin sees the second confirmation.
Banning somebody who has already left
A player who has disconnected no longer has a client number.
/sfban recent lists who left most recently, and /sfban recent <#> [reason] bans by list position.
Lifting a ban or a kick block
/sfban list pages permanent bans with their numbers.
/sfban remove <ip|#> takes a saved ban number or an exact address.