Skip to main content
Guides
PalMods

Updated

Guides/Player Essentials/Best World Settings for 1.0
Pacing presetsPalworld 1.0Beginner

Best World Settings for 1.0

Balanced, low-grind, and challenging Palworld 1.0 presets with clear explanations for XP, damage, drops, eggs, randomizer, and server performance.

12 min read Researched for 1.0 Sources included

Palworld 1.0 moves quickly if a co-op group explores together, catches every new Pal, and shares base production. The best custom settings do not simply make everything harder. They slow the progression that the group is outrunning, trim repetitive waiting, and leave combat readable enough that every player can contribute.

The presets below use Pocketpair's exact dedicated-server parameter names so they work as a planning sheet for both the in-game Custom Settings screen and PalWorldSettings.ini. Start with the balanced column, play one full session, then change only the cluster causing trouble. A setting you can explain is easier to tune than a downloaded one-line configuration with forty hidden compromises.

01Recommended values

Three practical 1.0 presets

Balanced co-op keeps the campaign paced; low-grind preserves combat while shortening chores; challenge co-op asks for coordination without using one-hit damage.

SettingBalanced co-opLow-grind / builderChallenge co-op
ExpRate0.751.00.5
PalCaptureRate1.01.250.8
CollectionDropRate1.02.01.0
EnemyDropItemRate1.01.51.0
PalEggDefaultHatchingTime1.002.0
DeathPenaltyItemNoneItemAndEquipment
PlayerDamageRateAttack1.01.20.8
PlayerDamageRateDefense1.00.81.2
PalDamageRateAttack1.01.01.1
PalDamageRateDefense1.00.91.1
PalSpawnNumRate1.01.01.25
BuildObjectDeteriorationDamageRate1.001.0
02Pacing

Why balanced co-op starts at 0.75 XP

A group earns capture bonuses and exploration experience in parallel, then pools materials at one base. That compounds faster than solo play. Dropping ExpRate to 0.75 gives the party more time in each equipment and Pal tier without turning every level into a grind. If your group skips captures and follows only the main objectives, return it to 1.0.

Do not use low gathering rates to slow progression. Resource scarcity mostly adds repeated trips and idle crafting rather than new decisions. Keep CollectionDropRate and EnemyDropItemRate at 1.0 for a deliberate first run, or raise them for a builder group, then tune XP separately. The same separation applies to eggs: PalEggDefaultHatchingTime is the number of hours for a Huge Egg, while smaller eggs scale from it. Setting it to zero removes incubation waiting without changing breeding outcomes.

03Slider traps

The settings that read backwards

Setting familyLower value doesHigher value does
PlayerDamageRateDefense / PalDamageRateDefenseReduces damage takenIncreases damage taken
PlayerStaminaDecreaceRate / hunger depletion ratesSlows depletionSpeeds depletion
BuildObjectDeteriorationDamageRateSlows out-of-base decay; 0 disables itSpeeds deterioration damage
CollectionObjectRespawnSpeedRateShortens the respawn intervalLengthens the respawn interval
DayTimeSpeedRate / NightTimeSpeedRateMakes that phase last longerMakes that phase pass faster
04Randomizer

Choose the Pal randomizer deliberately

The randomizer changes discovery more than difficulty. Keep its seed with your world notes so a favorite layout can be reproduced.

OptionWhat it doesBest use
RandomizerType=NoneUses Pocketpair's curated 1.0 habitats and levels.A first playthrough or story-focused group.
RandomizerType=RegionRandomizes Pal placement separately by region.Fresh discovery while retaining more geographic structure.
RandomizerType=AllFully randomizes Pal placement across the world.A replay where surprise matters more than intended progression.
bIsRandomizerPalLevelRandom=FalseKeeps randomized levels within each area's intended range.The safest co-op randomizer setting.
bIsRandomizerPalLevelRandom=TrueMakes wild Pal levels fully random.A chaotic challenge run that can produce severe early spikes.
RandomizerSeedMakes a randomizer layout repeatable.Sharing or restarting a known seed.
05Change control

Apply settings without creating a mystery configuration

  1. 01

    Name the problem

    Write one sentence such as “the group reaches new regions ten levels early” or “breeding nights become idle waiting.”

  2. 02

    Back up the stopped world

    For dedicated servers, stop the process and copy the full save and configuration tree. For local worlds, use the world-selection backup before large changes.

  3. 03

    Change one cluster

    Tune XP, resources, combat, survival, or performance as a group. Do not change all five at once.

  4. 04

    Use the live file on servers

    Edit the copied PalWorldSettings.ini under WindowsServer or LinuxServer. Editing DefaultPalWorldSettings.ini has no effect.

  5. 05

    Play a representative session

    Include exploration, one boss, base production, and a death or recovery. A five-minute spawn test cannot evaluate campaign pacing.

  6. 06

    Record the result

    Keep the date, old value, new value, and group reaction. Revert quickly when a multiplier creates one-hit combat or server stutter.

06Difficulty

Keep challenge fair in co-op

  • Lower player output before raising incoming damage

    A modest PlayerDamageRateAttack=0.8 lengthens fights without making every mistake lethal.

  • Raise both damage-taken multipliers gently

    Values around 1.1 to 1.2 are noticeable. Large values amplify lag, desync, and unavoidable attacks into one-shots.

  • Do not multiply spawns first

    PalSpawnNumRate increases combat density and server load together. Test 1.25 before attempting larger packs.

  • Keep capture difficulty separate

    Lower PalCaptureRate only if sphere progression still feels meaningful; failed catches can become material grind rather than combat challenge.

  • Use a recoverable death penalty

    ItemAndEquipment creates a rescue run. All can also drop team Pals and is much harsher for mixed-skill groups.

07Performance

Settings that can increase server load

SettingWhy it costs moreConservative approach
PalSpawnNumRateMore active wild Pals and combat AIKeep at 1.0; test 1.25 with several players online.
BaseCampWorkerMaxNumMore worker AI, pathing, and productionRaise only for bases designed with clear paths and enough host memory.
BaseCampMaxNumInGuildMore persistent bases and structuresPocketpair allows up to 10 but warns that increases raise processing load.
MaxBuildingLimitNumMore replicated structures per playerSet a real cap on public servers instead of unlimited.
bIsUseBackupSaveDataFrequent snapshots add disk I/OKeep it enabled and use fast SSD storage; safety is worth the measured load.
08Continue

Run the world safely

Server operationsServer, wipe, and save guideSet up SteamCMD, enable real backups, understand Global Palbox limits, and avoid unsafe character remapping.Game systems1.0 progression changesSee how the new capture bonus, level curve, condensation cost, and world reset details affect pacing.Primary documentationOfficial parameter referenceCheck Pocketpair's current descriptions and newly added settings before changing a production server.
09Verification

Research sources

The claims in this guide were checked against these current references. Primary sources are marked first.

Primary sourceConfiguration parametersCanonical PalWorldSettings.ini paths, backups, Global Palbox controls, randomizer options, and balance settings.Primary sourceConfigure the serverCurrent launch arguments and the 1.0 performance note for older multithreading flags.Primary sourcePalworld v1.0 official release changelogPrimary release notes for randomizer migration, egg-time changes, progression, and dedicated-server optimization.r/PalworldLeveling up too fast in Palworld 1.0Player feedback behind the slower balanced-co-op XP recommendation.r/PalworldHow long does it take to reach the endgame?Community pacing question used to frame the preset tradeoffs.r/PalworldHow does Palworld 1.0 feel for challenging co-op?Co-op difficulty question behind the challenge preset and change-control advice.r/PalworldStarting a new game with the Pal randomizerPlayer question that prompted the Region versus All randomizer explanation.
FAQ

Frequently asked questions

What XP rate is best for Palworld 1.0 co-op?

Start at `ExpRate=0.75` for a group that explores and completes capture bonuses together. Use 1.0 if the group follows only the main path or feels under-leveled. Keep resource rates separate so slower leveling does not become extra gathering grind.

What does PlayerDamageRateDefense do?

It multiplies damage taken by the player, so the name reads backwards from many players' expectations. Values below 1.0 make players tougher; values above 1.0 make them take more damage. `PalDamageRateDefense` follows the same pattern for Pals.

How do I make egg hatching instant?

Set `PalEggDefaultHatchingTime=0`. The parameter is the number of hours required for a Huge Egg, with smaller eggs scaling from that baseline. This removes waiting without changing the Pal produced by breeding.

Which randomizer mode is best for a first playthrough?

Use `None` for Pocketpair's intended 1.0 habitats. If the group insists on randomization, `Region` with `bIsRandomizerPalLevelRandom=False` preserves more geographic and level structure than a fully random `All` world.

Does increasing Pal spawn rate hurt server performance?

It can. Pocketpair explicitly notes that `PalSpawnNumRate` affects performance. Keep 1.0 on a busy server and test 1.25 with several players online before raising it further.

Where is PalWorldSettings.ini on a dedicated server?

After the first launch, use `Pal/Saved/Config/WindowsServer/PalWorldSettings.ini` on Windows or `Pal/Saved/Config/LinuxServer/PalWorldSettings.ini` on Linux under the PalServer install. Copy the default file there first; editing `DefaultPalWorldSettings.ini` directly has no effect.