Let users disable turbo mode!

Toad-1

Toad-1 wrote:
perfectpuppies wrote:
what is turbo mode?! I need to know!
ITS where everything IZ ALL AT ONCE

go to edit and select Turbo mode.next time you see check mark.

Toad-1

Toad-1 wrote:
Toad-1 wrote:
perfectpuppies wrote:
what is turbo mode?! I need to know!
ITS where everything IZ ALL AT ONCE
go to edit and select Turbo mode.next time you see check mark.

I GOT THE FIRST POST ON THE PAGE!!!

kathryn89

To turn off turbo mode, just hold the shift key and click the green flag.

duckboycool

kathryn89 wrote:
To turn off turbo mode, just hold the shift key and click the green flag.

They mean to prevent the user from being able to use it as they could cheat, and a cheater won't do that just because.

But no support for previously stated reasons.

customhacker

No Support. Just use one of the Turbo Mode Detecting Scripts in this, and tweak it so that if Turbo Mode is on, the game stops.

DadOfMrLog

customhacker wrote:
No Support. Just use one of the Turbo Mode Detecting Scripts in this, and tweak it so that if Turbo Mode is on, the game stops.

Even better: write your scripts in such a way that it makes no difference whether turbo mode is on or off!
(That's a sensible and worthwhile thing to do anyway…)

Gaza101

DadOfMrLog wrote:
customhacker wrote:
No Support. Just use one of the Turbo Mode Detecting Scripts in this, and tweak it so that if Turbo Mode is on, the game stops.
Even better: write your scripts in such a way that it makes no difference whether turbo mode is on or off!
(That's a sensible and worthwhile thing to do anyway…)

Exactly the point I made in a previous reply. I'm glad you have the same view.

humantorch01

To take away turbo mode just add a wait (0) secs to your forever loop

forever
Everything
wait(0)secs
end

Disclaimer: I have only experimented this offline.

Last edited by humantorch01 (Feb. 10, 2017 19:25:49)

DadOfMrLog

Gaza101 wrote:
DadOfMrLog wrote:
customhacker wrote:
No Support. Just use one of the Turbo Mode Detecting Scripts in this, and tweak it so that if Turbo Mode is on, the game stops.
Even better: write your scripts in such a way that it makes no difference whether turbo mode is on or off!
(That's a sensible and worthwhile thing to do anyway…)
Exactly the point I made in a previous reply. I'm glad you have the same view.

Yup, and here's a post explaining exactly how you can do that: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/post/2439954/

Last edited by DadOfMrLog (Feb. 10, 2017 21:56:03)

Penguin5664

There's a Turbo Mode detector.

reset timer
repeat (10)
. . . // Something goes here
end
if <(timer) < [1]> then
. . . // Can be used to force players to use Normal Mode
else
. . . // Can be used to force players to use Turbo Mode

This block can be used by using message blocks, defining custom blocks or through Green Flag clicked.

>——————————————( Extra )——————————————<
Also, if you want to use a timer but cant because of the Turbo Mode detector, why not to use this?!:

forever
wait (0.1) secs
change [timer_variable v] by (1)
end

stickfiregames

Penguin5664 wrote:
Also, if you want to use a timer but cant because of the Turbo Mode detector, why not to use this?!:
forever
wait (0.1) secs
change [timer_variable v] by (1)
end

That's not an accurate way to replicate the timer. Instead, you can use the timer as a timer and use this for the turbo mode check:

define check turbo mode
set [var v] to (timer)
repeat (10)
wait (0) secs
end
if <((timer) - (var)) < [0.2]> then
using turbo mode :: #00c000
else
not using turbo mode :: #e02020
end

it's a bit more complicated if you might want to reset the timer in the middle of the check.

jromagnoli

stickfiregames wrote:
Penguin5664 wrote:
Also, if you want to use a timer but cant because of the Turbo Mode detector, why not to use this?!:
forever
wait (0.1) secs
change [timer_variable v] by (1)
end
That's not an accurate way to replicate the timer. Instead, you can use the timer as a timer and use this for the turbo mode check:
define check turbo mode
set [var v] to (timer)
repeat (10)
wait (0) secs
end
if <((timer) - (var)) < [0.2]> then
using turbo mode :: #00c000
else
not using turbo mode :: #e02020
end
it's a bit more complicated if you might want to reset the timer in the middle of the check.

And then you can use this script in a main loop:

if <<turbo :: #00c000> = [true]> then
wait (0) secs
end

stickfiregames

jromagnoli wrote:
stickfiregames wrote:
Penguin5664 wrote:
Also, if you want to use a timer but cant because of the Turbo Mode detector, why not to use this?!:
forever
wait (0.1) secs
change [timer_variable v] by (1)
end
That's not an accurate way to replicate the timer. Instead, you can use the timer as a timer and use this for the turbo mode check:
define check turbo mode
set [var v] to (timer)
repeat (10)
wait (0) secs
end
if <((timer) - (var)) < [0.2]> then
using turbo mode :: #00c000
else
not using turbo mode :: #e02020
end
it's a bit more complicated if you might want to reset the timer in the middle of the check.
And then you can use this script in a main loop:
if <<turbo :: #00c000> = [true]> then
wait (0) secs
end

Yeah, single-loop projects have it even easier. Most of them wouldn't need to disable turbo mode though, unless they were reaction-based or something, because everything within the project would still run at proportionally the right speed.

LionHeart70

Well, they could go inside the project and delete the block that disables turbo mode, so..

duckboycool

They could edit the project in any way they please, so I don't see how this is any different.

Penguin5664

jromagnoli wrote:
stickfiregames wrote:
Penguin5664 wrote:
Also, if you want to use a timer but cant because of the Turbo Mode detector, why not to use this?!:
forever
wait (0.1) secs
change [timer_variable v] by (1)
end
That's not an accurate way to replicate the timer. Instead, you can use the timer as a timer and use this for the turbo mode check:
define check turbo mode
set [var v] to (timer)
repeat (10)
wait (0) secs
end
if <((timer) - (var)) < [0.2]> then
using turbo mode :: #00c000
else
not using turbo mode :: #e02020
end
it's a bit more complicated if you might want to reset the timer in the middle of the check.
And then you can use this script in a main loop:
if <<turbo :: #00c000> = [true]> then
wait (0) secs
end

Yeah, I was just going to stat this wait (0) seconds block:

forever
wait (0) secs
. . .
end

The @stickfiregames method is also inaccurate.

Just use the block. THAT'S IT.

Ex0gen

A good compromise would be a

(turbo mode?)

block, you can still prevent cheating by stopping the game from running when it =1

Last edited by Ex0gen (May 3, 2017 12:04:06)

Undertale027

I HAVE TURBO MODE ON, IT IS ANNOYING ME & MY GAME

saofan123

No support for DRM

Penguin5664

Undertale027 wrote:
I HAVE TURBO MODE ON, IT IS ANNOYING ME & MY GAME

Then put this on all your scripts:

forever
. . .
wait (0) secs // This does the trick.
end

This, in fact works. But yeah, we need some turbo mode blocks already implemented, like in SNAP! :

turbo mode :: control reporter
turbo mode [on v]? :: sensing boolean
set turbo mode [off v] :: control stack

custom speed modifiers :: control hat
set project speed to (0.5) :: control stack // Can be used for custom project speeds, min-speed: 0.25 ---- max-speed: 3 (run without screen refresh)
if <project speed is (0.5)? :: sensing> then
. . .
end
report (project speed :: sensing) :: control cap

Last edited by Penguin5664 (June 15, 2017 20:08:48)

Discuss Scratch