Let users disable turbo mode!

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 // 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

I quoted accidentally .-.' Delete this comment!

Last edited by Penguin5664 (June 15, 2017 20:10:58)

Penguin5664

stickfiregames wrote:
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.

As I've stated before, this is inaccurate, in fact, you cant use the [wait (0) secs] block as it ruins up the checker, Turbo Mode just speed-ups the loops, but Turbo Mode doesn't speed-up the [wait (…) secs] block. Instead, use BPS as in a project (Blocks Per Second), so there is the script:

when gf clicked
set [oldx v] to (x position) // Ensures the detector position.
forever
reset timer
repeat until <(timer) > (0.1)>
change x by (1)
end
set [project_speed v] to ((x position) - ([oldx v] :: variables)) // Checks the project speed.
set x to ([oldx v]:: variables) // Fixes the position for the new speed.
if <([project_speed v] :: variables) > (10)> then // If the speed is larger than 10, Turbo Mode is on.
. . .
else
. . .
end
end

Also, be sure to use the [. . .] instead of [using turbo mode] and [not using turbo mode].

Last edited by Penguin5664 (June 15, 2017 21:42:14)

GenderTheBender

I wan't to be able to turn off turbo mode myself, But this is not working. Sorry for the inconvenience. or are you just saying you WANT to be able to. that would make more sense. Again, sorry.

when green flag clicked
forever
if <confused> then
say [Sorry!] for (2) secs

end
end

Last edited by GenderTheBender (Aug. 20, 2017 11:51:08)

ComicWorldBros

It a good idea, support.

At first I was like, no but reading people post reason why about this make me want to change to YES!

I-Iz-A-Litten

no support, there are ways to detect turbo mode,

Charles12310

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

Randomness-TV

Charles12310 wrote:

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

Penguin5664

Randomness-TV wrote:

Charles12310 wrote:

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

Hey, dont only quote…

Penguin5664

Charles12310 wrote:

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

I'd better suggest this:

<turbo mode [on v]? :: control >
<turbo mode [off v]? :: control >

turbo mode [on v] :: control
turbo mode [off v] :: control
turbo mode [toggle v] :: control

turbo mode on at speed of () secs :: grey // Turbo mode works for a bit faster delays, not for speeding up the project.

(turbo mode speed :: grey ) // Same as above

when turbo mode is [on v] :: hat grey // Nobody would care of checking turbo mode while the project is stopped, so no support for the block.

Charles12310

Penguin5664 wrote:

Charles12310 wrote:

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

I'd better suggest this:

<turbo mode [on v]? :: control >
<turbo mode [off v]? :: control >

turbo mode [on v] :: control
turbo mode [off v] :: control
turbo mode [toggle v] :: control

turbo mode on at speed of () secs :: grey // Turbo mode works for a bit faster delays, not for speeding up the project.

(turbo mode speed :: grey ) // Same as above

when turbo mode is [on v] :: hat grey // Nobody would care of checking turbo mode while the project is stopped, so no support for the block.

“when turbo mode is (off)” would be the best way to detect Stop Sign clicking, since Turbo Mode goes off when the project stops.

Also what does Toggle do?

Penguin5664

Charles12310 wrote:

Penguin5664 wrote:

Charles12310 wrote:

// Support

<turbo mode? :: control >

turbo mode [on v] :: control

turbo mode [off v] :: control

turbo mode on at speed of () secs :: control

(turbo mode speed :: control )

when turbo mode is on :: control :: hat

I'd better suggest this:

<turbo mode [on v]? :: control >
<turbo mode [off v]? :: control >

turbo mode [on v] :: control
turbo mode [off v] :: control
turbo mode [toggle v] :: control

turbo mode on at speed of () secs :: grey // Turbo mode works for a bit faster delays, not for speeding up the project.

(turbo mode speed :: grey ) // Same as above

when turbo mode is [on v] :: hat grey // Nobody would care of checking turbo mode while the project is stopped, so no support for the block.

“when turbo mode is (off)” would be the best way to detect Stop Sign clicking, since Turbo Mode goes off when the project stops.

Also what does Toggle do?

Not really, Turbo Mode does not disable when the Stop Sign is clicked, since you can also toggle it when the project is stopped.

Toggle turns it on and off, depending if the Turbo Mode is disabled or enabled. That suggestion is not support-guaranteed. XD

Botcho_Otkho

abh206 wrote:
MushroomMan99 wrote:
Why do you need to disable turbo mode?
It lets you cheat and it's not cool. Turbo mode is POINTLESS. Oh, wait, is has a point……….I lied.

How can Turbo Mode let you cheat?

bl111006

move () steps
move () steps

PokemonScratch101

+1 Support

FoxesAreTheCutest12

when green flag clicked block when green flag clicked block

forever forever

set time to 0 (varible) change time by 1 (varible)

repeat 10 wait 0.01 seconds
_______ _______________

if time > 2 then

(turbo mode off)

else

(turbo mode on)
_____________

FoxesAreTheCutest12

when green flag clicked block when green flag clicked block

forever forever

set time to 0 (varible) change time by 1 (varible)

repeat 10 wait 0.01 seconds
_______ _______________

if time > 2 then

(turbo mode off)

else

(turbo mode on)
__________________________

portalpower

RandomPerson1789 wrote:
MushroomMan99 wrote:
Why do you need to disable turbo mode?
cheeting on games

I don't get how you would use turbo mode to cheat, most of the time turbo mode makes games harder

lovecodeabc

stickfiregames wrote:
I think he means let the project creator disable turbo mode, judging by the scripts, probably to prevent cheating in games.

I support
turbo mode on :: control

turbo mode off :: control
(turbo mode? :: sensing)
but for now you can use this and tell them to turn off turbo mode.

Edit: Actually, is there a way to force the screen to refresh? That would have the same effect as not being in turbo mode.

USE THE CONSOLE and type location.reload() in your javascript.

BaBy_Fin

MegaApuTurkUltra wrote:
No support. Use timer+switch costumes to detect turbo mode and do whatever action you think is necessary. I think turbo mode is fine, and some intensive projects like mine need it.

just because there is a workaround does not mean the feature should not be added.
support, this could help games that need turbo mode to be able to use turbo mode, and projects that don't need can turn it off to prevent cheating.

TopicBumper

Bump.

Maybe I should use my main account so I don't deal with the 120-second rule. Though, 18 20 illegitimate children is a lot, let alone 18 20 illegitimate posts falsely boosting my post count.

Last edited by TopicBumper (Feb. 18, 2021 02:29:52)

Discuss Scratch