this special 1,000,000 downloads competition is a really good idea

It's not a "bug".

Even a child can understand that's a typo.

Agreed - at least a native speaker child

I just wasn't shure and only wanted to help to correct a typo in this most helpful and well-edited C2 manual ...

under old fashioned

Force of nature

I remember ... those were the glory days of the C64 ... I never was an owner of this kind of "power engine" because it was to expensive, so had to borrow one

While I'm writing these lines I feel tears in my eyes ...

and boisterous wind

... my native language is german.

Like philx I also can understand almost everything written in english. For translations I use dict.cc, dict.leo.org and sometimes linguee.de

I played with the code and tried a few things.

Your built-in slow down mechanism is very usefull for testing - thanks for sharing

Looks like your code works as a really good count down timer regardless of the resulting FPS.

I wasn't aware of the big difference between "wallclocktime" and "time" for setting the variable gvStartTime.

If "time" is used instead of "wallclocktime" the count down time differs badly from the real world time.

After reading several posts regarding time/timer topics I still don't no how to use "timescale" in a usefull way.

Can you give me an example or explanation?

You don't have to defend yourself, you helped me with the original problem (the formatting)

The time delta / delay is more a kind of sideshow, but I'd be glad to get this problem solved.

Tomorrow I'll give your new capx a try ...

uuups, I just noticed a big drawback with RamPackWobble's timer solution

When I count down from 30s to 0 it will take about 33s !!! It is 3s to slow !

I tested this on different PCs with the same result - what's wrong ?

I need a really accurate timer, so what to do?

Any help is appreciated.

good idea

working with "Set text to left(text.ivTimerText,4) " combined with a little adjustment for my special needs does the formatting trick.

Thank you.

by the way:

I didn't even think of using a timer behavior! This is much more convenient then my awkward try with calculating the time left within the condition "System | Every tick" .

I can imagine that using a timer like you did, is more resource-friendly then my way with "System | Every tick". What do you think?

https://www.scirra.com/manual/167/timer

"A single Timer behavior can keep track of multiple timers. To distinguish between then, a tag is used."

It's only a micro bug, but I think "then" should be replaced by "them".

Sorry if I'm mistaken here, but English is not my native language.