f1lip wrote:

just use a variable.

No support.

no because scratch will do every frame plius a millisecond

-iviedwall- wrote:

Scratch has speeded 30 frames per second, which there will be a 0.033 secs (or 33 millisecs) delay between every movement even there are no wait blocks, and apparently, it's the fastest speed on Scratch (unless you have TurboWarp, you can make the speed 2 times faster) without any other modes, so we don't have to track down every millisec.

So you can go to 31 without turbo warp or turbo mode, but frame rate is variable and can change so we couldn't track it

I know I’m late to this discussion, but I have a project that gets the current millisecond without those annoying floating point errors. Here’s the link: https://scratch.mit.edu/projects/1050410199/

MathlyCat wrote:

Confusing to new scratchers is not a valid reason. Please be ore respectful to newer users of our community; they could do their research and find out.

Also, if you actually knew how a clock works than it goes by a single second. Very few real clocks time in shorter amounts due to convience.
No support, if it's only for animations that's not enough.

Do you expect an 9-10 year old to understand how stuff like that works? Unless they're gifted (as in smart) or something.

Contradictory to what most of the people who posted on the first page seem to think, this would actually make finding the current millisecond less confusing for New Scratchers. It goes from three blocks (which not everyone may understand, or at least understand why they work in this particular case) to one.

The timer is not a good workaround since it lags with the project and therefore is not useful for this purpose. Nor is a variable being updated every millisecond, since Scratch actually won't run it that fast regardless.

Potential uses:
- Precise timing. This would lessen timing inaccuracies with the current solution to this (which takes time of its own to run, and therefore reports values slightly higher than the millisecond; while this block would also take some time to run, it would return the current millisecond on most computers in less than a millisecond). This makes it very useful for accurately timing scripts and FPS counters.
- Clocks that display milliseconds (does come up occasionally)

BigNate469 wrote:

Contradictory to what most of the people who posted on the first page seem to think, this would actually make finding the current millisecond less confusing for New Scratchers. It goes from three blocks (which not everyone may understand, or at least understand why they work in this particular case) to one.

The timer is not a good workaround since it lags with the project and therefore is not useful for this purpose. Nor is a variable being updated every millisecond, since Scratch actually won't run it that fast regardless.

Potential uses:
- Precise timing. This would lessen timing inaccuracies with the current solution to this (which takes time of its own to run, and therefore reports values slightly higher than the millisecond; while this block would also take some time to run, it would return the current millisecond on most computers in less than a millisecond). This makes it very useful for accurately timing scripts and FPS counters.
- Clocks that display milliseconds (does come up occasionally)

Correct me if I am wrong, but don't stopwatches use milliseconds?

Timer and days since 2000 already report to the millisecond, but I suggest that it be made to go down to the microsecond for super high precision timing. Ive had several instances where I've needed to measure to that precision.

Macie1234 wrote:

I think that

should be added because it makes timing more accurate in many cases. I know that you can use

but this can be confusing to younger scratchers.

THANK YOU SO MUCH FOR THIS!!!

Sheep_maker wrote:

Macie1234 wrote:

Abstract- wrote:

Macie1234 wrote:

Abstract- wrote:

No Support. We don't need to track down every millisecond.

Think animations and clocks

Most real clocks don't track milliseconds.
How would this be used in animation?

Timing between frames.
In clocks, sometimes you want to have a smooth second hand.

Animations don't use the current time blocks. They use the wait blocks which can wait for units less than a second.

I find they get really innaccurate for anything below 0.1 secs tho

Why can't we add a block like this to make life easier for young, new Scratchers? It could be essential for those seeking accurately timed animations or games. Scratch is all about being a beginner-friendly way to learn programming, mostly through games and animations, isn't it? So why complicate that experience without adding a helpful, prerequisite block?

BTW @Macie1234, thank you for posting that block. Now scratchers can use the block to get milliseconds

Thanks and Regards,
@Cruzerblade14_group

Sure, there are workarounds. But they are advanced, and it won't clutter up anything if its in a dropdown Support.