287 total in version 1.0
Palworld Version 1.0 Changes
Official 1.0 change and old-save decision finder
Palworld Version 1.0 Changes
Back up the old world, then use the finder to compare mission resets, spawn data, level 80, 72 new Pals, Partner Skills, Work Suitability, combat, equipment, and settings. Keep systems that still work; retest or rebuild only the changed dependency.
Up from 65
Audit missions, skills, base, and settings
Change Finder
Version 1.0 change finder
Back up the old world, then use the finder to compare mission resets, spawn data, level 80, 72 new Pals, Partner Skills, Work Suitability, combat, equipment, and settings. Keep systems that still work; retest or rebuild only the changed dependency.
14 matches Version 1.0 change finder
Version 1.0 change · World
Official info Sunreach, World Tree, and expanded map
The return route begins with orientation, not a blind sprint to the old endgame.
- Before 1.0
- The old map ended before Sunreach and the World Tree route.
- In 1.0
- Sunreach, the World Tree, seven small islands, Watchtowers, settlements, ruins, and renewed sanctuaries expand exploration.
- Return action
- Re-open the map and activate nearby Watchtowers before a long expedition.
- Risk
- Old route memory no longer describes every fast-travel or progression path.
Player job
Decide whether to keep, retest, or rebuild the affected world route.
Use now
Re-open the map and activate nearby Watchtowers before a long expedition.
Safe next action
Re-open the map and activate nearby Watchtowers before a long expedition.
Risk
Old route memory no longer describes every fast-travel or progression path.
Version 1.0 change · Progression
Official info Player level cap 65 → 80
Returning characters have a new progression runway.
- Before 1.0
- The player cap stopped at level 65.
- In 1.0
- The cap is now 80 with new ancient-civilization technologies.
- Return action
- Stabilize the old party and base before spending toward the new cap.
- Risk
- Rushing new technology can hide a broken old production loop.
Player job
Decide whether to keep, retest, or rebuild the affected progression route.
Use now
Stabilize the old party and base before spending toward the new cap.
Safe next action
Stabilize the old party and base before spending toward the new cap.
Risk
Rushing new technology can hide a broken old production loop.
Version 1.0 change · Save
Official info Main and sub-mission progress reset
The story flow was reorganized around towers and the World Tree.
- Before 1.0
- Mission state followed the Early Access progression path.
- In 1.0
- Main and sub-mission progress was reset; some tutorial and Tower Boss missions auto-complete from defeat progress.
- Return action
- Back up the save, open the mission log, and rebuild the active route from the current markers.
- Risk
- Assuming the old checklist is intact can send the player to the wrong next objective.
Player job
Decide whether to keep, retest, or rebuild the affected save route.
Use now
Back up the save, open the mission log, and rebuild the active route from the current markers.
Safe next action
Back up the save, open the mission log, and rebuild the active route from the current markers.
Risk
Assuming the old checklist is intact can send the player to the wrong next objective.
Version 1.0 change · Save
Official info Random Pal spawn placement data
Habitat rebalancing changes where a returning player searches.
- Before 1.0
- Random spawn worlds carried older placement data.
- In 1.0
- Placement data from v0.7.3 and earlier is not carried over to reflect rebalanced habitats.
- Return action
- Back up and re-scout the habitats used by the old capture route.
- Risk
- Old spawn notes can be wrong even when the world itself loads normally.
Player job
Decide whether to keep, retest, or rebuild the affected save route.
Use now
Back up and re-scout the habitats used by the old capture route.
Safe next action
Back up and re-scout the habitats used by the old capture route.
Risk
Old spawn notes can be wrong even when the world itself loads normally.
Version 1.0 change · Pals
Official info 72 new Pals
The roster expands without making every old Pal obsolete.
- Before 1.0
- The Early Access roster was smaller.
- In 1.0
- 47 new Pals and 25 variants bring the total roster to 287.
- Return action
- Keep the old team until a new Pal proves a specific exploration, combat, or base job.
- Risk
- Collecting by novelty can consume training resources without improving the route.
Player job
Decide whether to keep, retest, or rebuild the affected pals route.
Use now
Keep the old team until a new Pal proves a specific exploration, combat, or base job.
Safe next action
Keep the old team until a new Pal proves a specific exploration, combat, or base job.
Risk
Collecting by novelty can consume training resources without improving the route.
Version 1.0 change · Pals
Official info Partner Skills reworked for 200+ Pals
Party composition requires a full audit.
- Before 1.0
- Old Partner Skill effects and same-Pal stacking shaped many teams.
- In 1.0
- More than 200 Partner Skills changed, and most same-Pal effects no longer stack.
- Return action
- Re-read every party skill and rebuild around distinct jobs and confirmed synergies.
- Risk
- An old stacked team can lose its core multiplier without looking obviously broken.
Player job
Decide whether to keep, retest, or rebuild the affected pals route.
Use now
Re-read every party skill and rebuild around distinct jobs and confirmed synergies.
Safe next action
Re-read every party skill and rebuild around distinct jobs and confirmed synergies.
Risk
An old stacked team can lose its core multiplier without looking obviously broken.
Version 1.0 change · Pals
Official info Awakening and Mutation
1.0 adds new long-term Pal investment paths.
- Before 1.0
- Late training relied on the earlier enhancement and breeding systems.
- In 1.0
- Radiant Gems enable Awakening; breeding can produce Mutations with higher stats and unique passives.
- Return action
- Protect proven breeding stock and test the new system before consuming rare resources.
- Risk
- Chasing a mutation can become a large resource sink without a target build.
Player job
Decide whether to keep, retest, or rebuild the affected pals route.
Use now
Protect proven breeding stock and test the new system before consuming rare resources.
Safe next action
Protect proven breeding stock and test the new system before consuming rare resources.
Risk
Chasing a mutation can become a large resource sink without a target build.
Version 1.0 change · Progression
Official info Capture Bonus 12 → 5
Early and midgame progression now moves faster.
- Before 1.0
- A species needed 12 captures to complete its Capture Bonus.
- In 1.0
- The requirement is now five captures.
- Return action
- Stop old twelve-capture farming loops once the current bonus is complete.
- Risk
- Following an old target wastes spheres and time.
Player job
Decide whether to keep, retest, or rebuild the affected progression route.
Use now
Stop old twelve-capture farming loops once the current bonus is complete.
Safe next action
Stop old twelve-capture farming loops once the current bonus is complete.
Risk
Following an old target wastes spheres and time.
Version 1.0 change · Pals
Official info Maximum condensation 116 → 48 Pals
Favorite Pal investment is substantially cheaper.
- Before 1.0
- Maximum rank consumed 116 total Pals.
- In 1.0
- Maximum rank now requires 48.
- Return action
- Recalculate the stock needed before condensing or releasing duplicates.
- Risk
- Old material targets can overfarm more than double the current need.
Player job
Decide whether to keep, retest, or rebuild the affected pals route.
Use now
Recalculate the stock needed before condensing or releasing duplicates.
Safe next action
Recalculate the stock needed before condensing or releasing duplicates.
Risk
Old material targets can overfarm more than double the current need.
Version 1.0 change · Base
Official info Work Suitability expanded to level 10
Base choices and favorite-Pal investment changed together.
- Before 1.0
- Work roles used the earlier suitability scale and Pal balance.
- In 1.0
- Suitability reaches level 10, every Pal was rebalanced, and rank-ups can raise work levels.
- Return action
- Observe one production cycle, then restaff the first bottleneck instead of rebuilding the whole base.
- Risk
- Exact old staffing math can fail after the rebalance.
Player job
Decide whether to keep, retest, or rebuild the affected base route.
Use now
Observe one production cycle, then restaff the first bottleneck instead of rebuilding the whole base.
Safe next action
Observe one production cycle, then restaff the first bottleneck instead of rebuilding the whole base.
Risk
Exact old staffing math can fail after the rebalance.
Version 1.0 change · Combat
Official info Tower Boss battles and time limit
Returning combat builds need a real benchmark.
- Before 1.0
- Tower fights used earlier arenas, skills, stats, and a 10-minute limit.
- In 1.0
- Towers were redesigned, some bosses gained new moves, and the limit is five minutes with adjusted stats.
- Return action
- Use one familiar tower to retest damage, movement, and team uptime.
- Risk
- An old slow strategy can fail the shorter clock.
Player job
Decide whether to keep, retest, or rebuild the affected combat route.
Use now
Use one familiar tower to retest damage, movement, and team uptime.
Safe next action
Use one familiar tower to retest damage, movement, and team uptime.
Risk
An old slow strategy can fail the shorter clock.
Version 1.0 change · Combat
Official info Dash, dodge, reload, and attack flow
Player control is faster and more continuous.
- Before 1.0
- Attacking or aiming used the old dodge behavior and reload interruption rules.
- In 1.0
- Combat now uses dash behavior while attacking or aiming; attacks and reload flow continue through more movement states.
- Return action
- Relearn movement in a familiar encounter before a high-cost boss or arena run.
- Risk
- Old muscle memory can create accidental distance or timing errors.
Player job
Decide whether to keep, retest, or rebuild the affected combat route.
Use now
Relearn movement in a familiar encounter before a high-cost boss or arena run.
Safe next action
Relearn movement in a familiar encounter before a high-cost boss or arena run.
Risk
Old muscle memory can create accidental distance or timing errors.
Version 1.0 change · Equipment
Official info 13 new weapons and up to six slots
Returning loadouts have more coverage options.
- Before 1.0
- The weapon pool and carried slot count were smaller.
- In 1.0
- Thirteen weapons were added; an Extra Weapon Holster allows up to six equipped weapons.
- Return action
- Add a tool only when it covers a missing range, crowd, or utility job.
- Risk
- More slots can create weight and choice clutter without a loadout plan.
Player job
Decide whether to keep, retest, or rebuild the affected equipment route.
Use now
Add a tool only when it covers a missing range, crowd, or utility job.
Safe next action
Add a tool only when it covers a missing range, crowd, or utility job.
Risk
More slots can create weight and choice clutter without a loadout plan.
Version 1.0 change · Save
Official info Normal difficulty equipment drops
Death-risk advice depends on the actual world setting.
- Before 1.0
- Older world settings may keep their existing death-drop behavior.
- In 1.0
- New or reset Normal worlds do not drop equipped items on death.
- Return action
- Read the current world setting before assuming the safer default applies to an old save.
- Risk
- The default changes only when world settings are reset or a new world is created.
Player job
Decide whether to keep, retest, or rebuild the affected save route.
Use now
Read the current world setting before assuming the safer default applies to an old save.
Safe next action
Read the current world setting before assuming the safer default applies to an old save.
Risk
The default changes only when world settings are reset or a new world is created.
No matching 1.0 change
Try mission, level cap, base, Partner Skill, combat, save, or remove one filter.
Failure recovery
Recover an old save that feels broken
Do not rebuild every system at once. Re-establish one known-good baseline.
- 1Restore a backup if needed
Keep the original world state available while investigating.
- 2Check mission and world settings
Confirm resets, death behavior, spawn mode, and active markers.
- 3Audit party and base separately
Re-read Partner Skills first; then watch one production cycle.
- 4Test one familiar fight
Use the result to decide whether combat or progression needs the next rebuild.
Decision table
Keep, retest, or rebuild after 1.0
Use the action column as the next test, not as a claim about hidden game values.
| Situation | Action | Why |
|---|---|---|
| System still performs its job | Keep | The update did not invalidate the actual result. |
| Rules changed but the route may survive | Retest | One controlled run reveals the impact. |
| Core stacking or staffing rule changed | Rebuild | The old dependency no longer exists. |
| Save or settings behavior is unclear | Back up and verify | Protect irreversible progress before experimentation. |
Player questions
Version 1.0 Changes FAQ
Use the current game panel before spending rare resources on a value that can change.
Are the change rows official?
Yes. Each visible row reflects a change announced in the official 1.0 release notes.
Which changes most affect an old save?
Mission resets, older random-spawn placement data, Partner Skill stacking, Work Suitability balance, and world-setting assumptions deserve the first audit.
Can I save a return checklist?
Yes. Save the change rows that apply to the current world; Reset clears the stored list.
Does this include later hotfixes?
The page is checked through July 24, 2026. Server settings, mods, and later hotfixes can change individual results.