I am sure many of us have hade a project with what seems to be a million variables, and as we are placing down tons to variable blocks in a big line are thinking "Wouldn't it be nice if I could do this in one block“ This is why I am suggesting the ”All" option to the dropdown menu in the variable block. If selected All would simply run that block to all of the variables in your project, rather than just 1. This would make using variables, something which I struggled a little with when I first started Scratch, more user friendly and streamlined.

For example:

set [All ] to [0]

Instead of

set [Random Variable] to [0]
set [Play] to [0]
set [Score] to [0]
set [Random Variable 2] to [0]
set [Clock] to [0]
set [Timer] to [0]
set [Random Variable 3] to [0]
set [etc..] to [0]

I can't see people using it much, so semi-support.

when green flag clicked
set [Number of players v] to (. . .)
wait until <<(Alive players) = [1]> or <(Timer :: variables) < [1]>>
set [All the variables v] to [0]
if <Any of the players has high score than others :: grey>
 say (join (Winner) [ won!])
end
Stop [All the scripts v]

No support, it would mess everything

This would be a help but I don't know if it is needed so semi-support

JavierR100 wrote:

when green flag clicked
set [Number of players v] to (. . .)
wait until <<(Alive players) = [1]> or <(Timer :: variables) < [1]>>
set [All the variables v] to [0]
if <Any of the players has high score than others :: grey>
 say (join (Winner) [ won!])
end
Stop [All the scripts v]

No support, it would mess everything

How would it mess things up?

Support, it gets tedious having to make every single variable hidden.

JavierR100 wrote:

when green flag clicked
set [Number of players v] to (. . .)
wait until <<(Alive players) = [1]> or <(Timer :: variables) < [1]>>
set [All the variables v] to [0]
if <Any of the players has high score than others :: grey>
 say (join (Winner) [ won!])
end
Stop [All the scripts v]

No support, it would mess everything
[Also, it will be so annoying]

It would be annoying to use one block instead of 50? Tell me more.
Also, if it'd mess everything up, don't use it, it's as simple as that.

Support for “all” and “all of this sprite” for the dropdowns in the data blocks.
Optionally the show/hide blocks could also be combined into one single block:

[show v] variable [var v]::variables // show, show large, show slider, hide

Sheep_maker wrote:

Support for “all” and “all of this sprite” for the dropdowns in the data blocks.
Optionally the show/hide blocks could also be combined into one single block:

[show v] variable [var v]::variables // show, show large, show slider, hide

Thanks of the support, also great idea for combining the show and hide into 1 block.

Support!

Basically, just allow people to set every variable to a value.

set [all v] to []

Maybe a

set [all locals v] to []

and

set [all globals v] to []

N O M O R E C O N T E N T

(Also, I won't be surprised if this was already suggested, so don't bother telling me.)

(username)

What would this be needed for? What are some example of it's use?

powercon5 wrote:

What would this be needed for? What are some example of it's use?

If we have like 100 or so variables. Maybe we can use this block to reset all variables in one block, so we don't have to individually place every set variables to () blocks just to reset all variables to 0. I want to say that sometime, individually placing every variables block to reset all variables to 0 can be exhausting and tiring.

This might be a good idea because it save workspace, but i have mixed opinions on this.
took me more time to post than i should.

Why would anyone want to set all the 100 variables to the same thing?

FutureBlack16 wrote:

powercon5 wrote:

What would this be needed for? What are some example of it's use?

If we have like 100 or so variables. Maybe we can use this block to reset all variables in one block, so we don't have to individually place every set variables to () blocks just to reset all variables to 0. I want to say that sometime, individually placing every variables block to reset all variables to 0 can be exhausting and tiring.

This might be a good idea because it save workspace, but i have mixed opinions on this.
took me more time to post than i should.

It would probably be better to use a list.

powercon5 wrote:

FutureBlack16 wrote:

powercon5 wrote:

What would this be needed for? What are some example of it's use?

If we have like 100 or so variables. Maybe we can use this block to reset all variables in one block, so we don't have to individually place every set variables to () blocks just to reset all variables to 0. I want to say that sometime, individually placing every variables block to reset all variables to 0 can be exhausting and tiring.

This might be a good idea because it save workspace, but i have mixed opinions on this.
took me more time to post than i should.

It would probably be better to use a list.

You give a good argument.

powercon5 wrote:

FutureBlack16 wrote:

powercon5 wrote:

What would this be needed for? What are some example of it's use?

If we have like 100 or so variables. Maybe we can use this block to reset all variables in one block, so we don't have to individually place every set variables to () blocks just to reset all variables to 0. I want to say that sometime, individually placing every variables block to reset all variables to 0 can be exhausting and tiring.

This might be a good idea because it save workspace, but i have mixed opinions on this.
took me more time to post than i should.

It would probably be better to use a list.

Yeah, if I make a large project I usually just throw variables out the window and use two lists instead of a hundred of them

You should probably do that if you'll have to be constantly resetting a large number of variables

But still support as it'd be pretty nice, maybe under something like that little line dividing global/local variables

There is a workaround, but support since it would be easier.

powercon5 wrote:

FutureBlack16 wrote:

powercon5 wrote:

What would this be needed for? What are some example of it's use?

If we have like 100 or so variables. Maybe we can use this block to reset all variables in one block, so we don't have to individually place every set variables to () blocks just to reset all variables to 0. I want to say that sometime, individually placing every variables block to reset all variables to 0 can be exhausting and tiring.

This might be a good idea because it save workspace, but i have mixed opinions on this.
took me more time to post than i should.

It would probably be better to use a list.

No, it wouldn't. The wiki gives no guidance on how set all the variables in a list to whatever initial value each needs to have. And the effort to build the list in the first place is more work than implementing a set all option in the block.

Support.

Skrizzle out.

To set all items in a list to a value:

set [i v] to [0]
repeat (length of [list v])
change [i v] by (1)
replace item (i) of [list v] with (value::grey)
end