[00:48] <Tiger4942> why is the update not released yet?

[00:48] <OmnipotentEntity> Tiger4942, because

[00:48] <OmnipotentEntity> Tiger4942, https://twitter.com/OmnipotentEntit/status/427312410693607424

[00:52] <NachtFalke> Some new information?

[00:53] <JellySeer> Last minute serialization bug

[00:53] <Baloney> What does that even mean?

[00:53] <OmnipotentEntity> Baloney, if you really want to know.

[00:54] <OmnipotentEntity> we use -1 to store an invalid offset for a given size.

[00:54] <OmnipotentEntity> we call it NPos in the code base

[00:54] <OmnipotentEntity> we were serializing it as an unsigned integer, which means it has a different representation between 32-bit and 64-bit platforms

[00:54] <OmnipotentEntity> this was a solved problem in the previous area of the code we were using

[00:55] <OmnipotentEntity> because we had special code to handle that case and to renormalize it to the correct length

[00:55] <OmnipotentEntity> but we changed the code we use to serialize to the disk

[00:55] <OmnipotentEntity> so it reintroduced this bug.

[00:55] <OmnipotentEntity> I caught it when I was testing out 64-bit and 32-bit linux binaries on my box

[00:56] <OmnipotentEntity> and it crashed the game

[00:56] <OmnipotentEntity> because it attempted to access 2^32-1 rather than detecting it as -1

[00:56] <freedose> got this bug fixed?

[00:56] <OmnipotentEntity> I have one instance of this bug fixed.

[00:56] <OmnipotentEntity> the problem is:

[00:57] <OmnipotentEntity> I have to fix it for every place where we would use an NPos and serialize it to a disk

[00:57] <OmnipotentEntity> multiple places in the code

[00:57] <OmnipotentEntity> like,

[00:57] <OmnipotentEntity> the one I fixed was in the player inventory and it saved which items was marked as active in your actionbar

[00:57] <OmnipotentEntity> -1 means "no item selected"

[00:58] <OmnipotentEntity> but the code thought that the 4billionth or so item was selected

[00:58] <OmnipotentEntity> and there aren't 4 billion items