Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

I want a new E block! Let me show you.

run {
...
} and {
...
} :: control

Basically, it will run two scripts at once.

run {
...
} and {
run {
...
} and {
run {
...
} and {
...
} :: control
} :: control
} :: control

Or three! Or four! Pretty much as many as you want.

Now, this would be really useful with forever loops.

when green flag clicked
run {
forever
wait (5) secs
show
wait (5) secs
hide
end
} and {
forever
next costume
end
} :: control

But Red!, you may be asking, why can't you just use two scripts like this?

when green flag clicked
forever 
wait (5) secs
show
wait (5) secs
hide
end

when green flag clicked
forever 
next costume
end

Well, okay, sure, you could do that, but what about when you CAN'T do two scripts?
Yup! I'm talking about custom blocks!

define Jump

There are many times you'd need two scripts in a custom block, but it only lets you do one script, because you can't put multiple define hats of the same custom block! This would fix that.

define Jump
run {
...
} and {
...
} :: control

This would also be useful for compacting scripts in general.

Yes, you could put code underneath this block, unlike the forever block. Code stacked underneath this block will run when all code is done running in the run, and run block(s). So, if you put a forever loop in one of the branches of this block, code underneath it will never run.

I hope you like my idea!

BEFORE SAYING THE WORKAROUND IS “EASY,” READ THESE POSTS:

xXRedTheCoderXx wrote:

Mr_PenguinAlex wrote:

if you make 2 different custom blocks,
and do this:

when green flag clicked
custom block 1 :: custom
custom block 2 :: custom

it would work like this script, right?

No…

Custom blocks run code underneath them when the custom block is done running.

And with forever loops, that would be never.

The only possible workaround is incredibly complicated and requires a list for every single argument of every single custom block.

xXRedTheCoderXx wrote:

This block's main use is to make custom blocks able to run multiple scripts.

And, as you may know, custom blocks are different from broadcasts because with custom blocks you can add boolean inputs and string inputs. You could only use those inputs when you define the custom block.

So, basically broadcasts can't carry over what you input in the custom block unless you use variables or something but like bruh.

xXRedTheCoderXx wrote:

DownsGameClub wrote:

xXRedTheCoderXx wrote:

So, basically broadcasts can't carry over what you input in the custom block unless you use variables or something but like bruh.

As a person who hasn't used custom blocks in a while, why would using variables be an issue?

Having to make a variable for every single argument in your custom block is beyond tedious and isn't ideal. Having so many variables could cause your variable list to clutter up.

Also, using variables means that you can only run a custom block when it isn't already running, otherwise your variables will change from the other custom block of the same type running, and you'd be left scratching your head wondering why your game doesn't work.

It's hard to put into words, at least for me, but trust me, using variables restricts you, which could lead to the breaking of your game, as well as clutters your variable list making your game as a whole just that bit more unorganized.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

Read the entire OP before posting.

There are ways around this, but yes support! It can be helpful! (´▽`ʃ♡ƪ)

_ReykjaviK_ wrote:

There are ways around this, but yes support! It can be helpful! (´▽`ʃ♡ƪ)

Thanks! But, how are there ways around this?

xXRedTheCoderXx wrote:

_ReykjaviK_ wrote:

There are ways around this, but yes support! It can be helpful! (´▽`ʃ♡ƪ)

Thanks! But, how are there ways around this?

Broadcast blocks are the only workarounds I can think of right now

I support.
There's not a workaround if you are using custom blocks.

But why would the same sprite need several different functions under the same custom block?

Support. This would be great for compressing scripts and especially walk cycles, where you want two procedures under one hat block.

This is support!

(-!*o_o*!-) // protecty, my signature kumquat protector. *power level: infinty *magic level: infinty
(?-i_i-?) // claculately, caculates weaknesses and finds out strengths to...
// evil qumquats

see my projects::looks
say [hello]

Vibrato wrote:

But why would the same sprite need several different functions under the same custom block?

It really depends on what you're coding. Personally, I've needed that many times.

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

_ReykjaviK_ wrote:

There are ways around this, but yes support! It can be helpful! (´▽`ʃ♡ƪ)

Thanks! But, how are there ways around this?

Broadcast blocks are the only workarounds I can think of right now

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

BosenChang wrote:

This is support!

kitten769 wrote:

Support. This would be great for compressing scripts and especially walk cycles, where you want two procedures under one hat block.

Mr_PenguinAlex wrote:

I support.
There's not a workaround if you are using custom blocks.

Thank you for the support!

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

You are right. It takes 0.1 seconds for a block to run from one to the other.

(-!*o_o*!-) // protecty, my signature kumquat protector. *power level: infinty *magic level: infinty
(?-i_i-?) // claculately, caculates weaknesses and finds out strengths to...
// evil qumquats

see my projects::looks
say [hello]

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

I don't think you understand this suggestion.

xXRedTheCoderXx wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

...

I understand that they won't exactly be synchronized but it's pretty close

I don't think you understand this suggestion.

Can you explain a little more then?

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

...

I understand that they won't exactly be synchronized but it's pretty close

I don't think you understand this suggestion.

Can you explain a little more then?

This block's main use is to make custom blocks able to run multiple scripts.

And, as you may know, custom blocks are different from broadcasts because with custom blocks you can add boolean inputs and string inputs. You could only use those inputs when you define the custom block.

So, basically broadcasts can't carry over what you input in the custom block unless you use variables or something but like bruh.

BosenChang wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

You are right. It takes 0.1 seconds for a block to run from one to the other.

uhh, It takes a lot less then 0.1 seconds for a block to run. it
they should be almost perfectly in sync.

No support because of easy workarounds

when green flag clicked
wait (1) secs
broadcast [Uninstallsupportx2 v]

when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::
when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::

JackK211424 wrote:

BosenChang wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

You are right. It takes 0.1 seconds for a block to run from one to the other.

uhh, It takes a lot less then 0.1 seconds for a block to run. it
they should be almost perfectly in sync.

No support because of easy workarounds

when green flag clicked
wait (1) secs
broadcast [Uninstallsupportx2 v]

when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::
when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::

I did not ask for the correct value.

(-!*o_o*!-) // protecty, my signature kumquat protector. *power level: infinty *magic level: infinty
(?-i_i-?) // claculately, caculates weaknesses and finds out strengths to...
// evil qumquats

see my projects::looks
say [hello]

BosenChang wrote:

-snip-

I did not ask for the correct value.

I did not give you the correct value

JackK211424 wrote:

No support because of easy workarounds

when green flag clicked
wait (1) secs
broadcast [Uninstallsupportx2 v]

when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::
when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::

You shouldn't not support something JUST because of a workaround.. especially when the “workaround” you posted isn't even a proper workaround.

Read the posts and all of the OP, please.

xXRedTheCoderXx wrote:

This block's main use is to make custom blocks able to run multiple scripts.

And, as you may know, custom blocks are different from broadcasts because with custom blocks you can add boolean inputs and string inputs. You could only use those inputs when you define the custom block.

So, basically broadcasts can't carry over what you input in the custom block unless you use variables or something but like bruh.

JackK211424 wrote:

BosenChang wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

define the thingy you are doing
if <<insert thing>> then
broadcast [tada v]
thingy1 that you were running
end

when I receive [tada v]
the thing you wanted to run at the same time

I understand that they won't exactly be synchronized but it's pretty close

You are right. It takes 0.1 seconds for a block to run from one to the other.

uhh, It takes a lot less then 0.1 seconds for a block to run. it
they should be almost perfectly in sync.

No support because of easy workarounds

when green flag clicked
wait (1) secs
broadcast [Uninstallsupportx2 v]

when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::
when I receive [Uninstallsupportx2 v]
uninstall support.exe :: #fc03ec ::

The workaround does not work with custom blocks.

(-!*o_o*!-) // protecty, my signature kumquat protector. *power level: infinty *magic level: infinty
(?-i_i-?) // claculately, caculates weaknesses and finds out strengths to...
// evil qumquats

see my projects::looks
say [hello]

xXRedTheCoderXx wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

KittyFireSt0rm wrote:

xXRedTheCoderXx wrote:

Nope! That doesn't work, you can't use the booleans, strings, etc. in a broadcast, only in a custom block.

...

I understand that they won't exactly be synchronized but it's pretty close

I don't think you understand this suggestion.

Can you explain a little more then?

This block's main use is to make custom blocks able to run multiple scripts.

And, as you may know, custom blocks are different from broadcasts because with custom blocks you can add boolean inputs and string inputs. You could only use those inputs when you define the custom block.

So, basically broadcasts can't carry over what you input in the custom block unless you use variables or something but like bruh.

ahhhh okay thanks!