Palworld 1.0 Server: What Changed and How to Update

Palworld left Early Access on 10 July 2026. What 1.0 changed for dedicated servers: new settings, crossplay, Early Access worlds, mods and launch flags.

By
Updated Oct 26, 2026 · 6 min read
Read inesenfrde
Pixel-block skyline with the title Palworld 1.0 Server: What Changed and How to Update

Palworld left Early Access on 10 July 2026, and a Palworld 1.0 server is not quite the server you ran in 0.7. There are new world settings, voice chat that only a dedicated server can switch on, a launch flag to drop and old mods to delete. Here is what Pocketpair changed and how our Palworld server hosting handles it.

New to running one? Our Palworld dedicated server guide covers setup, RAM and consoles from the start.

  • Date: 1.0 shipped on 10 July 2026; the current patch is v1.0.5 (15 September).
  • Old worlds: Early Access saves carry over; Pocketpair still suggests a fresh character.
  • New settings: the 1.0.4 reference lists ten keys the 0.7.3 one did not, voice chat among them.
  • Crossplay: unchanged, on by default for Steam, Xbox, PS5 and Mac.
  • Before updating: back up, delete old mod files, drop -useperfthreads.

1. What 1.0 changed for servers

Pocketpair announced the date at Summer Game Fest (Steam, 5 June) and published the 1.0 changelog on 10 July. Most of it is content: the Sunreach sky island, the World Tree, 72 new Pals for 287 in total, a story rework and wave-based raids. For whoever runs the server, the lines that matter are in the multiplayer and optimisation sections:

  • Voice chat, "only available when enabled in the world settings of a dedicated server".
  • Guild roles with permissions per role, and structures that only some roles can open.
  • Safer saves: the save process was changed "to reduce the risk of save data corruption".
  • Performance: dedicated server processing was optimised "even in situations with many players", and crashes and memory leaks on dedicated servers were fixed.
  • New defaults: dedicated server world settings now "closely match single-player Normal difficulty".

The patches since then are mostly fixes. v1.0.3 added bAllowEnemyCampSpawnNearBaseCamp, v1.0.4 added a per-player building limit and made version mismatch errors show the server's version, and v1.0.5 is a bug-fix build.

2. The new settings, key by key

Pocketpair keeps its configuration reference versioned. Compared with the 0.7.3 page, the 1.0.4 page adds these keys to PalWorldSettings.ini:

KeyWhat it does (Pocketpair's description)
bEnableVoiceChatEnables in-game voice chat
VoiceChatMaxVolumeDistanceDistance at which voice volume does not fade
VoiceChatZeroVolumeDistanceDistance at which voice volume reaches zero
bEnableBuildingPlayerUIdDisplayShows the builder's player ID on structures
bAllowEnemyCampSpawnNearBaseCampLets enemy camps spawn near player bases
BaseCampMaxNumTotal number of bases on the server
PhysicsActiveDropItemMaxNumDropped items that may use physics
MonsterFarmActionSpeedRateSpeed of ranch item production
FishingDifficultyRateFishing difficulty, 0.1 to 1.0
bIsPvPTurns PvP mode on

bIsPvP is not really new, it is now documented. The building limit from v1.0.4 is MaxBuildingLimitNum (0 means no cap). If you copied an old config around, note that AllowConnectPlatform is "not available in this version": use CrossplayPlatforms.

An update does not rewrite your PalWorldSettings.ini. The new 1.0 defaults arrive in DefaultPalWorldSettings.ini, which the server ignores, so on a server that started life in Early Access, compare the two files and copy across what you want. Our Palworld server settings guide explains the file key by key.

3. Bringing an Early Access world to 1.0

The changelog closes with: "we recommend starting fresh with a new character. Of course, you can also continue your adventure with your existing save data." So old worlds load. What changes for them:

  • Map edge: the playable boundary of Palpagos moved. With saves from v0.7.3 or earlier you may spawn outside it; use Emergency Escape from the Options menu.
  • Experience: existing experience is converted to the new table; player levels are not reduced.
  • New-world-only changes: some changes, such as halved egg incubation on Normal and Hard and the saddle unlock in Random Pal Spawn Mode, apply only to newly created worlds.

Before the first 1.0 start, copy the whole Pal/Saved folder: it holds both the world (SaveGames) and the settings (Config). Pocketpair's requirements page also warns that "low-performance storage may corrupt saved data", so keep that copy off the server.

4. Mods, launch flags and crossplay

Old mods. Pocketpair's mods and 1.0 notice warns that mods installed since around 2024 can crash the game, corrupt saves or block quests after 1.0, and that disabling them is not enough: delete the files, verify the install, and back up first. Saves that depend on modded items or Pals may not load once those mods are gone. On the server side, the mod page says server mods "work only on the dedicated server with Windows edition".

Launch flags. The arguments page used to recommend -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS for performance. For 1.0 it now says: "In v1.0 and later, leaving this parameter unset may improve performance." Remove them from old start scripts. The same page adds -enable-gamedata-api, which turns on a REST endpoint with a snapshot of every actor in the world.

Crossplay. Nothing changed here. The About server page still says dedicated and community servers are cross-play enabled by default for Steam, Xbox, the Microsoft Store PC version, Mac and PS5, and that Xbox and PS5 players need a community server, one that is listed in the in-game server list. If consoles cannot see you, our guide to a Palworld server not showing in the community list covers the checks.

5. Palworld 1.0 on 1up

Our Palworld page runs Pocketpair's own Linux server image, pinned to v1.0.5.102999 today. What that means for the points above:

  • Pro (€10/month, 8 GB RAM, 60 GB disk, 5 backups) is the smallest plan that keeps Palworld online 24/7, with exactly the 8 GB it needs to boot; Studio (€20/month) gives 16 GB and Ultra (€50/month) 32 GB. On Free, Palworld runs with the hourglass at ×3.5: your free time drains 3.5 times faster, so it is a way to try 1.0, not to host it. Pocketpair recommends 16 GB and says 8 GB boots but risks out-of-memory crashes.
  • Our start script does not pass -useperfthreads or the other old flags.
  • At each start we rewrite only the keys the Game tab manages and a few technical ones; voice chat and the other new keys are yours to set in Files, in Saved/Config/LinuxServer/PalWorldSettings.ini, with the server stopped.
  • The server runs vanilla: server mods need the Windows server, so there is no mod upload for Palworld.
  • List in the community servers in the Game tab starts the server with -publiclobby; console players should then find it by name. We have not seen it in the list from a console ourselves, so check after the restart.
  • The version moves when we publish a new image. If Pocketpair ships a patch before we do, the v1.0.4 mismatch message names the server's version, so players know what is happening.

Checked against Pocketpair's 1.0 changelog, patch notes and server documentation (docs version 1.0.4), and against the server our panel runs, Palworld v1.0.5.102999, on 2026-10-07.

Change log

  • 2026-10-07: first version, for Palworld v1.0.5.
  • 2026-10-08: panel names updated: the Game and Server tabs replace the old Settings tab.
  • 2026-10-20: Studio is now €25; Palworld also runs on Free with the hourglass at ×3.5.
  • 2026-10-26: Palworld runs 24/7 from Pro (€10, 8 GB); Studio €20/16 GB, Ultra €50/32 GB.

Frequently asked questions

On 10 July 2026, when Pocketpair took the game out of Early Access. The latest patch at the time of writing is v1.0.5, released on 15 September 2026.

About the authorFounder, developer and support

Keep reading