when I receive [ message1 v]:: Events
broadcast [ message1 v]:: Events
broadcast [ message1 v] and wait:: Events

define Your block:: custom
Your block:: custom

add [variable v]. Name:[variable name]:: gray

add [list v]. Name:[list name]:: gray

add [list v]. Name:(join (username) ['s to do list):: gray
(join (username) ['s to do list)

Remove Broadcast:
No support, how do you want that Sprite 1 broadcasts to Sprite 2 of do something ?
Custom blocks are only working on their sprite.

add [variable v] with name [] :: variables

No support, if we do:

when green flag clicked
forever
add [variable v] with name [LOL YOUR HAPPY NOW] :: variables
end

when green flag clicked
set [Spam v] to [1]
forever
create variable ((Spam) + (1)) :: variables
end

The4thPixel wrote:

My reactions to all the suggestions listed in the OP:

1. Why would messages be removed? They have a very helpful purpose of communication between sprites.
2. Making “add variables/lists” shouldn't be added because they would be abused, easily.

when green flag clicked
set [Spam v] to [1]
forever
create variable ((Spam) + (1)) :: variables
end

Executing this script would crash the Scratch player, and/or the browser used to open the project. You could also do the same thing with an “add list” block.

braxbroscratcher wrote:

The4thPixel wrote:

My reactions to all the suggestions listed in the OP:

1. Why would messages be removed? They have a very helpful purpose of communication between sprites.
2. Making “add variables/lists” shouldn't be added because they would be abused, easily.

when green flag clicked
set [Spam v] to [1]
forever
create variable ((Spam) + (1)) :: variables
end

Executing this script would crash the Scratch player, and/or the browser used to open the project. You could also do the same thing with an “add list” block.

Problem is, there's already hacked blocks for it. So your point is moot.

Sigton wrote:

With hacks you can create this block; and it's a simple hack at that
Just be careful not to recursively create variables; it doesn't end well, trust me, I've tried ;P

Sigton

Ceo_ wrote:

Remove Broadcast:
No support, how do you want that Sprite 1 broadcasts to Sprite 2 of do something ?
Custom blocks are only working on their sprite.

The4thPixel wrote:

My reactions to all the suggestions listed in the OP:
1. Why would messages be removed? They have a very helpful purpose of communication between sprites.

The4thPixel wrote:

My reactions to all the suggestions listed in the OP:

1. Why would messages be removed? They have a very helpful purpose of communication between sprites.
2. Making “add variables/lists” shouldn't be added because they would be abused, easily.

when green flag clicked
set [Spam v] to [1]
forever
create variable ((Spam) + (1)) :: variables
end

Executing this script would crash the Scratch player, and/or the browser used to open the project. You could also do the same thing with an “add list” block.

woodchester50 wrote:

The4thPixel wrote:

My reactions to all the suggestions listed in the OP:

1. Why would messages be removed? They have a very helpful purpose of communication between sprites.
2. Making “add variables/lists” shouldn't be added because they would be abused, easily.

when green flag clicked
set [Spam v] to [1]
forever
create variable ((Spam) + (1)) :: variables
end

Executing this script would crash the Scratch player, and/or the browser used to open the project. You could also do the same thing with an “add list” block.

Hello! Just sayin, you can kind of already crash the scratch player already.
Oh and read https://scratch-mit-edu.ezproxy.canberra.edu.au/discuss/topic/212098/

raisinr wrote:

Ceo_ wrote:

Remove Broadcast:
No support, how do you want that Sprite 1 broadcasts to Sprite 2 of do something ?
Custom blocks are only working on their sprite.

The4thPixel wrote:

Why would messages be removed? They have a very helpful purpose of communication between sprites.

You're right. i was thinking about a project i was making that only had one sprite.

awesome-llama wrote:

No Support. Custom blocks can only communicate within a sprite, broadcasts can contact other sprites.

define Your block:: custom

raisinr wrote:

The block will add a list or variable, and there should be a way to have blocks for that list or variable, but what if the block adds a list or variable that is named raisinr's to do list:

add [list v]. Name:(join (username) ['s to do list):: gray
(join (username) ['s to do list)

I haven't figured that part out yet.

edward789121 wrote:

you shouldn't really suggest blocks to go away.

The4thPixel wrote:

edward789121 wrote:

you shouldn't really suggest blocks to go away.

Unless that block's purposes are being replaced by a more commonly used block, or another good reason. But I do agree with you.

raisinr wrote:

First, you should delete the broadcast blocks.

when I receive [ message1 v]:: Events
broadcast [ message1 v]:: Events
broadcast [ message1 v] and wait:: Events

Why? Because you can do a lot more with making your own blocks.

define Your block:: custom
Your block:: custom

The block you make is the ‘broadcast’ block, and the ‘define’ block is the ‘when i receive’ block.

Ceo_ wrote:

Remove Broadcast:
No support, how do you want that Sprite 1 broadcasts to Sprite 2 of do something ?
Custom blocks are only working on their sprite.

The4thPixel wrote:

Why would messages be removed? They have a very helpful purpose of communication between sprites.

awesome-llama wrote:

No Support. Custom blocks can only communicate within a sprite, broadcasts can contact other sprites.

define Your block:: custom

Your Block:: custom

raisinr wrote:

raisinr wrote:

The block will add a list or variable, and there should be a way to have blocks for that list or variable, but what if the block adds a list or variable that is named raisinr's to do list:

add [list v]. Name:(join (username) ['s to do list):: gray
(join (username) ['s to do list)

I haven't figured that part out yet.

Well, what if this happens?