3 ms·
Some kind of overflow, it resets timer to 40 hours. Same thing happens with 1 year, except timer is reset to 60 hours. Another interesting observation is that "
by TrainedMonkey 4y ago
Some kind of overflow, it resets timer to 40 hours. Same thing happens with 1 year, except timer is reset to 60 hours. Another interesting observation is that "timer 723 years" did not bring timer up, but "timer 722 years" did.
Update: "timer 100 hours" works, but "timer 101 hours" does not. That is 100 hours is 144,000 seconds, does not seem to be anything special about this number.
- jefftk 4y agoSometimes it drops to 40hr, other times to 100hr. Haven't been able to figure out what the pattern is.
- buildbot 4y ago725 years causes it to glitch twice
- buildbot 4y agoI got it to reset twice in row by using 725 years, reset to 63 then 99!
- bhaney 4y agoIt can just only handle two digits in the hours place after the first tick. Any other digits get removed. 1 year becomes 60 hours because it turns 1 year into 8760 hours, then removes the "87" and leaves the "60" Edit: this seems like it's just a display bug and the original time is still preserved. If you search "timer 100 year 1 second" then it formats to "876000h 00m 01s", then the next tick shows "0s", then the next tick shows "99h 59m 59s" > Another interesting observation is that "timer 723 years" did not bring timer up That is weird. Even weirder that "timer 723 year" (singular) does seem to work.