Inventory change control

Change Palworld inventory values without a blind bulk rewrite.

Inventory edits should name the container, item, quantity, and affected player. Palworld Save Editor's sample workflow validates integer ranges and blocks any path outside the visible plan.

Scan local files Try the safe sample

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, freeze the original, preview the exact scope, run validation, and export a receipt. Unknown binary formats stay read-only.

0 B sent to a serverLocal hashing and ZIP inspectionBlocked export on failed validation

What needs to happen?

Drop Level.sav, a world ZIP, or a Pal Save Editor JSON fixtureFor editing or transfer checks, include Level.sav and the Players folder. Choose local files

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.

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.

Legal values and item identity

Quantity validation checks integers and supported limits, but it cannot make an unknown item ID valid. Current binary support needs a version-aware item registry before adding or replacing arbitrary items.

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

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

FAQ

Questions people ask before touching the save

Can I add any item by name?

Not safely without a current version-aware item identifier map. The sample edits known fixture fields only.

Will inventory edits affect storage boxes?

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