The number you put into the block will determine the number of milliseconds it takes for the minute to change in the clock. Inputting 60000 ms will mean that each minute for the clock is a minute in real-life.
Also, any negative number that is put in for the clock time will be multiplied by -1 to make it a positive number, and if 0 is put in for the hour, it will be turned to 1 instead. Additionally, if the hours value is set to a number of 13 or greater, the hour will be set to 1, and the am will change to pm or vice versa. Something similar will happen with the minutes. If you set it to 60+, the hour value will change by 1.
Okay, I’ve changed the set clock speed block to be less confusing (set one second duration to [number]), and the clock now supports seconds! Just expand the return clock time block and you will have the option to make the seconds visible! The am/pm system was causing problems, so I took it out.
It would be really neat if you added individual parameter blocks for both minutes and seconds
Similar to what @UnsignedArduino said, changing the wording of the set clock speed to $number ms to set tick speed to $number ms would make it a bit easier to understand the intended usage of that block
This extension can be used to make an in-game clock. Just use the set clock time to block and input the hour, minute and second to make it! You can then use the clock time return block to get the clock time, and the rest of the blocks are just extra settings for the clock. (I hope this answers your question.) Also, I haven’t tested the extension on MeowBit yet.