JPod update 1.3.0
Folder-aware authoring for POD1/POD1-64, plus optional POD2. POD1 is still the default.
POD1 / POD1-64
- Fixed: the writer capped entries at 4096 while the reader allowed 8192, so
Hellbender's GAME.POD (4341 entries) opened fine but wouldn't save. Both 8192 now. - Entries keep their original directory field, so Fury3's embedded .ACT palette
names survive a re-save. Renaming a RAW keeps its palette. - Over-long comments and paths are rejected instead of silently truncated.
POD1-64 promotion only happens when something actually needs the wider field. - Archives with duplicate entry names (POD uses these as overrides) are savable
again; the validator reports them instead of blocking the save. - Payload offsets pointing inside the header or directory are rejected.
POD2 (4x4 EVO) - new, opt-in, never the default
- Timestamps, per-entry and archive CRCs, and an audit trail for
add/remove/replace/rename/move, with author and history viewer. - Explicit POD1 <-> POD2 conversion, warns before dropping POD2-only metadata.
Editor
- Create, rename and move folders, internal drag and drop, recursive folder import.
- Save in place alongside Save As.
- Validate Archive: limits, unsafe and duplicate paths, overlapping ranges,
palette records, checksums, output layout. - PODTool-compatible response files (podFilename:, volumeName:, // comments).