DARKTHUNDER11 wrote:

WORKAROUND:
message split.
Broadcast mmessage.
Have 2 scripts recieve it at the same time.

DARKTHUNDER11 wrote:

WORKAROUND:
message split.
Broadcast mmessage.
Have 2 scripts recieve it at the same time.

EpicGhoul993 wrote:

cooldude-222 wrote:

Sorry, you have to wait 60 seconds between posts

[Offtopic]Oof rip[/Offtopic]

Anyway, there actually is a quite acceptable workaround, BUT if you use many block combinations there will be lots of duplicated codes.

broadcast [run 1 and 2 v]

when I receive [run 1 and 2 v]
block 1 ::custom

when I receive [run 1 and 2 v]
block 2 ::custom

And, I don't say I give this a No Support,

EpicGhoul993 wrote:

Support.

I only want to point out how the workaround given is not very affective compared to the suggestion block.

• Mountains of broadcast
  Let's say you are making a wayyyy complex game, and you are forced to have several script parts to run at once. Imagine you having to make 10 broadcasts exactly like the one I give above… you know.
  
• Screen refeshing
  As I recently read from a Scratch HWS topic,
  

  […]boardcasts force the screen to refresh, while cusrom blocks with the tick on “run without screen refresh” don't.

  that leads to some scary times where you do stuff really fast and don't want the player to, like, see the character runs everywhere on the screen, but the refresh ruins everything and you are left scratching your head on how to hide it from the player again.
  

Here's my opinions on the workaround. Please think before posting “ThErE's A wOrKaRoUnD1!!1!!111!”, and be constructive on the topic.

DARKTHUNDER11 wrote:

WORKAROUND:
message split.
Broadcast mmessage.
Have 2 scripts recieve it at the same time.

do {
 repeat (10)
  next costume
  wait (.05) secs
 end
}while doing {
 glide (1) secs to x: (0) y: (0)
} :: control loop
say [Hello]

Byron_Inc wrote:

When will it say “Hello” if I do the following script:

do {
 repeat (10)
  next costume
  wait (.05) secs
 end
}while doing {
 glide (1) secs to x: (0) y: (0)
} :: control loop
say [Hello]

?

Ihatr wrote:

cooldude-222 wrote:

leahcimto wrote:

Support, I have needed this so many times and it would be so helpful for custom blocks

please be constructive

How is this not constructive?

cooldude-222 wrote:

Byron_Inc wrote:

When will it say “Hello” if I do the following script:

do {
 repeat (10)
  next costume
  wait (.05) secs
 end
}while doing {
 glide (1) secs to x: (0) y: (0)
} :: control loop
say [Hello]

?

I believe it will run after both are done

when green flag clicked
1
define 1
...
define 2
...
when green flag clicked 
2

lovecodeabc wrote:

https://scratch.mit.edu/projects/424934761/

when green flag clicked
1
define 1
...
define 2
...
when green flag clicked 
2

Mr_PenguinAlex wrote:

what if you put a forever loop in it? does it ever do the scripts below?

cooldude-222 wrote:

I believe it will run after both are done

apple502j wrote:

Technically Impossible.
To have multiple scripts run at the same time, we need to use new threads. That's what broadcasts do - each broadcast receiver has its own thread. Custom blocks don't use threads - it runs in the context of parent thread. In the different thread, you cannot access thread variables (aka custom block arguments). Also, we need to wait until all thread finishes executing so we need to yield. Hey, I re-designed “broadcasts”, right?

Also, thread's top block needs to be a hat block, and needs to have set opcodes, not just arbitrary command block. This makes it impossible to use the argument as a thread.

do{
}while doing{
} ::control

start{
} ::control

cooldude-222 wrote:

what if instead of the

do{
}while doing{
} ::control

it is

start{
} ::control

it would start running the script inside and it would also continue to run the script below

xXRedTheCoderXx wrote:

cooldude-222 wrote:

what if instead of the

do{
}while doing{
} ::control

it is

start{
} ::control

it would start running the script inside and it would also continue to run the script below

Seems interesting - but is it possible?

launch ((move (10) steps::stack)::grey) ::control

cooldude-222 wrote:

xXRedTheCoderXx wrote:

Seems interesting - but is it possible?

they have a

launch ((move (10) steps::stack)::grey) ::control

block in snap so yes. i just feel like this would be easier to understand than that

cooldude-222 wrote:

they have a

launch ((move (10) steps::stack)::ring grey) ::control

block in snap so yes. i just feel like this would be easier to understand than that

xXRedTheCoderXx wrote:

cooldude-222 wrote:

xXRedTheCoderXx wrote:

Seems interesting - but is it possible?

they have a

launch ((move (10) steps::stack)::grey) ::control

block in snap so yes. i just feel like this would be easier to understand than that

Hmm… well it seems promising. What do other people think of this idea?

xXRedTheCoderXx wrote:

cooldude-222 wrote:

xXRedTheCoderXx wrote:

Seems interesting - but is it possible?

they have a

launch ((move (10) steps::stack)::grey) ::control

block in snap so yes. i just feel like this would be easier to understand than that

Hmm… well it seems promising. What do other people think of this idea?

cooldude-222 wrote:

^^^ They don't really seem to like it