These Looks blocks should be removed:

BY147258369

duckboycool wrote:
They would do;
switch costume to (([costume # v] of [Sprite1 v]) + (1))//current sprite
But I only agree with the blocks, not the reporters anyway.

Why create such a long workaround when you have such a simple solution?

duckboycool

It isn't really such a long workaround, but I think we should just remove the blocks.

jromagnoli

BY147258369 wrote:
duckboycool wrote:
They would do;
switch costume to (([costume # v] of [Sprite1 v]) + (1))//current sprite
But I only agree with the blocks, not the reporters anyway.
Why create such a long workaround when you have such a simple solution?

^^ This. And @TheLogFather made an excellent post about why we should keep the next costume but not have the previous costume block. It was about teaching kids algorithmic thinking. We gave them next costume, and now they try to solve how to make an effective previous costume block.
EDIT: here: https://scratch.mit.edu/discuss/topic/2793/?page=3#post-2461268

Last edited by jromagnoli (May 2, 2017 15:24:13)

venyanwarrior

duckboycool wrote:
It isn't really such a long workaround, but I think we should just remove the blocks.

No way. Removing the blocks will break MANY YAS VERY MANY projects. Even the good ones like Scratch: Story mode. #Notsponsored.

This will be VERY confusing and also will be a hassle for the ST because people will just suggest for the blocks to be added back in so their games will work. Otherwise, they will probably have to go and re-work the code around their projects, and some might even have to re-work from the ground up.

All-in-all, this is a VERY bad idea.

awsome_guy_360

No support as per everyone else.

I wouldn't mind for the

next costume

Block to be removed. But even so if that was the only one removed, you just took away an essential block for costume based animations, even since it does have a simple workaround it still is a extremely useful shortcut.

As for the other blocks, you'd again be breaking a lot of animations and games.

As per gems and jrom; if it ain't broke, don't fix it.

EDIT: Also, how can you do the workaround for the “next costume” block if you plan to take the

(costume #)

boolean?

Last edited by awsome_guy_360 (May 2, 2017 23:26:13)

miniepicness

I dont usually support removing blocks.
Scratch seems fine with these blocks it has, im fine with more, not less.

monstermash3

BY147258369 wrote:
Just realized there's a huge contradiction. If you plan to remove
next costume
and
(costume #)
How can you do the workaround of
switch costume to<(costume #) + (1)>

awsome_guy_360 wrote:
EDIT: Also, how can you do the workaround for the “next costume” block if you plan to take the
(costume #)
boolean?

monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

Last edited by monstermash3 (May 2, 2017 22:21:16)

monstermash3

venyanwarrior wrote:
duckboycool wrote:
It isn't really such a long workaround, but I think we should just remove the blocks.

No way. Removing the blocks will break MANY YAS VERY MANY projects. Even the good ones like Scratch: Story mode. #Notsponsored.

This will be VERY confusing and also will be a hassle for the ST because people will just suggest for the blocks to be added back in so their games will work. Otherwise, they will probably have to go and re-work the code around their projects, and some might even have to re-work from the ground up.

All-in-all, this is a VERY bad idea.

There might be a way to replace all uses of the blocks in projects with the workarounds.

awsome_guy_360

monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.

monstermash3

awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.

The dropdowns in the of block.

awsome_guy_360

monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?

switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]

Last edited by awsome_guy_360 (May 2, 2017 22:36:02)

monstermash3

awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?
switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]

No, the sensing block.

awsome_guy_360

monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?
switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]
No, the sensing block.

switch costume to ((([Costume v] of [Sprite1 v])) + (0))

?

monstermash3

awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?
switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]
No, the sensing block.
switch costume to ((([Costume v] of [Sprite1 v])) + (0))
?

Yeah, I mean this block.

VideoGamerCanInvent

No Support.

It's currently fine as it is.

awsome_guy_360

monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?
switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]
No, the sensing block.
switch costume to ((([Costume v] of [Sprite1 v])) + (0))
?
Yeah, I mean this block.

Comparing to the block that we already have and how much I've used it, that workaround seems way too complex for me. I mean, sure you can backpack it, but I don't want to go to my backpack, search for it, then finally find the block and wish that there was an official shortcut that was already there in the first place.

What I'm saying basically, is I don't really want things to be more complicated. In my view the “next costtune” block is a very essential block. It's used for animations and run cycles and more that I possibly didn't list.

monstermash3

awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
awsome_guy_360 wrote:
monstermash3 wrote:
monstermash3 wrote:
(I don't think that would make the above workaround for the next costume block much harder, since all you would have to do would be set the two dropdowns.)

I-I don't really know what dropdowns you're talking about.
The dropdowns in the of block.

Do you mean this?
switch costume to [costume 1]
switch costume to [costume 2]
switch costume to [costume 3]
[...]
No, the sensing block.
switch costume to ((([Costume v] of [Sprite1 v])) + (0))
?
Yeah, I mean this block.
Comparing to the block that we already have and how much I've used it, that workaround seems way too complex for me. I mean, sure you can backpack it, but I don't want to go to my backpack, search for it, then finally find the block and wish that there was an official shortcut that was already there in the first place.

You know what? I think you're right about the reporter. I'll get rid of

(costume #)

monstermash3

Bump.

Pezd

duckboycool wrote:
They would do;
switch costume to (([costume # v] of [Sprite1 v]) + (1))//current sprite
But I only agree with the blocks, not the reporters anyway.

You know this isn't a valid work-around, because it won't work with clones.

([costume # v] of [Sprite1 v])

Only reports the costume number of the original sprite.

duckboycool

Well since the (costume #) block has been removed from the list, you can do;

switch costume to ((costume #) + (1))

which will work with clones.

Discuss Scratch