@sus_meeeooow gave me this idea, which I actually liked! Honestly, that's a good suggestion. Yes, I did bring back the Scratch 2.0 list blocks in a different way though, by putting broadcast dropdowns on the text and integer inputs. Sorry if you don't like it, but you might rethink that decision when seeing that they still work perfectly! Also, the custom blocks are there because they're meant to represent blocks that no longer exist anymore. Just a heads up, these are the following blocks that work: • set costume to (previous costume ▾) • set costume to (next costume ▾) • set costume to (this same costume ▾) • set backdrop to (this same backdrop ▾) • set backdrop to (this same backdrop ▾) and wait • when this sprite touches (mouse-pointer ▾) • while <> { • all at once { • (counter) • increment counter • clear counter • <key (¬) pressed?> • <loud?> • for each [my variable ▾] in (10) { • delete (all ▾) of [my list ▾] • insert (thing) at (last ▾) of [my list ▾] • replace item (random ▾) of [my list ▾] with (thing) • (item (last ▾) of [my list ▾]) • set pen shade to (10) • change pen shade by (15) • set pen color to (10) • change pen color by (15) • play note (60) for (1) seconds • when (z x c v b n m space) pressed in order • when (enter) key pressed • play drum (1) for (0.25) beats • set instrument to (1) Heheh... this a long project description, isn't it? ...at least you got to the end, I suppose... Make sure to give extra credit when using the contents of my projects! C2A (credit to all)
