HOI4 1.19.3 Ironman save: strict melt stops on three unknown binary tokens (0x2af1, 0x49d0, 0x0000)

[vibeking252]

Summary

rakaly melt --format hoi4 --unknown-key error on a Hearts of Iron IV 1.19.3 Ironman save stops on an unknown binary token. A diagnostic run with --unknown-key stringify shows only three unknown tokens in the whole save, one occurrence each, so this looks like a small token-table gap for the newest patch rather than a format change.

Environment

• rakaly CLI 0.8.19 (release asset rakaly-0.8.19-x86_64-pc-windows-msvc.zip, Windows 11)
• Game version string from the melted header: Operation Postern v1.19.3.0.c01a (5632); save_version=33, minor_save_version=0
• Save: Ironman (header HOI4bin5), about 40 MB, single player, Australia, dated 1937.1.26

Command and result

rakaly.exe melt <save>.hoi4 --format hoi4 --unknown-key error -o melted.txt
exit 2
stderr: unknown binary token encountered: 0x2af1

The strict melt wrote 19,723 bytes of header before stopping.

Diagnostic (not used as output): --unknown-key stringify completes the melt (about 64 MB of plaintext, 3.9 million lines) and reports exactly three unknown tokens, each once:

0x2af1
0x49d0
0x0000

Notes

• No save file is attached (single-player save from a private machine); I can test a candidate build against it and report back.
• Happy to provide the surrounding plaintext context lines for each token if that helps identify them.

[nickbabcock]

Can you try out 0.8.20. It should contain 0x2af1 and 0x49d0.

0x0000 is concerning and may require more investigation if you want to upload the compressed save I can take a look.