I am currently working on a PR for another issue, which I have in draft: #2112
As part of this work, I have discovered that, at least in the latest Minecraft version, negative block state data values are sometimes populated (see screenshot). This causes a failure during rendering due to the data array being converted to a uint64, which is unsigned and does not support negative values.
Is there a reason the longs must be unsigned? I can attempt to make a change to switch from unsigned to signed 64 bit integers, but I want to know if there is any specific guidance on why unsigned was chosen in the first place. Let me know if you need a world download to test this. Also note that since the world was generated in the latest version, it will be unable to render without my fixes to world spawn location as the spawn location is no longer present in the NBT data as of the latest game drop (1.21.9).
I am currently working on a PR for another issue, which I have in draft: #2112
As part of this work, I have discovered that, at least in the latest Minecraft version, negative block state data values are sometimes populated (see screenshot). This causes a failure during rendering due to the data array being converted to a uint64, which is unsigned and does not support negative values.
Is there a reason the longs must be unsigned? I can attempt to make a change to switch from unsigned to signed 64 bit integers, but I want to know if there is any specific guidance on why unsigned was chosen in the first place. Let me know if you need a world download to test this. Also note that since the world was generated in the latest version, it will be unable to render without my fixes to world spawn location as the spawn location is no longer present in the NBT data as of the latest game drop (1.21.9).