Ah, that makes sense
Also, please refer to my last commits referred here: https://github.com/StarMade/StarMade/pull/6
The first ~64KB section is mostly understood now
* The first 32KB section is a table which I called chunkIndex table. It is arranged in 16x16x16 grid and consists of an int which is an index into the list of chunks and an int which is the chunk size in bytes. The ship origin will be in the middle of the grid and nonexistant chunks have an index of -1.
Note: I found out that it\'s possible for the file to contain redundant/unused chunks which are not referenced by the index table
* The second 32KB section is a table consisting of timestamps. It is also arranged in a 16x16x16 grid and is a long int in millisecond time format. Nonexistant chunks may have a 0 timestamp but I also found that empty chunks nearby to the ship are seemingly \"preallocated\" with a timestamp
Also, please refer to my last commits referred here: https://github.com/StarMade/StarMade/pull/6
The first ~64KB section is mostly understood now
* The first 32KB section is a table which I called chunkIndex table. It is arranged in 16x16x16 grid and consists of an int which is an index into the list of chunks and an int which is the chunk size in bytes. The ship origin will be in the middle of the grid and nonexistant chunks have an index of -1.
Note: I found out that it\'s possible for the file to contain redundant/unused chunks which are not referenced by the index table
* The second 32KB section is a table consisting of timestamps. It is also arranged in a 16x16x16 grid and is a long int in millisecond time format. Nonexistant chunks may have a 0 timestamp but I also found that empty chunks nearby to the ship are seemingly \"preallocated\" with a timestamp