Hm, I guess, based on the results so far, that my feelings about it are mostly not shared by others.
I felt like the expected behavior was that the hour should be the most significant data entered. Thus if I entered a 21, it should consider that as 21:00. Minutes would be next in significance, so if I entered 1245 it would translate directly to 12:45.
In fact, I thought this made so much sense that I wrote a line to make it work. I thought maybe it should made the default, but if most people are happy I'll just post the line so the few who aren't can use it.
If you want to try it, change chatcommands.lua (found in the builtin directory) to look like this:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
minetest.register_chatcommand("time", {
...
else
newtime = newtime * 10 ^ (5 - #string.match(param, "%S.*%S"))
minetest.set_timeofday((newtime % 24000) / 24000)
...
The added line takes the number and pads it with zeros on the right to make it 5 digits.
p.s. This change means a leading zero is required for times < 10:00. For instance setting the time to 6:00 requires an 06.