Server Checklist

Palworld 1.0 Server Owner Checklist

Palworld 1.0 server owner checklist for backups, MOD cleanup, version matching, settings review, save testing, guild permissions, voice chat, and safe reopening.

Short answer

Before reopening a Palworld 1.0 server, back up the complete world, remove unsupported MODs, update server and clients, review changed defaults, test saving and restart persistence, verify guild permissions, and document rollback rules.

Practical advice for new and returning players

  • Use a copy of the production world for the first Version 1.0 test whenever possible.
  • Do not raise capacity or base load only because the changelog mentions optimization.
  • Tell players whether the world is continuing, fresh, temporary, or subject to rollback before they join.

Before the update

  • Stop the server cleanly.
  • Back up world data, player data, configuration, startup arguments, and management files.
  • Record the current build, MODs, plugins, and server tools.
  • Store the backup outside the active server directory.
  • Announce the maintenance window and rollback policy.

MOD cleanup

  • Remove old MOD files and loaders manually rather than only disabling them.
  • Unsubscribe from Workshop MODs and verify game files where applicable.
  • Confirm the server and a test client run unmodded.
  • Restore only creator-confirmed Version 1.0 MODs, one at a time.

Version and configuration check

  • Update the dedicated server and confirm clients use a compatible Version 1.0 build.
  • Compare the old configuration with the current file and changed defaults.
  • Review progression, capture, death, base, raid, PvP, access, and communication settings.
  • Keep the original configuration with the pre-update backup.

Private smoke test

  • Join with at least two test clients.
  • Confirm character loading, spawn location, password behavior, and guild membership.
  • Access a representative base, move items, assign a Pal, and verify role permissions.
  • Save, log out, restart the server, reconnect, and confirm persistence.
  • Run a longer session before calling the server stable. Needs in-game verification.

Multiplayer features to review

Version 1.0 adds optional dedicated-server voice chat, expanded guild roles and permissions, guild markers, improved chat, server-list changes, password and IP-entry improvements, unstable-connection indicators, and optional Discord integration on supported versions.

Enable only the features the community needs, then test permissions and platform support before public access.

Do not assume optimization equals capacity

Pocketpair confirms optimization for dedicated servers, memory, dense placed objects, spawn points, and other high-load processing. It does not publish a universal safe player count, base count, or object limit.

Capacity, restart frequency, long-session memory behavior, and stability need in-game verification on the real host and world.

Reopening checklist

  • Keep the pre-update backup and tested rollback steps available.
  • Publish the world policy, settings summary, MOD status, and known limitations.
  • Confirm who can change settings or restore backups.
  • Monitor official hotfix and known-issue announcements.
  • Record every post-launch setting or MOD change.

Source note

This checklist is based on Pocketpair's official Palworld v1.0 Steam changelog and official MOD warning. Operational tests are intentionally marked as verification steps rather than claimed server results.

FAQ

Should a server owner wipe for Palworld 1.0?

Pocketpair says existing saves can continue. A wipe is optional, but the existing world should be backed up and tested before reopening.

Did dedicated-server defaults change?

Yes. Pocketpair says Version 1.0 defaults were adjusted to more closely match single-player Normal difficulty.

Can I increase the player limit after the optimization update?

The changelog does not define a safe increase. Capacity needs in-game verification on the actual host and world.

Is voice chat available on every server platform?

No. It must be enabled in dedicated-server world settings, and Pocketpair says it is not supported on WinGDK.

Sources