Scratch

ok...

technoguyx wrote:

<visibility?>
([ghost v])

Would be nice to have, though you can work around it by having a variable and constantly setting an effect, or visibility to it.

Previous costume

Easy workaround:

switch to costume ((costume #) - [1])

Set to group [group v]
<touching group [group v]>

Though you can work around it, it's very complicated to do, and while not essential, would be nice to have.

Stop loop

I'd love to have this - I'm used to having a "break" command in text programming languages such as Java. c: I've worked around it with "stop script" (it was inside a broadcast) before.

Stop [sprite v]
Clear [sprite v] pen

Would be useful.

Go to www.[]

Security issues; what if I link to an inappropriate, phishing, or virus-infested website?
___________

The rest of the blocks are all workaround-able. And you'll be able to make custom blocks in 2.0 - I'm sure many people will offer to make blocks for purposes such as these. 

Stuff like previous costume could be useful to new scratchers who have no experience and makes it easier. Oh, and how can you work around the group things?

Blazingwave wrote:

How about, 

go to scratch.mit.edu[]

That way we can link each others projects to each other as well as forum pages etc.
Also we would have to make it so there is a limit to how many times you can repeat/use the block to avoid spam of lots of pages opening

Yeah!

go to www is bad. but I like the group idea

numberonegamers wrote:

Oh, and how can you work around the group things?

if <<<touching [Sprite1 v]> or <touching [Sprite2 v]>> or <touching [Sprite3 v]>>
say [do stuff]
end

Ugly workaround but it works. If you'd like to, say, move a "group" of sprites, you can do it with broadcasts, or variables perhaps.

With cloning, the touching block would check if it is touching ANY clone of the sprite, or it's original.

numberonegamers wrote:

Ok, but when cloning comes out? They won't sense different sprites if they hadn't existed there before.

One possible way would be to add clone's names to a list and check whether every single of them is touching.

set [i v] to (1)
repeat until <(i) > (length of [sprites v])>
    if <touching (item (i) of [sprites v])?> //we touched one sprite of the "group"
        broadcast [do stuff v] //we are "touching group"; do something.
        set [i v] to ((length of [sprites v]) + [1]) //to break off the loop
    end
    change [i v] by [1] //else, check next sprite.
end

This can be placed inside a loop, maybe even made a custom block with Scratch 2.0.

I dunno how cloning works in 2.0, but if it is true that all clones of a sprite count as one (which I reckon would cause some problems    ), then this won't be necessary.

Most are workaroundable.

like real programming

print ()

numberonegamers wrote:

Here is my idea of a ton of blocks for scratch 3.0 ( i said 3 on purpose! ) I hope a scratch member sees this!

Spin to point in direction [] in [] seconds

<I receive [broadcast some script sent v]>

<visibility?>

([ghost v])

Point away from [sprite v]

Previous costume

<moving?>

Stop sound [sound v]

Next sound

Previous sound

(Sound)

<playing sound?>

Set to group [group v]

Set timer to [ ]

<touching group [group v]>

Change timer by [] seconds

<[sprite v] is touching [sprite v]>

Broadcast [broadcast v] to [sprite v]

Broadcast [broadcast v] to [sprite v] and wait

Repeat for [] seconds
End

Stop loop

Stop [sprite v]

Clear [sprite v] pen

(Color)

<drawing?>

(% of ink covering screen)

<[variable v] showing?>

Make variable [variable v] go to x [] y[]

Go to scratch.mit.edu/[]

the stop sound [] is usable, but obsolete.