Evidence log

Palworld Save Editor changelog for compatibility evidence.

Every capability change should say what format, task, fixture, and game version was tested. Palworld Save Editor does not turn a parser commit into a blanket compatibility claim.

PAL SAVE EDITOR / DIAGNOSTICWorld overview

Open a save to see its world summary

We will identify the files, version clues, completeness, and tasks available for this exact input.

Compatible PlZ Beta worlds can expose named players and Pals; unsupported formats receive diagnostic evidence.
Open this task Select files inside the App so the local session is preserved.
0.1.0RecognitionLocal ZIP/file intake, format signals, receipts, Worldprint
0.1.0Fixture loopEdit, diff, 6 checks, backup, receipt, export
PlZ Beta37 operationsPals, players, inventory, progress, guilds, and bases
01

July 27, 2026 - Static launch

Added local `.sav`, ZIP, and Palworld Save Editor JSON intake in an isolated Web Worker. Added Level.sav, player, metadata, backup, PlZ, PlM, CNK, GVAS, and unknown signature recognition with explicit capability states.

Added the complete sample editing loop: immutable original, field-level diff, owner and identity checks, legal-value validation, scope lock, JSON round-trip, safe-pack ZIP, redacted share card, and local Save Chronicle.

02

August 5, 2026 - PlZ Beta foundation

Pinned Pyodide 0.28.3 and MIT codec commit 7dc2c72a5d15948ca5f52e000981e18b3404e3b9. Added named projections and scoped `pal.hpIv`, `pal.attackIv`, and `pal.defenseIv` commands for the documented PlZ2 / 0x32 fixture.

Added unchanged round-trip, changed reparse, non-target equality, Safe Pack hash checks, loose-file browser intake, and desktop/mobile acceptance.

03

August 6, 2026 - Fourth real Pal IV

Added the existing `pal.meleeIv` property to the real PlZ command, validation, browser, and export path. The public corpus contains this decoded property on both Pal records, so the operation has its own changed-reparse and non-target evidence row.

Nickname remains locked because the public Pal records have no decoded `NickName` property. Passive replacement remains locked because the public corpus does not contain two distinct source catalog identifiers.

04

September 9, 2026 - Pal stats, players, and inventory items

Widened PlZ Beta to 26 operations: a Pal's level, experience, work speed, sanity, fullness, condensation rank, four souls, gender, nickname, passive skills, and equipped and mastered moves, plus a player's level, experience, name, work speed, sanity, and fullness. A property the Pal does not carry yet is created in exactly the shape the game writes it.

Inventory slots can now take a new item, lose one, or change quantity. Palworld reserves every slot a container will ever have, so adding fills a free slot rather than growing the container. Unique weapons and armour with their own durability record stay read-only.

05

September 9, 2026 - Guilds, bases, and Pal identity

Guild names and camp level, and base names and radius, are writable. Every Pal in the roster now carries its own generated colour token, so two rows never look alike and an Alpha or elemental variant reads as the same creature with a marker.

06

September 10, 2026 - The player's own save file

Players/<id>.sav became a write target alongside Level.sav: technology points, unlocked technologies, Paldeck registration, and the fast-travel points a save records. A Players file no command touches must come out byte-identical, and one that was edited may differ only inside the records it declared.

07

September 10, 2026 - Technologies, item moves, and large saves

The player editor lists unlocked technologies, locks any one again, and unlocks any number at once from pasted technology ids. A stack can move from one container to another in a single undoable step.

World sections the editor never edits - buildings, foliage, spawners, dungeons - are now kept as the exact bytes the game wrote, and only the containers a player owns are decoded. On a 124 MB decoded test world, a full open, edit, check, and write fell from 163 seconds to under 5 seconds on a desktop CPU, with output byte-identical to the previous release, and a 57 MB server save now opens and checks in the browser.

08

Known limitations

Species, placement, ownership, unique weapons and armour, dynamic item data, guild membership, base position, map fog, PlM/Oodle, CNK, raw GVAS, WGS, and other real-save writes remain locked.

09

Next evidence gates

Add new operation rows only after the same preservation and browser gates pass, keep failed fixtures visible, and retain restoration evidence for every published operation.

SAFE

Task checklist

  1. 01State the exact task and format.
  2. 02Link parser commit and fixture version.
  3. 03Separate parse and round-trip results.
  4. 04Keep failed fixtures and known limits visible.
FAQ

Questions people ask before touching the save

When will real PlM editing ship?

Only after the licensing route and safety test suite are both resolved. There is no date-based promise.

How can I verify a compatibility claim?

Check the task, format, game version, fixture, and validation result. Each PlZ Beta operation has its own row in the compatibility matrix.