mirror of
https://github.com/curioustorvald/Terrarum.git
synced 2026-03-07 12:21:52 +09:00
idea for deterministic save format?
This commit is contained in:
@@ -43,11 +43,11 @@ Ord Hex Description
|
||||
# A payload is consisted as follows:
|
||||
#
|
||||
# Literal Description
|
||||
# "\0pLd" Payload header [00, 70, 4C, 64]
|
||||
# "\0pLd" Payload header [00, 70, 4C, 64]
|
||||
# [4] Identifier. 4 lettres ASCII string
|
||||
# [6] Uncompressed size of DEFLATEd binary (max size 256 TB)
|
||||
# [6] Length of the actual payload (max size 256 TB)
|
||||
# [..] DEFLATEd binary (begins with one of these: 0x789C, 0x78DA, 0x7801)
|
||||
# "EndPYLd\xFF" Payload footer [45, 6E, 64, 50, 59, 4C, 64, FF]
|
||||
|
||||
|
||||
Payload "TERR" -- world terrain data in Uint16
|
||||
@@ -92,7 +92,3 @@ EOF 4D M
|
||||
EOF FF Byte order mark
|
||||
EOF FE Byte order mark
|
||||
|
||||
|
||||
* To read layers: you'll need to search for specific strings, namely ["TERR", "WALL", "WIRE"]
|
||||
* It is possible that compressed data happen to replicate any of the internal identifiers
|
||||
(e.g. "\0pLdTERR", "EndTEM\xFF\xFE", "EndPYLd\xFF"), but such probability is very low (0.000000000000000005421 %)
|
||||
|
||||
Reference in New Issue
Block a user