Snap! 9.0 please

Feature Requests Snap! Feature Requests
, , ,
1

I have Ideas for the Snap! 9.0 update.
You can post an idea too!

1: Custom hats and caps!
[scratchblocks]
when (custom :: control) = <added? :: control> :: events hat
say [Yay!]
loop script :: events cap
[/scratchblocks]

2: MultiUser Editor!
[scratchblocks]
open MultiUser :: control
comment to @[User] "[Message]" :: control
(reply from @[User] :: control)
<talking to @[User]? :: control>
(user you are talking to :: control)
(username)
delete message [Message] :: control
close MultiUser :: control
<MultiUser on? :: control>
when MultiUser is on :: control hat
[/scratchblocks]

3:Wifi detectors
[scratchblocks]
<online? :: sensing>
[/scratchblocks]

What are your Ideas?

3

I reported u to the moderators.

4

also you will get ip banned if you use this block

5

We already have the generic WHEN block!

6

Yeah.He is reffering to custom hat blocks,which have been rejected multiple times due to the generic when block.

7

However, we dont have a
[scratchblocks]
when project stopped :: events hat
[/scratchblocks]
block.

9

Lets make a deal.

You stop being mean, I give you the Real 9.0 update.

10

CyberBullying is a crime.

11

I dont get banned using scratch's username block.

12

Previously, the most viable way to get the current user’s username was by accessing the Snap! Cloud API. However, this method has been banned, and accessing/attempting to access the Snap! Cloud in a project will result in the user doing so being banned.

13

Please be nicer. This user is new to the forum, and we don't want to scare them away.

14

But the picture was of a generic when! ¯\(ツ)/¯

15

He's going to start being nicer.

FYI, there's nothing secret about the dev version. It's our more-or-less official alpha test channel. But some of its features will be experimental, and we're not committing ourselves to keeping anything in the eventual release version.

16

Huh. That's interesting. Long, long ago they had a username block, and then long ago they removed it, as a privacy violation, and replaced it with a block that would report a unique identifier per user per project so that game programs could remember their users without having to know anything else about their users' interactions with Scratch. But now the username block seems to be back. Does anyone know more than I do about why they changed their minds?

17

It was probably because mainly of cloud variables, otherwise there would be literally no possible way to distinguish different users

I still think user id is better as that’s a number and that’s what cloud variables support, but both have strengths and weeknesses

18

He wants custom hats and caps

19

I'm pretty sure they added the user id block, then removed it, all while keeping the username block (which has been in scratch since 2.0, never getting removed).

20

Let me edit my message for a sec.

21

There.

22

I fixed it.