Works fine. Nothing wrong about it. Super useful, hope this gets added to Snap!
What. In the actual.
(finish the phrase as you like)
But why? Do you enjoy making scripts to push poor Snap! to its limit? Come on, man.
But just give me a few days (so I can access a faster computer), and I’ll make the definition even bigger.
Don’t talk to me like that or ill torture it again.
That looks like a piece of paper lol
good luck trying to use that in an actual project.
ancient egyptian pyramid of L I S T
This one is like the previous, but made of LIST INPUT LIST: LIST INPUT LIST: … instead of LIST LIST LIST …
but <is <> true> is fundamentally equivalent to <not <is <> false>>
why not just use that its so much simpler
These blocks are joke blocks
how did you make list input list?
Went in dev mode and changed the block spec, then exported and reimported
Worrying about duplicate blocks. Check the definitions
ok clearly it wasn’t obvious that i was joking
Oh mb.
What if when aremia said “that”, they were referring to <not<is<f>false::operators>> and not <is<t>true::operators>? 
Isn’t Snap! made for both simple block code and also more complex programming?
I don’t see how it wouldn’t be able to handle that. (If you were joking or something, my apologies [also i don’t know much about coding, I’ll be honest])
I mean, it pushes my computer (school chromebook btw) to the limit more than it pushes Snap! to the limit. I was mostly a joke, because nowadays we usually do atrocious stuff to Snap! like that all the time.