Using the Time Set command resets the day to day 0 instead of just advancing to that time of day
Using the Time Set code (eg: "/time set 13000" to make it just barely nighttime) resets the day to day zero instead of just advancing to that time of day. I assume it's been like that for awhile but I'm only noticing now that the day is in the F3 menu.
What I expected to happen: Well if it's 2 hours after sunrise for example I would expect that telling it to set the time to noon (6000) would ADVANCE to noon not TURN BACK TIME to noon on the first day.
Environment
Win 8, 32bit Java
Created Issue:
Using the Time Set command resets the day to day 0 instead of just advancing to that time of day
Using the Time Set code (eg: "/time set 13000" to make it just barely nighttime) resets the day to day zero instead of just advancing to that time of day. I assume it's been like that for awhile but I'm only noticing now that the day is in the F3 menu.
What I expected to happen: Well if it's 2 hours after sunrise for example I would expect that telling it to set the time to noon (6000) would ADVANCE to noon not TURN BACK TIME to noon on the first day.
Environment
Win 8, 32bit Java
is duplicated by
is duplicated by
relates to
is duplicated by
MC-241128
Duplicate of MC-51760
Don't think you understand how the time set fully works.
/time set 24000 = day 1
48000 = day 2
72000 = day 3
If you /time set 0 you are resetting time to the beginning of time.
See I think that's counter-intuitive and not what people want out of the code. Having said that I can just adapt to using the "time add" command.
Otherwise it makes tracking days impossible. The time value has been like this as long as I can remember and I believe since MC was created. It just wasn't as obvious until they added a day counter.