SuperJedi224 wrote:

1. Bring back the user id block Neutral support. There's an easy workaround which will become even easier when cloud lists and strings come out.
2. Cloud broadcasts- as a separate block, not as a replacement for normal broadcasts. Don't know. Interesting idea.
3. View count reporter block No support: Why? Couldn't you just use a cloud variable?
4. Active players reporter block- relatively low priority, a more complicated solution is already possible with cloud variables Neutral support. Not sure of use.
5. A join block with extendable inputs, as per BYOB extendable inputs - again. relatively low priority, you can just use multiple normal join blocks, but would still be helpful Neutral support. Really easy to workaround.
6. Custom reporter and boolean blocks SUPPORT! Having to use a variable is annoying.
7. Temporary variables (declared at the start of a script or block definition, exclusive to that script or block, deleted at the end of the block or script) Support. BYOB had this.
8. (Idea by jvclincoln) “<recieving (messsage)>” boolean block. (Appended: OR a “message” reporter like in Snap 4.0) Ambiguous. I never really figured out a purpose for this one, neither how it would really work.
9. Flash cookie variables- look like cloud vars, but with a cookie instead of a cloud. Stores the variable locally as a flash cookie. No support. Seems like people's computers could be spammed. Also, why?
10. Increase the tag limit Support. Except for the spam problem, 1.4 allowed much more tags.
11. Possible special cloud variables in addition to normal cloud- apply to all projects by user Don't know.
12. “print (text) at x (x) y (y)” pen block Some support. Easy workaround, and it's barely customizable either way. Don't see why you couldn't use a variable.
13. You should be able to log into the bugtracker with your regular scratch account. I see no reason to require a seperate account for that. Support. Don't see why not.
14. **Images from http://internetometer.com/ should be allowed. Myself and, most likely, the other scratchers with internetometers, would like to be able to use them properly.** Wouldn't know.
15. You should be allowed to put reporter blocks in more dropdowns than you currently can. It's more helpful than the scratch team seems to think. Support.
16. BRING BACK “EXPORT SCRIPTS TO IMAGE”! Some support. But the images would have to be an even higher filesize than before.
17. Maybe bring back single stepping? Some support. I never used it anyways; I use wait blocks.
18. Allow images from Creative Commons. Support. Don't see why not.
19. <[string] contains [other string]> boolean. Support. My friend made a workaround, and it's a lot of code.
20. Say [] until <> block. No support, easy workaround, see no use
21. Bring back the Scratch API. Support.
22. (Index of [string] in [list v]) and (Index of [string] in [other string]) reporter blocks Support. The only problem I see is multiple findings.
23. There should be a board for text-based games here Some support. Good idea, but I never play TBG's anymore anywhere
24. greyshift graphic effect Not exactly sure what that is.
25. Negative color mode Interesting idea, but not sure of use.
26. Colored variables! I guess. Would be useful for stage monitors.
27. Can Scratch please have a built in text-to-speech engine?Support. I hate having to go offsite…

mathfreak231 wrote:

SuperJedi224 wrote:

22. (Index of [string] in [list v]) and (Index of [string] in [other string]) reporter blocks Support. The only problem I see is multiple findings.

Put my opinions in color above. Green is full support, blue is partial/neutral support, and red is no support. Yellow=IDK.

meowflash wrote:

Can you add cloud lists?