Block: Turbo mode <on/off>

D-Zi

16carlsm wrote:
I agree. I also think there should be a block like this:
toggle "can drag" [ v]
This way, in dress-up games, when the game starts, you can drag the clothes, but when you're finished, you can't. There is a workaround, but it's easier to put everything in one block.

or

DESTROY [ v]

minekraftkid

when turbo mode on

minekraftkid

when turbo mode switches to [ on]

go to x: (crazy) y: (crazy) z: (crazy)

or you could do

if <<turbo mode?> = [on]> then
    
set [ crazy] to [on]
end

minekraftkid

when [ awesome] < (epic)

forever
    
set [ turbo] to (pick random (on) to (off))end

AonymousGuy

MeDiaMond wrote:
There's no turbo mode block and it seems like there won't be one too, but if you make a project you'd need it in there's kind of workaround:
You can figure out if turbo mode is on or off with the timer and then let your project say if turbo mode is on: ‘Turbo mode is on. Please keep it on!’ and if it's off: ‘Turbo mode is off. Please turn it on! (Shift + Gf)’.
how to figure it out:
when green flag clicked
if <(timer)> [0.1]> then
say [turbo off...]
else
say [turbo on...]

Even better:

when gf clicked
forever
reset timer
end

when [timer v] > (0.1)
say [TURBO ON!]

That way, it will detect turbo even if it's not activated beforehand.

minekraftkid

when I receive [ a great progect and its in turbo mode]

forever
    if <[ progect] contains [more than 30]> then
insert [project] at (my folder) of [username]

if <not <(project scripts) > [30]>> then
insert [the project] at (the beginning) of [my sisters acount]
reset timer
keep looking[and keep shearching]

it was just an idea

davidkt

Use Run without Screen Refresh. Create a custom block (More Blocks > Create a Block), go to Options, and check “Run without screen refresh”. Put your would-be-turbo-moded scripts in there. While it's not exactly turbo mode, it works.

savaka

No support. On slow computers it could probably crash the flash player. What we really need is for it to not “hide” the turbo mode.

Thepuzzlegame

I think scratch should add two more blocks to the sensing category: a set turbo mode to block with three dropdowns consisting of on, off, and reverse as well as a boolean block which reports true if turbo mode is on and false if it isn't. These blocks can be seen below:

set turbo mode to [on v]::sensing
set turbo mode to [off v]::sensing

<turbo mode?::sensing>

Why do I think the Scratch team should implement this? Because with these two simple a blocks a whole new range of complexity can be added to scratch projects. The set turbo mode to block could be used to quickly render something and then be toggled off so as not to interfere with regular gameplay. The turbo mode? block could be used to detect cheating and adjust the project accordingly. Additionally, when told to play a project in turbo mode many new scratchers are unaware of this feature and how to activate it. However with the set turbo mode to block there would be no need for all the extra explanation and the user could make turbo mode activate automatically!

Some more examples of how these two blocks could be used can be seen below:

when green flag clicked
set turbo mode to [on v]::sensing
render level //category=custom
set turbo mode to [off v]::sensing
...


when green flag clicked
forever
    
if <<turbo mode?::sensing> = [true]> then
    
say [No cheating!] for (1) secs
set turbo mode to [off v]::sensing
end

end


when green flag clicked
forever
    
if <touching [player v] ?> then
    
say [Speed boost!] for (1) secs
set turbo mode to [on v]::sensing
wait (3) secs
set turbo mode to [off v]::sensing
end

end

Well there you have it. I would love it if these blocks were implemented into scratch. Let me know what you think!

Last edited by Thepuzzlegame (July 30, 2014 22:35:46)

gigapouch_test

Awesome! I too think this should be implemented.

Mr_sprite

I agree! (Is this why you wanted to edit the Scratch code?)

AonymousGuy

A few things:
1) What does reverse do?
2) Turbo mode / cheating can already be (relatively simply) detected.
3) For rendering levels, etc. just use custom blocks without screen refresh.

Thepuzzlegame

AonymousGuy wrote:
A few things:
1) What does reverse do?
2) Turbo mode / cheating can already be (relatively simply) detected.
3) For rendering levels, etc. just use custom blocks without screen refresh.

1. Reverse sets turbo mode to the opposite of what it already is
2. True, however many scratchers overlook turbo mode as a form of cheating and the addition of these blocks would raise awareness of this issue as well as make it easier for scratchers to prevent it. Additionally, although turbo mode can be detected it can't be toggled. So if a user was caught cheating then the only way to stop them would be to stop the game, however with these blocks you could just deactivate turbo mode and the user wouldn't lose their progress.
3. Turbo mode works even faster than this, and run without screen refresh blocks have a few bugs (try putting a stop this script block into them)

Last edited by Thepuzzlegame (July 29, 2014 05:15:47)

Thepuzzlegame

Mr_sprite wrote:
I agree! (Is this why you wanted to edit the Scratch code?)

It is one of many reasons

TimothyLawyer

Thepuzzlegame wrote:
1. Reverse sets turbo mode to the opposite of what it already is

Slo-mo?

Thepuzzlegame

TimothyLawyer wrote:
Thepuzzlegame wrote:
1. Reverse sets turbo mode to the opposite of what it already is
Slo-mo?

What I mean is if turbo mode were on it would set it to off and vice versa

Math_Addict

I agree!

BSH1

Support! Although the Boolean is workaroundable the workaround it not 100% reliable

stickfiregames

Support.
“Reverse” is a bit of an ambiguous name though, and I would change them to control blocks.

AonymousGuy

Thepuzzlegame wrote:
AonymousGuy wrote:
A few things:
1) What does reverse do?
2) Turbo mode / cheating can already be (relatively simply) detected.
3) For rendering levels, etc. just use custom blocks without screen refresh.
1. Reverse sets turbo mode to the opposite of what it already is
2. True, however many scratchers overlook turbo mode as a form of cheating and the addition of these blocks would raise awareness of this issue as well as make it easier for scratchers to prevent it. Additionally, although turbo mode can be detected it can't be toggled. So if a user was caught cheating then the only way to stop them would be to stop the game, however with these blocks you could just deactivate turbo mode and the user wouldn't lose their progress.
3. Turbo mode works even faster than this, and run without screen refresh blocks have a few bugs (try putting a stop this script block into them)

As far as I know, no screen refresh blocks are the fastest thing possible in Scratch. (They can do lots of maths and rendering almost instantly!)

Also, cheating with turbo mode doesn't really work in a lot of games.

Discuss Scratch