Palworld v1.0.4 Base Assignment Retest Checklist

A slow station after v1.0.4 is a reason to test one assignment—not proof that your whole base needs rebuilding.

What v1.0.4 changed—and what it does not prove

Establish the confirmed refresh triggers while preventing unrelated Base Pal changes from being treated as one production-system rewrite.

• The official v1.0.4 notes include a fix for Worker Pal assignments not being correctly reflected in Base Facilities.
• The patch adjusted both summoned Pals and Base Pals to prioritize skills expected to deal higher damage and adjusted Base Pal behavior when using charging-type skills.
• Those skill-behavior changes concern what Pals do when using skills; they do not by themselves identify the cause of an idle production facility.
• The Work Suitability level required to gather Ancient Bark is Lv. 1 in v1.0.4.
• Treat each confirmed change as a separate retest trigger rather than assuming every prior base decision is invalid.

Capture one reproducible base symptom

Replace a general impression of slower production with a bounded observation that can be compared.

• Confirm that the game or server is running v1.0.4 before attributing relevance to this patch.
• Choose one affected facility or gathering task instead of reviewing the entire base at once.
• Record the assigned Pal, the assignment displayed by the facility, the relevant Work Suitability shown in the current interface, available inputs, and observed behavior.
• Describe when the symptom begins and whether it repeats under the same conditions.
• Preserve the initial setup long enough to establish a baseline before moving facilities or replacing several workers.

Verify the assignment shown by the facility

Apply the assignment-related fix directly without assuming that a display problem explains every work interruption.

• Open the affected Base Facility and confirm that the intended Worker Pal is reflected there.
• If the displayed assignment differs from the intended assignment, record both states before making a correction.
• Repeat the same task after confirming or restoring the assignment.
• Compare only the observed assignment and task behavior; do not infer a wider base failure from one facility.
• If the assignment is displayed correctly but the task remains stalled, continue testing instead of treating the fixed issue as the confirmed cause.

Separate work behavior from skill behavior

Prevent the patch's combat-oriented skill-priority adjustment from being misapplied to production diagnosis.

• Record whether the observed problem occurs while the Pal is performing facility work, gathering, or using skills in another context.
• When charging-type skill behavior is the symptom, reproduce that behavior separately from the production test.
• Do not use a combat-skill observation as evidence that Work Suitability or facility assignment changed.
• Change one worker, assignment, or test condition at a time so the result remains interpretable.
• Keep separate notes for facility work, gathering, and skill use.

Retest Ancient Bark gathering with the current requirement

Turn the confirmed Work Suitability change into a narrow gathering check without making unsupported rate claims.

• Inspect the candidate Pal's current Work Suitability in the active interface.
• Use Lv. 1 as the v1.0.4 Work Suitability requirement for gathering Ancient Bark.
• Observe whether the Pal begins the intended gathering task under the current setup.
• Record the result without inferring a gathering speed or yield that the supplied patch evidence does not quantify.
• If the task still does not proceed, document the surroundings, assignment state, and Pal behavior before changing another factor.

Interpret the controlled retest

Convert observations into one bounded next decision without promising increased output.

• If confirming the assignment changes the result, retain the working setup and record what differed.
• If changing one worker changes the result, compare the displayed suitability and assignment states before drawing a conclusion.
• If neither change affects the symptom, restore the baseline where practical and investigate a different observable factor.
• Avoid rebuilding the base unless the controlled result points to a layout-specific issue.
• Recheck this workflow after a later patch that changes Base Pal behavior, Work Suitability, or facility assignments.

Decision checklist

• Confirm the active game or server version.
• Choose one facility or gathering task to test.
• Record the intended and displayed Worker Pal assignment.
• Record the relevant Work Suitability shown in the current interface.
• Confirm that required task inputs are present.
• Repeat the task once without changing the layout.
• Change only one worker, assignment, or test condition.
• Write down the result and one next verification step.

Worked example

Suppose a production facility appears idle after updating to v1.0.4. First, record the facility, intended worker, assignment displayed by the facility, relevant Work Suitability, available inputs, and the Pal's observed action. Repeat the task without moving the station. If the displayed assignment is wrong, correct only that assignment and run the same observation again. If the assignment is already correct, substitute one suitable worker while leaving the facility and inputs unchanged. A changed result supports a narrower worker-or-assignment investigation; an unchanged result means the patch evidence does not yet identify the cause. Do not rebuild the base from this observation alone.

Common mistakes

• Replacing several workers before recording a baseline.
• Treating adjusted combat skill selection as proof of a production-system cause.
• Assuming the assignment fix explains every idle facility.
• Changing the worker, facility, inputs, and layout in the same test.
• Using an older Ancient Bark requirement instead of checking the v1.0.4 requirement.
• Claiming a production-rate improvement when the supplied evidence gives no rate measurement.

Related guides