Palworld World Settings Guide for 1.0

World settings decide whether Palworld feels fair, slow, dangerous, or completely broken. The trick is not maxing every convenience slider. The trick is removing friction without deleting the game.

Random Pal Mode placement data from v0.7.3 and earlier is not carried forward into the habitat rebalance. Treat old randomizer routes and boss maps as stale unless rebuilt on 1.0.

Where to change settings

For solo or hosted co-op, select the world from the title screen and open the world settings menu before launching. For dedicated servers, settings live in the active server configuration and usually require a full server restart.

Before large changes, make a backup with Save Data Backup & Recovery.

Choose settings by the result you want

Goal	Setting group to inspect	What to verify before saving
More daylight	Day/night timing	The current UI’s description and whether a larger value means faster or longer
Faster catch-up	EXP and capture settings	The current label, default, range, and effect direction
Less resource repetition	Gather/drop and respawn settings	Whether the value changes quantity, frequency, or interval
Easier travel	Stamina and inventory settings	Whether the value controls capacity or drain
Shorter breeding waits	Incubation settings	Whether zero or an extreme value removes the intended timer

Small numbers beat extreme ones. If every slider moves too far, you are no longer tuning the save; you are deleting the curve.

Settings to treat carefully

Setting	Why it is risky
Pal Appearance Rate	More entities can hurt performance and make fights messy
Max workers per base	More workers can mean more pathing and raid pressure
Bases per guild	More bases increase simulation and management load
Death penalty	Harsh settings can turn a mistake into a quit moment
Random Pal Mode	Creation-only behavior should be decided before the world matters
Hardcore options	These are commitment settings, not casual experiments

If you are setting up a long-term base network, read the Base Site Selection Guide before raising base caps just to compensate for poor placement.

Preset chooser

Playstyle	Start from	First systems to review	Stop if…
Balanced solo	The current Normal preset	Travel, gathering, incubation	A core loop becomes irrelevant
Relaxed exploration	The closest current casual preset	Death penalty, stamina, capture friction	Encounters lose all consequence
Builder	Normal, then base-focused changes	Raids, building, worker and base caps	Performance or pathing worsens
Co-op host	Normal	Shared pacing, drops, death penalty	Clients disagree about the applied state
Dedicated server	A documented server preset	Only keys confirmed in the active config	The server rejects or ignores the value

These are editorial starting points, not Pocketpair presets. Record the old value, read the current UI description, and test one change in a disposable session before applying a batch to a valuable world.

Breeding and settings

Egg timers interact directly with Mutation Breeding. If incubation is instant, cake choice and farm throughput barely matter. That is fine for a sandbox save, but it makes guide advice about breeding economy less useful.

The Mutated Egg outcomes guide explains the separate rare-result taxonomy; changing incubation pacing does not turn those outcomes into deterministic recipes.

For a normal long-term save, shorten timers enough to respect your time, not enough to erase the system.

Raids and bases in 1.0

Raids are more important after 1.0 because base defense is a real loop again. Keep raids enabled if you want the pressure. If your base is built on bad terrain and raids feel unfair, fix the layout before blaming the setting.

Flat paths, chokepoints, and worker placement solve more than most slider changes.

Base raids and summoned slab raids are different systems. Turning random base raids off does not replace the preparation required for a Summoning Altar or Raid Area encounter. Use the Hartalis Raid Guide for that separate loop, and the Boss Route Guide for tower, Alpha, and raid discovery.

Dedicated server notes

Server admins should change one thing at a time and document it. If players report that a setting “did nothing,” check these basics first:

• Was the active config file edited?
• Was the server stopped first?
• Did the server restart after the edit?
• Is the value locked by world creation state?
• Did the syntax remain intact?

Bottom line

Good settings are invisible: travel is smoother, farming is less repetitive, and deaths still matter. If a slider makes an entire system irrelevant, you probably moved it too far.

Read the current description, change one setting at a time, record the old value, and keep a save backup before large experiments.