Need to stop a griefer fast? Palworld lets you kick or ban with precise commands. Here’s exactly what to type, where to click, and how to avoid common mistakes.
Pal/Saved/Config/WindowsServer/PalWorldSettings.ini via AdminPassword="your_pass"8211/UDP)banlist.txt/AdminPassword your_admin_pass exactly, then confirm you see the acceptance message. If not, the password is wrong or mistyped. Next, list connected players with /ShowPlayers to grab their PlayerUID and SteamID. Example output lines include UID=123456789, SteamID=76561198000000000, Name=PlayerX.
/KickPlayer PlayerUID. Replace PlayerUID with the exact UID from /ShowPlayers (e.g., /KickPlayer 123456789). The player is disconnected immediately but can rejoin. If you see “Player not found”, rerun /ShowPlayers (UIDs can change after reconnects) and check for extra spaces. Kicking is perfect for a quick warning.
/BanPlayer PlayerUID to block access long-term (e.g., /BanPlayer 123456789). Some servers also accept SteamID64: /BanPlayer 76561198000000000 (prefer UID when available to avoid ambiguity). Ask the player to try reconnecting to confirm the ban is active. If you get “Unknown command”, you’re not admin yet (redo /AdminPassword ...) or the command is misspelled.
ShowPlayers to list, KickPlayer 123456789 to kick, BanPlayer 123456789 to ban. Hit Enter and watch the log for confirmation. If nothing happens, ensure the server is “Online” and that you didn’t include a slash.
Pal/Saved/SaveGames and open banlist.txt (create it if missing). Add one player per line using the exact format steam_SteamID64 (e.g., steam_76561198000000000). Save, then start the server so the list loads on boot. If the ban fails, check the steam_ prefix and remove trailing spaces.
Pal/Saved/SaveGames/banlist.txt. Remove the line (e.g., delete steam_76561198000000000) and save. Start the server to apply. Depending on your version, you may try UnbanPlayer 76561198000000000 in console; if you see “Unknown command”, use the file method.
– Keep a small sheet mapping Name ↔ UID ↔ SteamID64 to avoid targeting the wrong player.
– Use a strong admin password (12+ chars, mixed set) to prevent abuse.
– Back up banlist.txt before edits so you can roll back instantly.
– Prefer UID when banning via commands to reduce ambiguity with similar names.
– After moderation actions, run Save in console to force a clean server save.
In-game, you must run /AdminPassword your_admin_pass and see the success message. In the panel console, never use a slash (e.g., BanPlayer 123456789). Double-check the exact command spelling and the UID via ShowPlayers. Also ensure the server is running.
Kick disconnects now but allows rejoin. Ban blocks the player from reconnecting until removed from banlist.txt or the server’s ban record. Use ban for persistent sanctions.
Live: use /ShowPlayers to view UID and sometimes SteamID. Offline: ask for the player’s Steam profile URL and use a SteamID → SteamID64 converter. Then add steam_SteamID64 to banlist.txt.
You’re set to moderate your Palworld server like a pro. Keep these commands handy, stay consistent, and your community will thrive.