CommandBook
CommandBook copied to clipboard
Published
20 hours ago •
EngineHub
EngineHub
24-hour notation of time is inaccurate
CMDBOOK-2231 - Reported by .
0 in time tick is normally considered as 6 am, but this plugin shows time tick 0 as 8 am.
Comment by wizjany
Mathmatically looks fine to me. Whoever "normally considers" 6 am is wrong probably.
0 0 sec day
600 30 sec
1200 1 min
1800 90 sec
2400 2 min
3000 150 sec
3600 3 min
4200 210 sec
4800 4 min
5400 270 sec
6000 5 min
6600 330 sec
7200 6 min
7800 390 sec
8400 7 min
9000 450 sec
9600 8 min
10200 510 sec
10800 9 min
11400 570 sec
12000 10 min sunset
12600 630 sec
13200 11 min
13800 690 sec night
14400 12 min
15000 750 sec
15600 13 min
16200 810 sec
16800 14 min
17400 870 sec
18000 15 min
18600 930 sec
19200 16 min
19800 990 sec
20400 17 min
21000 1050 sec
21600 18 min
22200 1110 sec sunrise
22800 19 min
23400 1170 sec
Comment by .
First, sorry for using wrong words. "Time tick" had to read "Minecraft time." But when the sun is just on the player's head, what we call "noon", the MC time is 6000. Also midnight, when the moon is just on the head, is corresponding to 18000 of MC time. These show that 0 in MC time should be 6 am in 24-hour notation.