Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
I have just realized, when trying to update the information on PAK format in the wiki, that there's a fundamental flaw in the format design. It doesn't take endianness into account at all. When reading and writing the number of chunks and the chunk header, no endianness conversions are performed, meaning that a file saved on one platform is unusable on another platform.
Traditionally, MCServer has been used on Intel, so we probably could declare that it uses little-endian formatting, and fix the code to that. What do you think?
Posts: 1,450
Threads: 53
Joined: Feb 2011
Thanks: 15
Given 120 thank(s) in 91 post(s)
Isn't the pak format deprecated?
Why not leave it as it is for the moment, and set anvil as the default saving scheme
Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
06-10-2012, 09:14 PM
(This post was last modified: 06-10-2012, 09:15 PM by xoft.)
It does not, necessarily - if anyone's using PAK files on a big-endian platform (older Macs, I think ARM is big-endian, too), they will lose their worlds with such a change.
PAK is actually the default now (if you don't set [Storage].Schema or set it to "Default", PAK is used)
Posts: 1,450
Threads: 53
Joined: Feb 2011
Thanks: 15
Given 120 thank(s) in 91 post(s)
Why would they lose their worlds? I'm talking about NO change, only set the default saving to Anvil. If they already have a world, that world's saving scheme is set to PAK, and that won't change by changing the default scheme.