Inventory change control
Palworld Inventory Editor with container-scoped item changes.
The editable sample and Pal Save Editor JSON fixtures expose wood, stone, Paldium fragments, and ancient technology points. In PlZ Beta, a complete Level.sav plus the matching Players files lists each player's six linked containers: change a stack's quantity, add an item to a free slot, remove an item, or move a stack to another container. Unique weapons and armour, dynamic item data, and ownership stay untouched.
Open a save to edit inventory
Choose the complete world so every editable quantity remains tied to the right owner and container.
Change item quantities, add items to free slots, remove items, and move a stack between containers once the matching Players files resolve who owns each container.Quick answer
Palworld inventory editor: what to know first
- Four documented fixture counters are editable; equipment mutation, money edits, and storage ownership changes are not.
- A complete PlZ2 / 0x32 Level.sav plus the matching Players files resolves each player's six linked containers and every slot in them.
- Each operation names the exact owner, container, slot, and source path: a quantity from 1 to 9,999, an item added to a free slot, an item removed, or a stack moved.
- A move is one undoable step, so an item is never left in both containers or in neither.
What inventory evidence is available today
The editable fixture model contains four inventory counters and exposes them as a dedicated module. Every change appears as an exact inventory path and must pass integer range, scope, and round-trip checks.
In PlZ Beta, the matching Players file supplies six container IDs. Level.sav supplies the corresponding slots, item IDs, quantities, owner context, changed reparse, and non-target preservation checks. Inventory edits never change the Players file itself.
| Input | Available inventory evidence | Inventory edit or export |
|---|---|---|
| Editable sample | Four documented counters | Allowlisted quantities + safe pack |
| Pal Save Editor JSON | Documented fixture inventory | Allowlisted quantities + safe pack |
| Real Level.sav + matching Players | Six linked containers and every slot | Quantity, add, remove, move + Safe Pack |
Why bulk inventory edits are risky
A save can contain several inventory-like containers. A global search-and-replace can touch player bags, equipment, base storage, key items, another player's data, or references that are not item quantities. The live operation therefore identifies the exact owner, container, slot, and StackCount path before it exposes a value, and rejects missing containers, missing slots, empty slots, unknown targets, and out-of-range values.
Legal values and item identity
Palworld reserves every slot a container will ever have, so adding an item fills a free slot rather than growing the container. The item ids already present in your save are offered first, and a typed id is checked for shape. Quantities are whole numbers from 1 to 9,999. Moving takes the whole stack to the first free slot of another container: always a Common inventory, and any other container only when it already holds that item. Unique weapons and armour, dynamic item data, equipment metadata, and ownership remain outside this allowlist.
What an inventory export receipt proves
The real-save receipt identifies each player-linked container and slot, the item, the exact before-and-after contents, changed reparse, non-target comparison, unchanged Players file bytes, and the immutable original backup.
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.
Questions people ask before touching the save
Can I add any item by name?
Yes, into a free slot of a container you own: pick one of the item ids already in your save, or type an id from the game. The editor checks the id's shape rather than a full item catalogue, so an id the game does not know may simply be ignored.
Will this edit move or create storage items?
Only when you ask it to. Adding fills a free slot, and moving takes a stack from one container to another in a single undoable step. Dynamic item data, ownership, and the Players file stay unchanged, and unique weapons and armour are never moved.