Discuss Scratch

dhfbei8987
Scratcher
1000+ posts

Improving broadcasts

You have my full support. The workaround would most likely malfunction, and this helps target broadcasts at certain sprites.

My only concern is….. Could you do it to two sprites with one block?

No edit and king of the page!
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

dhfbei8987 wrote:

My only concern is….. Could you do it to two sprites with one block?
No, but you would be able to just do this for the same effect:
broadcast [message1 v] to [Sprite1 v] :: events
broadcast [message1 v] to [Sprite2 v] :: events
dhfbei8987
Scratcher
1000+ posts

Improving broadcasts

Mr_PenguinAlex wrote:

- big fat sni[-
No, but you would be able to just do this for the same effect:
broadcast [message1 v] to [Sprite1 v] :: events
broadcast [message1 v] to [Sprite2 v] :: events
Ah, got it
216138
Scratcher
100+ posts

Improving broadcasts

Semi-Support. I use variables for these type of things. for example a
when brodcast recived
if = DIS SPRITE CAN RECIVE IT? = 1
then do da thing
else
“ ”
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

bump
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

bump
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

bump
ninjaMAR
Scratcher
1000+ posts

Improving broadcasts

Support! I would use this to run large games needing a bridge to other sprites.
electrogame02
Scratcher
500+ posts

Improving broadcasts

Who cares about broadcasting for only specific sprites? You can easily ignore it, what we really need is a broadcast reporting Data values or is useless aside from changing scenes.

broadcast [ a message with data v] (Data) ::events

when I receive [A message with data v] (Data) ::events hat
play sound (Data)
216138
Scratcher
100+ posts

Improving broadcasts

electrogame02 wrote:

Who cares about broadcasting for only specific sprites? You can easily ignore it, what we really need is a broadcast reporting Data values or is useless aside from changing scenes.

broadcast [ a message with data v] (Data) ::events

when I receive [A message with data v] (Data) ::events hat
play sound (Data)
Theres a post actually a lot similar just with a different name that here
Scratchperson1000000
Scratcher
500+ posts

Improving broadcasts

there's a workaround:
when gf clicked
set [broadcast to whatever sprite v] to (0)
...
set [broadcast to whatever sprite v] to (1)
if <(broadcast to whatever sprite) = (1)> then
...
which is similar to
send [ v] to [ v] :: events
but some new scratchers probably wouldn't know what variables are
support
dhfbei8987
Scratcher
1000+ posts

Improving broadcasts

Scratchperson1000000 wrote:

there's a workaround:
when gf clicked
set [broadcast to whatever sprite v] to (0)
...
set [broadcast to whatever sprite v] to (1)
if <(broadcast to whatever sprite) = (1)> then
...
which is similar to
send [ v] to [ v] :: events
but some new scratchers probably wouldn't know what variables are
support
That workaround does not work at all.
BrowserExtension
Scratcher
100+ posts

Improving broadcasts

I don't see why we need this, you can have one sprite listening.
bluedragon8633
Scratcher
1000+ posts

Improving broadcasts

BrowserExtension wrote:

I don't see why we need this, you can have one sprite listening.
For projects with lots of broadcasts (I have one that has over 40 broadcasts) it's annoying to have to sort through all 40 when most are only being used by specific sprites.
dertermenter
Scratcher
1000+ posts

Improving broadcasts

This would definitely make the broadcast drop-down lest cluttered, but is it that useful? I personally don't really mind if 1 broadcast is for 1 sprite but is still in the editor for others.
electrogame02
Scratcher
500+ posts

Improving broadcasts

Are you a Masochist but want to have less broadcast in the drop-down menu? Make an array of events and an array for sign if checked.
Scratchperson1000000
Scratcher
500+ posts

Improving broadcasts

dhfbei8987 wrote:

Scratchperson1000000 wrote:

there's a workaround:
when gf clicked
set [broadcast to whatever sprite v] to (0)
...
set [broadcast to whatever sprite v] to (1)
if <(broadcast to whatever sprite) = (1)> then
...
which is similar to
send [ v] to [ v] :: events
but some new scratchers probably wouldn't know what variables are
support
That workaround does not work at all.
sorry, I mean this could work, script for first sprite:
set [broadcast to sprite v] to (1)
script for second sprite:
if <(broadcast to sprite) = (1)> then
...
wait (0.001) secs
set [broadcast to sprite v] to (0)
then if you want to broadcast to that sprite multiple times just make multiple variables

Last edited by Scratchperson1000000 (March 21, 2021 17:03:38)

foursquaremaster000
Scratcher
100+ posts

Improving broadcasts

support. This would be very useful and make it so you don't have to make a ton of broadcasts

Last edited by foursquaremaster000 (March 21, 2021 18:15:13)

dhfbei8987
Scratcher
1000+ posts

Improving broadcasts

foursquaremaster000 wrote:

Mr_PenguinAlex wrote:

-snip-
It could be useful, even if there's a workaround. There's no downside to adding this.

Options for 2nd dropdown:
all - sends broadcast to all sprites
name of a sprite - sends a broadcast to that specific sprite
myself - sends a broadcast only to the sprite that sent the broadcast
stage - sends a broadcast to the stage
support. This would be very useful and make it so you don't have to make a ton of broadcasts
Don't quote the op, or at least snip it.
foursquaremaster000
Scratcher
100+ posts

Improving broadcasts

dhfbei8987 wrote:

support. Don't quote the op, or at least snip it.
o sorry, removed the quote

Last edited by foursquaremaster000 (March 21, 2021 18:15:37)

Powered by DjangoBB