Currently, when you make a block, you can only use the block in that sprite, which is annoying. When you make a project with a lot of procedures and a lot of sprites, you end up duplicating the same block definition again and again (imagine if you need to make one little change!) I propose that it should be like variables: you have a little tickbox for local block or global block

OK, this is getting ridiculous; there are nearly one-hundred supporters and still no feature. Argh.

Support

+1

Support!

+1

Yes please! -It's a bit tedious to have to do such things across sprites via broadcast-and-wait with global variables for the ‘parameters’.

One practical implementation question that comes to mind about this, though, would be concerning clones… if you have some sprite that runs a global custom block that's in some other sprite which has clones, would it be just the original sprite that runs it (in which case, you only get to work with its own local vars at that point)? Or would it be all clones as well that run it (like all clones also receive broadcasts - and which could lead to all sorts of possible unexpected behaviour for those who don't quite realise this is what happens)?

I guess a possible alternative to the local/global checkbox (if there's a reason why that isn't so easy to implement, and which doesn't have the clone question above) might be to have (the option for?) custom blocks on the stage be available to all…?

I have run into the problem a lot - support!

Global custom blocks, yes!

+1

YEEEESSS!!! support

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

10 supporters so far!

Anyone got any thoughts about the implementation question I brought up above? (-Whether or not all clones of a sprite also run the global custom block when you use it…)

And another (fairly minor) practical implementation question (but also partly a topic bump): how should they be shown? Presumably, they get listed in the “More Blocks” section for all sprites - can't think of another way - but are they separated from the local ones by a divider? (Like local vs global sprite variables used to be in the 2.0 beta - and I kinda miss that, even though the alphabetical sorting certainly helped in other ways… I keep meaning to start globals with a specific character to make it like that again, but keep forgetting )

I'll support.

sxsaxAr+waxBr-*

Hi,

Just started Scratch with my three kids a couple days ago.

Yes! My daughter and I were just talking about this. Global Blocks would be awesome! It would enable you to create behaviors like “Dance” that any sprite could use.

Paul
(Dad of three Scratchers)

Thanks! (a.k.a., bump)

I very much support this!

this is one of the most problems iget when i use custom blocks!
Defenitly SUPPORT!

I know I support this before, but how would global custom blocks be distinguished from local custom blocks? Maybe for the sprite only, there could be “sprite1: custom block name” like how local variables look on the stage.