Block: Turbo mode <on/off>

16carlsm

turbo mode [ on v]

Looks cool!

Failord

ProdigyZeta7 wrote:
This has been suggested countless times before, and rejected. Sorry, but we don't need it when we can run definition scripts on “no refresh”.

Perhaps you misread it- it's not

run this loop in turbo
    
end //fail.

but

put project player in turbo

I must say, this is an interesting idea.

Last edited by Failord (Dec. 7, 2013 21:21:02)

Failord

16carlsm wrote:
I agree. I also think there should be a block like this:
toggle "can drag" [ v]

While that's nice, I still would prefer my workaround.

Blaze349

this should be moved to help with scripts

Sonickyle

Blaze349 wrote:
this should be moved to help with scripts

Please don't necrobump threads.

RSQgame

I think It should be a block to. If you use Turbo mode in my never ending runner game It's super difficult, So I would use a block like this to make a difficulty!

A-no-meep

I think that this would also need a boolean to detect if the player is in turbo mode.

RSQgame

when [ d] key pressed

set [ Turbo Mode] to [on]

9kiwi9

turn turbo mode [on v]::events
<turbo mode?::events>

derpmeup

16carlsm wrote:
turbo mode [on v] // category=control
Looks cool!

I think that would go into the control section if it was implemented.

RSQgame

when key [ v] pressed

Turbo Mode [ on]
stop [ all]

when [ Turbo Mode] = (on)

RSQgame

Here is a better one

when [ V] key pressed

Turn Turbo Mode [on]

stop [ This Script]

Last edited by RSQgame (April 12, 2014 11:28:35)

poniesareso

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.

Exactly! In my awesome dress up game (not bragging-just excited about it :0), when i tested my project, I can't even drag and it takes WAY TOO LONG using the

glide () secs to x: () y: ()

so it would be nice.

hppavilion

16carlsm wrote:
I agree. I also think there should be a block like this:
toggle "can drag" [ v] //category=motion
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.

I think a major part of the point of scratch is that a lot of the blocks like that, which have easy workaronds, don't exist. The point is that it encourages you to use knowledge of coding instead of doing it for you. This is why I disagree with

 if on edge, bounce

It should be more like

 bounce off [ v] //category=motion

because this way, it encourages you to use an if. And you can use something like if it is enabled AND touching edge, bounce. (I know you can use if-then and put this inside, but that has a completely different if-then in the bounce, which makes no sense)
This got kind of off topic, but it still explains it.
As for the turbo block, I semi-support. Also, put //category=control after the block design (in the main post, which you should add) so it looks like this:

 turbo mode [on v] //category=control
<turbo mode on?> //category=control

Looks much better.

RSQgame wrote:

when [V v] key pressed
Turn Turbo Mode [on v] //category=control
stop [all v] //what's this for?

when <Turbo Mode on?> //category=events we need a when <> block. This is just that with a turbo mode

RSQgame wrote:

Here is a better one

when [V v] key pressed
Turn Turbo Mode [on v] //category=control
stop [This Script v]

Have you not heard of the edit button? Also, add //category=x to change color and “ v” to the end of a string to make a dropdown. I fixed it above.

poniesareso wrote:
16carlsm wrote:
*snip*

Exactly! In my awesome dress up game (not bragging-just excited about it :0), when i tested my project, I can't even drag and it takes WAY TOO LONG using the
glide () secs to x: () y: ()
so it would be nice.

 When this sprite clicked 
repeat until <not <mouse down?>>
Go to [mouse pointer v]

Last edited by hppavilion (April 12, 2014 20:38:02)

ExtremeLogic

9kiwi9 wrote:

turn turbo mode [on v]::events
<turbo mode?::events>

Support.

Last edited by ExtremeLogic (April 13, 2014 19:33:11)

spgame05

when turbo mode [on v] :: events hat

turn turbo mode [on v] :: control stack

turbo mode :: sensing reporter

Support!

Last edited by Kaj (May 21, 1362 3:27:52)

GyroscopeBill

This is cool, I support.

TeslaTech

spgame05 wrote:
when turbo mode [on v] :: events hat

turn turbo mode [on v] :: control stack

turbo mode :: sensing reporter
Support!

Last edited by Kaj (May 21, 1362 3:27:52)

i support

The_Game_Master007

JamesOuO wrote:
We need a turbo mode block. Think of all of those games that need turbo mode, but people don't know about turbo and just leave it. Also, in some games, you can cheat by using turbo mode, which is frustrating when it uses cloud data.
It should be formatted like the camera block, Toggle turbo mode (on/off) and also <Turbo mode?> for putting into operators.
This could be used for games where the terrain loads so that turbo mode is turned on during loading, then turned off afterwards.
Anyone Agree?

I agree, Im making a game and turbo is cheating for it!

MeDiaMond

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...]

Last edited by MeDiaMond (May 14, 2014 15:21:26)

Discuss Scratch