johnathoni

Does time naturally advance this way once it gets close to the Integer.MAX_VALUE limit?

Is your gamerule tick-rate set to the default?
Are you using a command block to speed up or slow down the passing of time?

I'm wondering that if you have the default tick speed, and no command blocks, just vanilla gameplay, if this would still even happen? perhaps it was forced into the negatives by skipping the value it checks for (checking for greater than max value and not for less than min value, negative numbers). I assume your proposed fix would fix this issue, I'm just curious if this would occur naturally, and after how long? 2,147,483,648/200 (bedrock tick speed) by my calculations, this would only naturally occur after one hundred and eighty hundred thousand (180,000) minutes, or 124 real life days. I've played on a worlds much older than this, yet have never once ran into this issue, is why I ask. My question is, does this have to do with speeding up time? Or maybe do you have your time day cycle in game set to match real life days? (I have a friend who did this with his world).

This is really in-depth for a bug report, i've been having a similar issue on Windows10 - I'd managed to lock myself out of the game, though I can only imagine its for different reasons (since diff platform).

this sounds like an issue with that particular world. do other worlds work?