In some projects - like games - turbo mode may give the player an unfair advantage.

A work around for this is using the wait block. At the end of every script, put a wait block, with the value 0.0000000000001.

If you want a more seamless approach, do a wait block after every block!

Good idea.
But is it possible to tell the player not to use turbo mode.
Then inside the game you could use the timer and see that the time laps are quicker than normal. If so, you exclude or “pause” the game for that player …
?

andre_rifaut wrote:

Good idea.
But is it possible to tell the player not to use turbo mode.
Then inside the game you could use the timer and see that the time laps are quicker than normal. If so, you exclude or “pause” the game for that player …
?

The timer runs the same speed in Trubo. You could still use it in relation to how fast a bunch of script blocks run, however.

Failord wrote:

andre_rifaut wrote:

Good idea.
But is it possible to tell the player not to use turbo mode.
Then inside the game you could use the timer and see that the time laps are quicker than normal. If so, you exclude or “pause” the game for that player …
?

The timer runs the same speed in Trubo. You could still use it in relation to how fast a bunch of script blocks run, however.

Well, this is because timers run the same that you can measure the difference of delay when executing, for instance,
<repeat 10> <if <ln 3> = <ln 5> > nothing <end if> <end repeat>
Then you can tell eiher that the computer is too lazy, or it is too quick … independently of the turbo mode …

You can’t make. Just type “Use in turbo mode” on introductions.














My profile | My best project | My pfp maker