I have now a preview of Scratch 3.1.

Homepage:


New blocks:

point towards x: (0) y: (0)::motion//Points toward a specified point

previous costume::looks//Switches to the previous costume

previous backdrop::looks//Switches to the previous backdrop

change [blur v] effect by (10)//Added a new effect: blur

([color v] effect::looks)//The graphic effect of a sprite

(width::looks)//The width of a sprite

(height::looks)//The height of a sprite

<shown?::looks>//Is true if the sprite is shown

pause sound (pop v)::sound//Pauses a sound

resume sound (pop v)::sound//Resumes a sound

stop sound (pop v)::sound//Stops a single sound

change [speed v] effect by (10)::sound//Added a new effect: speed

([pitch v] effect::sound)//The sound effect of a sound

when <>::events hat//When the statement is true, the script activates

when [Sprite1 v] clicked::events hat//When a sprite is clicked, the script activates

<[message1 v] received?::events>//True if a message is received

while <> {

}::control loop//Repeats the script until the statement is false

for each [i v] in (10) {

}::control loop//The same as the repeat (number) block, but with a variable that increments by 1 at each iteration

delete all clones::control cap//Deletes all clones of a sprite

(# of clones::control)//The number of clones

(distance to x: (0) y: (0)::sensing)//The distance to a position

(current [millisecond v])//The current millisecond

(last key pressed::sensing)//The last key that you pressed

(() ^ ()::operators)//A number raised to a power of a number

(pi::operators)//3.14159265359

([2 ^ v] of ()::operators)//2 raised to the power of a number

(letter # of [a] in [apple]::operators)//The letter number of something in the word

move [my variable v] to x: (0) y: (0)::variables//Moves a variable to a specified position

set readout style of [my variable v] to [normal v]::variables//Sets the readout style of a variable

set [minimum v] of [my variable v] to (0)::variables//Changes the slider range to a number

move [my list v] to x: (0) y: (0)::list//Moves a list to a specified position

set width of [my list v] to (10)::list//Sets the width of a list

set height of [my list v] to (10)::list//Sets the height of a list

delete items (1) to (5) of [my list v]::list//Deletes a set of elements on a list

write [Hello!] using font [Sans Serif v] at x: (0) y: (0) size (10)::pen//Writes text to the stage

I sincerely doubt that also this isn't a suggestion.
If this is somehow real I will eat my own hat that I don't have.

Don’t make lists of unrelated suggestions. Also, previous backdrop already exists in the dropdowns of the switch backdrop blocks.

Yes, but I also added it as a new block.

pyromoose wrote:

Yes, but I also added it as a new block.

What do you mean? (Also use the quote button)

Rejected Suggestions wrote:

1.1 “Broadcast received” boolean block
This would allow a project to detect when a broadcast is sent. But, there is a lot of ambiguity on how this would work. Would it return true if the broadcast was fired since the project was created, since the green flag was clicked, or since something else was broadcasted? The workaround is simple: use variables that change when a broadcast is received, then use the “equals” block.

However, the blocks “repeat until broadcast received” and “wait until broadcast received” are NOT rejected; you can discuss them on this topic.

<[message v] recieved?::events>

I believe it should be added.

pyromoose wrote:

Rejected Suggestions wrote:

1.1 “Broadcast received” boolean block
This would allow a project to detect when a broadcast is sent. But, there is a lot of ambiguity on how this would work. Would it return true if the broadcast was fired since the project was created, since the green flag was clicked, or since something else was broadcasted? The workaround is simple: use variables that change when a broadcast is received, then use the “equals” block.

However, the blocks “repeat until broadcast received” and “wait until broadcast received” are NOT rejected; you can discuss them on this topic.

<[message v] recieved?::events>

I believe it should be added.

Well, it's rejected so it won't be and if you are going to make suggestions make them individual posts.

First block:
https://scratch.mit.edu/discuss/topic/8101/?page=1
Previous costume:
https://scratch.mit.edu/discuss/topic/2793/?page=1
Blur effect:
https://scratch.mit.edu/discuss/topic/45089/?page=1
Shown can be done like this:

define show
set [shown v] to [yes]
show
define hide
set [shown v] to [no]
hide

For when [sprite v] clicked, you can use broadcasts.
For effects you can keep track of the changes like this:

define set pitch effect to (number)
set [pitch effect v] to (number)
set [pitch v] effect to (number) ::sound
define change pitch effect by (num)
set pitch effect to ((num) + (pitch effect))

I found this for while loop:
https://scratch.mit.edu/discuss/topic/279609
However the while loop is in Scratch, just hidden. It does the same thing as:

repeat until <not <>>

end

The when block can be replicated like this:

when [loudness v] > ((loudness) - <condition ::grey>)
set [note v] to [booleans are 0 (for false) or 1 (for true) in operations like this]

It is being suggested here:
https://scratch.mit.edu/discuss/topic/2471

Please don't quote this image just to put your reaction to it, it's unconstructive.
-
Jokes aside, we are already past scratch 3.1, and these blocks haven't been implemented yet.
Please don't make a list of suggestions, and please don't claim something is going to be added if it isn't, that's being dishonest and against the guidelines.

If you have a suggestion, make a separate topic for each one, and be sure to check whether it has been already suggested or it is rejected.

Look at the homepage again.

What do you see different?

pyromoose wrote:

Look at the homepage again.

What do you see different?

Please don't quote this image just to put your reaction to it, it's unconstructive.

This doesn't appear to be a suggestion.