More Events: Add More Events extension

[LilyMakesThings]

I've wanted to create this extension for a long while, this is about as many blocks as I can think of.

I needed this extension for specifically the "broadcast to target" block. (In hindsight, it may need some work).

[LilyMakesThings]

This block now exists thanks to @CST1229

[LilyMakesThings]

Thumbnail:

[BlueDome77]

"when extension added" will pair nicely with ShovelUtils "load extension" block!

[LilyMakesThings]

Likewise with what TheShovel commented on CustomCSS, if there's any immediate problems with this extension (or other ones), just let me know and I can resolve them

[BlueDome77]

Are you going to add this block?

It only makes sense cause the original "broadcast ()" block has a STRING input

[LilyMakesThings]

Are you going to add this block?

It only makes sense cause the original "broadcast ()" block has a STRING input

That's impossible to add.

[BlueDome77]

Are you going to add this block?

It only makes sense cause the original "broadcast ()" block has a STRING input

That's impossible to add.

why?

[LilyMakesThings]

Are you going to add this block?

It only makes sense cause the original "broadcast ()" block has a STRING input

That's impossible to add.

why?

Sigh. I hate explaining this to people (that's not your fault).

Broadcasts themselves work through a Block Utility called util.startHats (alternatively you can do Scratch.vm.runtime.startHats, but they work the same regardless). Broadcasts have an input field that it'll check on the hat it starts to see if they match. In this case, it'll be "message 1". If they're the same, the hat will start.

However, the field check on util.startHats only works for 1 type of field (in Scratch terms, "the square one"). It does not work for fields that accept any kind of input.

There is no way around this.

[LilyMakesThings]

I forgot to say but I made the changes to this block I eluded to:

• It now supports sending messages to the stage target
• The menu isn't broken
• It sends to clones as well
  

[LilyMakesThings]

A few questions:

• Are merge conflicts something I'll need to resolve?
• Should these blocks be removed?
  

[LilyMakesThings]

Added data sending through broadcast messages

[LilyMakesThings]

Using XML blocktype to get the broadcast menu into the blocks. Doing this until there's a way to do it without XML

[GarboMuffin]

There is a VM change that is merged but not deployed yet that will make whenValueChanged work properly

[LilyMakesThings]

should "forever" only run while the project is active?

[LilyMakesThings]

All of these have now been implemented. I'm not adding anymore than this.

[LilyMakesThings]

...except that.

[GarboMuffin]

is this done?

[LilyMakesThings]

yep

[LilyMakesThings]

OH DAMN