This is what happens with rounding inaccuracy
Explained a little better (I hope I understand what's happening here):
Blockland can only have numbers precise to a certain point. It can only have a certain number of significant figures.
A significant figure is the part of a number that's actually measured. 0.001 has 3 sig figs. 1000 only has 1, while 1000. has 4.
The rules are:
>Any NONZERO digit is a significant figure.
>Any ZERO between two NONZERO digits is a significant figure.
>Any ZERO after a NONZERO digit, or a TRAILING ZERO, is a significant figure.
>If there's a decimal point, any zeroes between the nonzero and the decimal are significant.
>Ex: 1000 = 1sf, 1000. = 4sf
>Any LEADING ZERO (ex. [0.000]75) is NOT a significant figure.
Check wikipedia or something.
So, if you go out far enough, those decimals get destroyed to make room for the larger values.
For example, I think the number of digits is 16, so...
Let's say the player is at 356, -10247689305258923.48586, 1.
This is 17 integer digits, 5 decimal digits.
Now, it can only have 16 significant figures at a time.
So, to make room, it deletes some of them.
The coordinates are now 356, -10247689305258920.00000, 1.
See those numbers that turned into zeroes? Those aren't significant figures anymore so Blockland ignores them, letting it pay attention to the larger numbers instead.
The player jumps around in steps of 10 units in this area. This messes everything the heck up.
