~♛_??? some variation of catafinity
113 blocks for the timer credits to @Martinez135 for original project logic conditions for the first input top 1 ADD THIS NOW SCRATCH: Currently, our custom reporter blocks (the oval-shaped "My Blocks" that return true or false) immediately run all of their internal logic the moment we use them. My suggestion is to add an option that allows a custom Boolean block to serve purely as a container or placeholder for complex logical statements (e.g., <A and B and C>) without evaluating them immediately. This would be incredibly useful because it allows for powerful abstraction and organization; we could build "helper" logic once and reuse it across multiple sprites or scripts without having to copy-paste the entire string of condition blocks everywhere. It would enable highly reusable logic structures, helping us structure projects modularly, making large codebases significantly easier to read, debug, and maintain for sophisticated projects basic structure logic: item 0: <c> item 1: <not <item 0 > item 0>> ∧ <item 0 > item 0> ∧ <not <item 0 < item 0>> ∧ <item 0 < item 0> ∧ <not <item 0 = item 0>> ∧ <item 0 = item 0> | and | <not <not <item 0 > item 0>> ∧ <item 0 > item 0> ∧ <not <item 0 < item 0>> ∧ <item 0 < item 0> ∧ <not <item 0 = item 0>> ∧ <item 0 = item 0>> item 2: <not <item 1 > item 1>> ∧ <item 1 > item 1> ∧ <not <item 1 < item 1>> ∧ <item 1 < item 1> ∧ <not <item 1 = item 1>> ∧ <item 1 = item 1> | and | <not <not <item 1 > item 1>> ∧ <item 1 > item 1> ∧ <not <item 1 < item 1>> ∧ <item 1 < item 1> ∧ <not <item 1 = item 1>> ∧ <item 1 = item 1>> item 3: logic structure of item 2 but it’s item 2 instead of item 1 item 4: logic structure of item 3 but it’s item 3 instead of item 2 …
