thats really cool lol
oh, sorry
Yeah, @sathvikrias had already explained it to me. I knew that the feature was new, so I just wasn't sure whethere it actually did anything yet - hence my suggestion.
EDIT: Also, I like to think of it like a forever loop as well, because my brain has a hard time superimposing the "when <>" block; this is partially because I rarely use said block.
I am currently trying to make a "When stop square clicked" and a "When play button clicked" block (I am already done the "When stop square clicked" block, but still ironing out difficulties with the "When play button clicked" block).

I am already done the "When stop square clicked" block
wait, how?
this does not seem to work for me. though I did suspect you were doing something with the timer, but I could not figure out what
hi jens
Haha, that's brilliantly funny!
lol thanks
yes, it appears to run the script when the flag is clicked and not when the project is stopped
Yes, the very first time you open the project, it will run when the flag is clicked. Also, remember that it is "when stop square clicked", which means you have to click the stop sign a second time.
I would suggest using (current [time in milliseconds V])
because yhe timer can be reset from any script.
That is true, but that would only result in the timer being lower than the variable, which is expected. The forever loop will then set the variable to be close to the timer again. However, that block may be useful in the "when play button clicked" block.
Also, I don't have any particular purpose for these blocks, I just am trying my hand a them for fun. It has certainly tested my knowledge of threading ;~).

you could probably singlehandedly explain everything I'm learning and i'd understand way better than I do now
Well, the math and the computer science. I don't quite know everything. But thanks for the compliment!
If there's something in particular you're having trouble with, start a new topic and we can talk about it.

Okay, I'm confused. If the stop sign is a square instead of an octagon, custom WHEN scripts don't run. I get that the point of the LAUNCH is so that there will be a running script all the time, but if that works, then the stop sign won't ever be a square, no? What am I missing?
What you are missing is that this runs when the stop square switches to a stop sign, because the stop square was clicked. When you press the stop sign, the forever script stops running. If you press the stop square after that, then my script notices that the script isn't running and reports true. However, I just realized that I made it overcomplicated - I don't need the timer at all. I was trying to create the "when stop sign clicked" block you can create in Scratch, but in the process I ended up creating another way to do it:

What you are missing is that this runs when the stop square switches to a stop sign, because the stop square was clicked.
Oh. So if the user accidentally double-clicks the stop sign, that defeats the disabling of custom WHEN scripts? Sounds like a bug to me. You should have to click the green flag, or otherwise fire a primitive hat block, or click on a script, to undo the squareness... I guess the idea is that any user action at all is enough to let WHEN scripts run, including any mouse click?

the "when stop sign clicked" block you can create in Scratch
Wait, what? You can create hat blocks in Scratch?
no, but you can use blocks like when [timer v] > (...::)
to do similar things

If there's something in particular you're having trouble with, start a new topic and we can talk about it.
Honestly if I do, I'd probably just private message you. Not really worth everyone's time for my troubles, lol
but what if, say, someone like me wanted to help too?
¯\_(ツ)_/¯
create a group chat with you, bh, and I? (assuming you have the ability to use the private message function on the forums)