XML editing is crazy
Operators blocks are crazy.
(join (list ({when gf clicked} @>) @<>) (list ({when gf clicked} @>) @<>) @<:>)
(join (list ({delete this clone} @>) @<>) (list ({create a clone of [myself V]} @>) @<>) @<:>)
(join ((<> @>) @>) ({when gf clicked} @>) @<:>)
Hats in rings was impressive back when that wasn’t something you could natively do
I think their point was that their hat was in a predicate ring.
I didn’t do it natively. I’m actually not aware of ring block joining
i forgot this was posted 2 months ago mb all
what did you use for it (I know you used xml, but more specifically)?
I downloaded the project, opened it in VS code, edited it, saved it, then loaded it back into Snap
Ah. just so you know, there are xml encoding blocks already in snap (click file → extension blocks, then scroll to the bottom of variables and select the extension reporter).
i bet i could find something a lot weirder 
We don’t need rings where we’re goin
Also, removing the hat blocks does THIS
l o n g
i love the
move (10) steps :: cap
block
It’s not a cap block; the ring around the when flag clicked block just covers the bottom dent. Still cursed though
woooosh
offtopic for @d016
can i copy the userscript code to use with the split mod for crackle?
what? (I know what woosh means, but I can’t really see the joke)
The userscript is extremley outdated. It’s also broken if you don’t use the userscript in a manager like tampermonkey. Just copy the code from the Split repo!