Inventory change control

Palworld Inventory Editor guide to scoped quantity changes.

Inventory edits should name the container, item, quantity, and affected player. This page explains the validation and receipt requirements, but the current browser UI does not expose inventory fields or edit real save files.

Value ruleInteger onlyNo NaN, fractions, or unsupported negative quantities
ScopeNamed pathsUnexpected collections fail the gate
ExportReceipt includedEvery quantity change is recorded

Local safety workbench

Run the same safety workflow on your local files.

Scan locally and export a receipt. Editing, diff, and validation are limited to the sample and Pal Save Editor JSON fixtures; every real binary input stays read-only.

0 B of save data uploadedLocal hashing and ZIP inspectionBlocked export on failed validation
What needs to happen?
Find my save
Files never leave this tab Original input stays immutable Real binary writing is locked in this release

Local return loop

Save Chronicle

Receipt metadata lives only in this browser. Raw saves are never stored.

Your next local scan will appear here.

ReadyLocal workbench loaded.
01

Why bulk inventory edits are risky

A save can contain several inventory-like containers. A global search-and-replace can touch storage, equipment, key items, or another player's data. The change plan must identify the exact container path.

03

A better export receipt

The receipt should say which player and container changed, list each before and after quantity, and confirm unrelated inventory groups were unchanged.

SAFE

Task checklist

  1. 01Select the exact player and container.
  2. 02Use integer quantities inside supported limits.
  3. 03Do not add unknown item IDs.
  4. 04Check unrelated inventory groups remain unchanged.
FAQ

Questions people ask before touching the save

Can I add any item by name?

No. Inventory controls are not implemented, and a future editor also needs a current version-aware item identifier map.

Will inventory edits affect storage boxes?

They should not unless those paths are explicitly selected. Scope lock exists to catch that kind of spillover.