This guide shows you how to remove a troublesome player from your Palworld dedicated server, either temporarily (kick) or permanently (ban). You’ll need access to the server’s console or its configuration files, depending on how your server is hosted. The steps below cover both official dedicated servers and common third-party hosting panels.
What You’ll Need
- Access to the server console (if self-hosted) or the hosting provider’s control panel.
- The player’s in-game name or their Steam ID (64-bit). You can find this in the server logs or by using the in-game command
ShowPlayers. - Administrator privileges on the server (usually the server owner or someone with admin rights).
Step-by-Step
- Open the server console. If you’re running a dedicated server on your own machine, open the command prompt window where the server is running. If you’re using a hosting panel (like a game server control panel), look for a “Console” or “Terminal” tab.
- Identify the player. Type
ShowPlayersin the console and press Enter. This lists all connected players with their Steam ID and in-game name. Note the Steam ID of the player you want to kick or ban. If you can’t access the console, check the server logs (usually in aLogsfolder) for player join/leave messages that include the Steam ID. - To kick a player: Type
KickPlayer <SteamID>(replace<SteamID>with the actual 64-bit Steam ID) and press Enter. The player is immediately disconnected. They can rejoin unless you ban them. - To ban a player: Type
BanPlayer <SteamID>and press Enter. The player is disconnected and added to the server’s ban list. They won’t be able to join again unless you unban them. - Confirm the action. The console should output a confirmation message. You can also run
ShowPlayersagain to verify the player is gone. - Alternative method via config file (for permanent bans): If you can’t use the console, you can edit the
banlist.txtfile located in the server’sPal/Saved/Config/LinuxServer/directory (orWindowsServeron Windows). Add the Steam ID on a new line, save the file, and restart the server. This is a manual way to ban players.
Common Mistakes
- Using the wrong ID: The commands require the 64-bit Steam ID, not the player’s display name or the shorter 32-bit ID. Using the wrong ID will either fail or kick/ban the wrong person.
- Typing the command incorrectly: The commands are case-sensitive. Make sure you type
KickPlayerandBanPlayerexactly as shown, with no spaces. - Not having admin rights: On some hosting panels, you must first grant yourself admin rights in the server settings or use a special admin command. Without admin rights, the kick/ban commands will be ignored.
- Editing the banlist while the server is running: If you edit
banlist.txtwhile the server is running, the changes may be overwritten when the server saves. Always stop the server, edit the file, then restart.
Tips
- Kick first, ban later: If you’re unsure, kick the player first. If they come back and continue the behavior, then ban them.
- Communicate with your community: Let your players know the rules and that violations can lead to kicks or bans. This reduces the need for moderation.
- Keep a backup of your banlist: If you need to reinstall the server, you can restore the banlist to keep banned players out.
- Use the in-game admin menu (if available): Some server setups allow admins to kick/ban from the in-game pause menu. Check your server’s documentation for this option.
Troubleshooting
Command not recognized: If you type KickPlayer and get an error, make sure you have the latest server version. Also, check if your hosting provider uses a custom command (e.g., kick or ban). Consult your host’s documentation.
Player not found: If the command says “Player not found,” double-check the Steam ID. It must be the 64-bit ID (usually starts with 7656…). You can find it in the server logs or by using a Steam ID lookup tool.
Player reconnects after ban: If a banned player rejoins, your banlist may not have been saved. Ensure you use the BanPlayer command (not just kick), and if you’re editing the file manually, make sure the server is stopped and the file is saved correctly.
No console access: If you don’t have console access (e.g., you’re renting a server without a control panel), you may need to contact your hosting provider to run the command for you. Some providers offer a web-based console in their panel.
Banlist file not found: If you can’t find banlist.txt, it may not exist yet. Create a new text file named banlist.txt in the correct directory and add the Steam IDs, one per line.
Frequently Asked Questions
Can I kick a player by their in-game name?
No, the kick and ban commands require the 64-bit Steam ID. You can find the ID using the ShowPlayers command or in the server logs.
How do I unban a player?
To unban, type UnbanPlayer <SteamID> in the console, or remove the Steam ID from the banlist.txt file and restart the server.
Will a kicked player lose their items or progress?
No, kicking only disconnects them. Their character and base remain as they were. Banning also does not delete their data; they just can’t join.
Can I ban a player from the in-game chat?
No, the in-game chat does not support ban commands. You must use the server console or the hosting panel.
What is the difference between kick and ban?
A kick is temporary—the player can rejoin immediately. A ban is permanent (until you unban) and prevents them from joining.
Do I need to be the server owner to ban?
Typically yes, you need admin privileges. On some servers, you can grant admin to other players via the AdminPassword setting in the PalWorldSettings.ini file.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- Credential Manager: Seamless Sign-In Explained
- API Governance for Public Data: What Growing Portfolios Need
- Enterprise AI Hidden Cost: Data Architecture ROI