As a HumanitZ server admin, you have powerful tools at your disposal to keep your community safe and enjoyable. Whether you need to remove a disruptive player, issue a permanent ban, or manage roles across your server, this guide walks you through everything you need to know — step by step.
Before you can kick or ban players, you must activate admin privileges in-game. Connect to your server, press Enter to open the chat, and type /AdminAccess [YourPassword]. Your admin password is defined in your server’s GameServerSettings.ini configuration file. Once granted, you’ll have access to all moderation and player management commands.
To kick a player, use the command /kick [PlayerName] directly in the in-game chat. A kick is a non-persistent removal — it disconnects the player from the server immediately but does not prevent them from reconnecting. Use kicks for minor disruptions, temporary rule violations, or desync issues. Always include a reason when possible for transparency and documentation.
To permanently ban a player, you can use RCON commands remotely or manually edit the F_BannedPlayers.txt file on your server. Add the offending player’s SteamID64 on a new line in that file — one ID per line — then save. This adds them to the permanent banlist and blocks all future reconnection attempts using that Steam account.
Need to reverse a ban? You can unban a player by either manually removing their SteamID64 from the F_BannedPlayers.txt file or by running the appropriate unban command via RCON. This gives server owners full control over who is allowed to play, with the flexibility to correct mistakes or reinstate players after an appeal.
HumanitZ supports tiered admin permissions, allowing you to separate full administrators from moderators. Administrators handle server configuration and world-altering commands, while moderators focus on player management tasks such as kicks, temporary bans, and behavior monitoring. Permissions are assigned via server configuration files or admin lists that map player identifiers to roles.
When targeting a player with any moderation command, HumanitZ resolves players using one of three identifiers: in-game name, session ID, or SteamID64. For bans and whitelist enforcement, always use the SteamID64, as these actions must survive server restarts and reconnects. For live actions like kicks, a session ID or in-game name is sufficient — but confirm the correct player first to avoid mistakes.
Beyond banning and kicking, HumanitZ admins can access the /adminw panel for advanced server management, use /SuperAdmin to monitor the server invisibly, issue a timed /Shutdown [SECONDS] to notify all players before a restart, and toggle /god mode for testing. All admin actions should be intentional, justified, and logged to maintain a fair and thriving server community.