Create a recoverable save copy before testing changed mission progress, Awakening, Mutation, or map state.
Palworld Guide
Need a Palworld 1.0 rule? Open the Change Finder; back up before diagnosing an old save. For one stalled job, filter the dated Work Suitability list by job and minimum recorded Work Suitability level, put one candidate first in that Pal’s Work Priority, confirm its output reaches storage, then compare equal-length runs with other inputs unchanged. Suitability level does not predict output speed.
- Latest reviewed official patch
- v1.0.5 · September 15, 2026
- Work Suitability snapshot
- 292 Pals · 747 job records · September 2, 2026
- Live base check
- Work Priority + stored output
1.0 returner field notes
Palworld 1.0 is an old-save inspection job
The first 1.0 session should not be a blind sprint into level 80 content. Back up the world, name the visible symptom, inspect the connected mission, Partner Skill, Work Suitability, party, or setting, then rebuild one system at a time.
A familiar Pal may no longer cover an old station plan; inspect Work Suitability and the real production bottleneck together.
Sunreach, the World Tree, new weapons, and level 80 progression are easier to approach after the old party and base are stable.
Record one working party job and one complete base cycle so a later change can be judged by a repeatable result, not by memory.
Revisit signal: Return after a major Palworld patch, an old-save mismatch, or whenever a base assignment seems to contradict the prior 1.0 plan. Re-open the exact system first; do not restart the whole world by default.
At a glance
Palworld at a glance
A decision-first Palworld 1.0 Hub that routes changes, save safety, base staffing, progression, and travel to focused pages while separating official rules, dated records, and live-world tests.
- Release
- Version 1.0 · July 2026
- Platforms
- PC, PlayStation 5, and Xbox
- Developer
- Pocketpair
- Publisher
- Pocketpair
- Latest reviewed official patch
- v1.0.5 · September 15, 2026
- Work Suitability snapshot
- 292 Pals · 747 job records · September 2, 2026
- Live base check
- Work Priority + stored output
- Progression rule
- Follow the active mission or Technology gate
Symptom → evidence → next check
Choose the test before changing the save
This Hub routes a named problem to its focused reference. It keeps official patch rules, dated Work Suitability records, and results that must be tested in your own world separate.
Quick actions
Open the player job in front of you
Each route leads to a current table, a repeatable first-session step, or a recovery answer.
Current blockers
Route by the symptom you can actually see
Start from the problem you can name, then take the smallest safe next action.
My old mission route no longer matches the save
Version 1.0 reset main and sub-mission progress; some tutorial and Tower Boss progress can be restored from recorded defeats. Back up, open the live mission log, and compare the current marker before calling the save broken.
A map icon vanished after respawn
The official v1.0.5 note covers some map filters turning off after respawn. Confirm the installed build, restore the category, and check one known destination before moving a Palbox.
My old Ancient Bark worker is rejected
v1.0.4 lowered the named gathering gate to Work Suitability Lv. 1. That is an eligibility rule, not a throughput promise; hold the path and storage steady while testing one gather-to-storage cycle.
The Pal keeps leaving its target station
Filter the exact job and minimum level, then place that worker’s target task ahead of competing jobs in Work Priority. If output still stalls, inspect the complete handoff instead of reading the suitability level as speed.
Can one Pal cover two jobs without slowing either?
Use the two-job overlap only as a shortlist. Observe a complete cycle in both lanes; keep separate workers if competing tasks interrupt either bottleneck.
What should I pursue after returning to Palworld 1.0?
Use the live mission or Technology gate as the next objective. The progression page connects that gate to captures, new Pals, Awakening, Mutation, and level-80 growth.
Which return option takes me to a chosen base?
An activated Statue or Palbox is the chosen-destination route; Homeward Thundercloud returns to the nearest base where usable. Emergency Escape prevents item drops under the 1.0 rule but does not choose a destination.
One controlled check
Turn a base-job shortlist into a real production test
The Hub points to the relevant reference; use this short loop when the next decision is whether a worker actually solves a base bottleneck.
- 1Name one stalled job
Pick the station or output that is actually short; do not infer a base-wide failure from one empty product.
- 2Filter job and minimum level
Use the dated 292-Pal snapshot to find an eligible candidate at the base level you need. The record is a shortlist, not a live-server guarantee.
- 3Give one worker the first task
Set that Pal’s target lane ahead of competing jobs in Work Priority. Keep its other jobs unchanged unless they keep pulling it away.
- 4Prove delivery, then compare
Confirm a finished item reaches storage. Hold station, input, path, storage, power, and test duration steady; change one staffing choice and compare stored output over equal runs.
- 5Route the second decision
Use Coverage for a two-job worker, Progression for a mission or Technology target, and Return to Base for a chosen-versus-nearest destination.
Game systems
Three evidence lanes, three different kinds of answer
Use official notes for named rule changes, the dated database for shortlist comparisons, and the live save for assignment behavior and actual output.
| System | Player job | First move |
|---|---|---|
| Official patch rule | Named changes in 1.0, v1.0.4, and v1.0.5. | Match your symptom and installed build. |
| Work snapshot | 292 Pals and 747 Pal-to-job records from 2026-09-02. | Filter by the exact base job and minimum level. |
| Live assignment | Work Priority decides which eligible task a worker attempts first. | Prioritize one lane, then watch the worker. |
| Measured output | A suitability level does not state items per minute or completed deliveries. | Compare stored output across equal test windows. |
| Return destination | Chosen base, nearest base, and Emergency Escape are different routes. | Choose by destination and item-risk rule. |
Risk board
Keep the evidence and the player action in sync
When a row says “Check in game,” confirm it before spending rare resources or changing an important save.
- Safe move
- Keep a recoverable copy before diagnosing.
- Avoid
- Treating a mission reset as proof the whole save is unusable.
- Safe move
- Use the 2026-09-02 Work Suitability snapshot for recorded job eligibility and base level.
- Avoid
- Reading a snapshot level as live Work Priority or output speed.
- Safe move
- Confirm one completed product reaches storage, then compare equal-length runs.
- Avoid
- Changing worker, station, inputs, route, and storage at once.
- Safe move
- Separate the no-item-drop Emergency Escape rule from destination travel.
- Avoid
- Assuming Emergency Escape selects a particular base.
Guide directory
Open the page that changes the next decision
Choose the route, comparison, database, or guide that matches what you need to do next.
Player questions
Palworld FAQ
Answers reflect the current status and check date shown on this hub.
What is the latest Palworld update covered here?
The official notes reviewed for this Hub run through v1.0.5, dated September 15, 2026. That patch fixed some map icon filters turning off after respawn; confirm your installed build and the live filter panel before treating a marker as missing.
How current is the Palworld Work Suitability list?
It contains 292 Pals and 747 Pal-to-job records from the September 2, 2026 snapshot. Use it to shortlist eligibility and recorded Work Suitability levels, then confirm assignment and behavior in your own world.
Does a higher Work Suitability level mean higher priority or faster production?
No. Suitability records which base jobs a Pal can perform and at what recorded level. Work Priority determines competing tasks; completed output still depends on the live worker, inputs, route, station, storage, power, and world settings.
How do I test whether a new base worker increased output?
Prioritize one candidate on the stalled job, make sure a finished item reaches storage, then compare stored counts across equal-length runs while holding the station and inputs steady. Change one staffing choice at a time.
Should I start a new world for Palworld 1.0?
Not automatically. Keep a backup, read the current mission and world state, and isolate one changed system before deciding whether the save actually needs a restart.