I suppose I don't really know the logic behind the division of Control and Events into two sections and how it was decided where each should go, but Events all seem to be mainly things that the user can trigger, while a broadcast is triggered by the script and not a buttonpress/camera/greenflag click, so it seems like broadcasts should go under Control.

I disagree—broadcasts and the when I receive block go together, and are clearly triggers. The clone block is different, it's not really a trigger, more like an announcement/initialization.

Hardmath123 wrote:

I disagree—broadcasts and the when I receive block go together, and are clearly triggers. The clone block is different, it's not really a trigger, more like an announcement/initialization.

But the way I see it, the “Control” area is clearly things that the script, and by extension the programmer, is controlling. Like having things wait blank seconds, or stopping all. Broadcasting is another thing that the broadcast (and “when I recieve block”, which would obviously move to control with it) are all based on the script. Sure, the user CAN do things to trigger the broadcast, but they also may not do anything to trigger them.
Everything besides the broadcast and corresponding blocks in events are most likely to be triggered by the user. The most arguable is the backdrop switching check, but even then, to put that as a hat block would most likely be user triggered (as you could attach the script directly after changing the backdrop in the original script if the user didn't have to do it).

Events means conditions that start the script. Broadcasts are conditions that start the script, so I think they go there.

As above, events are conditions that start the script. Controls are for repeating and waiting.

no, this isn't a necropost.

[0.0](ᵔ ᵕ ᵔ::stack)('_'::stack variables)(o,o::stack control)(d_b::stack operators)(²-²::stack motion)(1_1::stack looks)(°-°::stack sound)::stack #000000//these are my kumquat protectors

if <(username) = [add signature] > then
set [big brain v]to [True] 
end

<<true(::grey) ::#00FF00>::operators>
<<(::grey) false::#ff0000>::operators>

5000 posts (::control) (::control) (::#000000) (::#000000) (::#000000) ::#00008B

move (1) step::motion

() () ::custom hat

hahaha superhero block go brrrr::#FFFFFF cap

No support, events are for starting scripts as said above. Control is for controlling the scripts.

([foo v] ::variables)
([list v] ::list)
set [ v].y to [] ::variables
([foo v] [ v] pos :: variables)
<[] is exactly [] :: operators>
<mouse moving? ::sensing>
point towards x: () y: () ::motion

glide () secs to [sprite v] ::motion

we reach 410 + 10 posts :: sound

lol ::operators