Background info: I am attempting to create a very slow world border increase (+1 block per hour) that will increase to a very large area (10000 block diameter), so my timeInSeconds value I want to use are very large (36000000 for the math above).
Extra info: I have observed four distinct results from various timeInSeconds values. These results have been observed in both survival and creative modes on the PC version. This bug occurs with both the set and add functions of the world border. The sizeInBlocks value does not appear to be a factor with this bug. The previous location of the world border does not appear to be a factor with this bug either.
Results #2 and #3 are the bug I want to report.
Bug details:
Result #1) Between the values of 0 and 2147483, the world border moves incrementally at the appropriate rate and displays the appropriate message that corresponds to a border moving incrementally. (Everything works great)
Result #2) Between the values of 2147484 and 4294967, the world border moves instantly and displays a message that corresponds to a world border moving instantly (as if no value was entered in the timeInSeconds)
Result #3) Between the values of 4294968 and 45097156, the world border moves incrementally at the incorrect rate and displays the appropriate message that corresponds to a border moving incrementally, however, the value displayed does not match the value entered by me.
Result #2 repeats for values between 45097157 and 999999999.
Result #4) Values 1000000000 and above return a message "[Value entered] is not a valid number" (Not saying this is a bug, but perhaps it is)
Comments 3
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
This is most likely a datatype conversion error associated with the value of timeInSeconds.
2^31 = 2,147,483,648 (exactly 2 gigabytes)
The point at which the error occurs begins at 2,147,484...which is the above value divided by 1,000 (and rounded).
So timeInSeconds is most likely being improperly divided (or possibly truncated) when converting to seconds/milliseconds.
The Long Integer / Single datatype is exactly 4 gigabytes (2 ^ 32 = 4,294,967,296) so the error could start there, continue by dividing by 2, and then either divide by 1,000 or truncate.
Or the equivalent.