Palworld 1.0 dedicated servers can allow Steam, Xbox, PlayStation 5 and Mac players, but the server must use the correct join method. Pocketpair's current documentation lists CrossplayPlatforms=(Steam,Xbox,PS5,Mac) by default. Xbox and PS5 players need the server to be registered as a community server; a private IP-and-port-only dedicated server is not the same thing. Older guides describing PS5 server crossplay as unavailable or using AllowConnectPlatform refer to earlier versions.
Why can't Xbox or PS5 players join my Palworld dedicated server?
Start with the server type. Pocketpair distinguishes dedicated servers, which players on supported PC editions can connect to by entering an IP address and port, from community servers, which also register in the in-game list. Its current server overview explicitly requires a community server for Xbox and PS5. Running a dedicated server process without listing it as a community server is not enough for those console players.
How do you enable community server listing?
- Stop the Palworld dedicated-server process and back up its save and configuration before editing.
- When launching with Steam, choose the community server start option. If using SteamCMD or a standalone executable, include the command-line switch
-publiclobby. - Restart the server and confirm its public name is visible in the in-game community-server browser from an external client.
- Have Xbox and PS5 users locate the listing in their server browser rather than attempting to connect using a raw IP address.
Pocketpair's community-server instructions show the startup argument PalServer.exe -publiclobby on Windows or ./PalServer.sh -publiclobby on Linux. It also warns that a router without hairpin NAT can prevent someone on the host's own network from connecting to the public listing. Have a player outside that network test discoverability rather than assuming an external outage from a local failure.
Which Palworld crossplay setting is current?
In the current 1.0.2 documentation, the allowed-platform list is controlled by CrossplayPlatforms, which defaults to (Steam,Xbox,PS5,Mac). The old AllowConnectPlatform parameter is explicitly marked as no longer functional. If you migrated an older server, review the working PalWorldSettings.ini rather than copying an old AllowConnectPlatform=Xbox example.
The server configuration file is under Pal/Saved/Config/WindowsServer/PalWorldSettings.ini on Windows and Pal/Saved/Config/LinuxServer/PalWorldSettings.ini on Linux. Copy DefaultPalWorldSettings.ini to the correct location when first setting it up, but editing the Default file itself does not apply live settings. The official configuration reference documents both the paths and the supported platform list.
Which server and network settings can prevent connection?
- Server not running or build mismatch: Update the game server and clients to compatible versions before further troubleshooting.
- No community listing: Check
-publiclobbyfirst, particularly if the only affected players are on Xbox or PS5. - Incorrect public address: For community servers,
PublicIPandPublicPortcan describe the externally reachable endpoint. PublicPort does not change the server's actual listening port. - Port or firewall problem: The documented default listen port is 8211. If you changed it using
-port=, update the host firewall, router and hosting-provider rules to match that chosen port. - Local NAT test fails: A same-LAN connection may fail even while the server is reachable externally. Test from a separate network.
- Disallowed platform: Check that the relevant store/platform entry is included in
CrossplayPlatforms.
Pocketpair separates server list visibility from the actual listening port in its launch-argument documentation. A visible listing does not establish that network traffic can reach your game process. Do not publicly expose administrative API or RCON ports as a general fix for joining.
Where do I find full Palworld hosting instructions?
Our Palworld 1.0 dedicated-server setup guide covers installation. For file formats and port settings, see Palworld server configuration explained. This article focuses on troubleshooting mixed-platform access rather than repeating the full installation process.