Palworld Common Issues

Cannot Connect to Server

Copy the Server Address exactly from Connection Info on the server Overview tab. GameGrid allocates the port from its own 28000-39000 pool, so it is not Palworld's stock 8211.

Make sure the server is running (green "Online" status on your Dashboard).

If you set a Server Password, players must enter it correctly. It is blank by default.

Check Crossplay Platforms in Settings. All four platforms (Steam, Xbox, PS5 and Mac) are allowed by default, so if a friend on one platform is refused, check that their platform has not been unticked, then save and restart.

Check that Maximum Players is not reached. The default and the engine cap are both 32.

If using the community server list, give a new server several minutes to register. The in-game browser only shows the first 200 results, so have players search the exact name.

Console players (Xbox, PS5) can only join via the community server list - they cannot type an address.

World Save Corruption

Symptoms: server crashes on startup, players spawn in the void, structures disappear.

First, restore the most recent backup from the Backups tab. Only a backup in the "verified" state offers a Restore button.

If the world will not load but the files look intact, use "Verify & Repair" on the Admin tab. It checks the game files against the known-good manifest and repairs corrupt or missing ones. It does not touch your save.

WorldOption.sav is a settings snapshot, not a corruption cause. Do not delete it while chasing a corrupt world - see the WorldOption.sav guide for what it actually does.

To prevent corruption: always use Stop (not a force-kill) to shut down; Palworld gets a 90-second graceful budget here so a large world finishes writing. Never edit save files while the server is running. GameGrid servers use SSDs, which Palworld's own documentation asks for.

High Ping or Lag

Check the player count - Palworld servers get laggy well before the 32-player cap.

Lower Pal Spawn Rate in Settings to reduce the number of entities the server simulates. Pal Capture Rate does not affect load; it only changes how easily Pals are caught.

Lower Workers per Base (default 15) to reduce base simulation. If that change refuses to stick, see the WorldOption.sav guide.

Turn Invading Enemies off - the panel's own description warns of memory growth over long uptimes with it on.

Restart on a schedule. The "Automatic Daily Restart" card on the Admin tab offers 6, 12 or 24 hours and only fires when nobody is connected.

Every one of those needs a server restart to take effect.

Run a WinMTR report (see the Platform Guides section) to check for network issues between you and the server.