It is hard to organize certain sprites or costumes, so I think this is the solution. For grouping sprites, it would allow you to describe what the different groups do and if you forget what sprites do this will help explain the general. idea for those group of sprites. For costumes, it would just make it easier to find certain sections. YOu could even have blocks for the costumes one:

if within [ v] group

pippy2011eight wrote:

I don't know, I can't use them.

No, since that doesn't involve blocks.

medians wrote:

pippy2011eight wrote:

I don't know, I can't use them.

No, since that doesn't involve blocks.

I was talking about the “group” itself and not about the block.

pippy2011eight wrote:

It is hard to organize certain sprites or costumes, so I think this is the solution. For grouping sprites, it would allow you to describe what the different groups do and if you forget what sprites do this will help explain the general. idea for those group of sprites. For costumes, it would just make it easier to find certain sections. YOu could even have blocks for the costumes one:

if within [ v] group

I don't see why we would need the block though, do you have a reason for it to be added?

it would be a loop block

pippy2011eight wrote:

it would be a loop block

Loop blocks already exist?:

forever

end
repeat until <>

end

no, this would say that if it- wait no, it would be this block:

<within [ v] group?>

pippy2011eight wrote:

It is hard to organize certain sprites or costumes, so I think this is the solution. For grouping sprites, it would allow you to describe what the different groups do and if you forget what sprites do this will help explain the general. idea for those group of sprites. For costumes, it would just make it easier to find certain sections. YOu could even have blocks for the costumes one:

if within [ v] group

You can actually replicate this in scratch itself by neatly organizing the names of your costumes. But this is a great idea otherwise.

pippy2011eight wrote:

no, this would say that if it- wait no, it would be this block:

<within [ v] group?>

Like I said, why would we need to know if a sprite would be in a group?

Also, I think the boolean should look like this:

within [Yomama v] group? :: sensing boolean

yup!

Dragonmyflesh wrote:

pippy2011eight wrote:

no, this would say that if it- wait no, it would be this block:

<within [ v] group?>

Like I said, why would we need to know if a sprite would be in a group?

Also, I think the boolean should look like this:

within [Yomama v] group? :: sensing boolean

Let's say I am making a hurricane track and I want to represent when a storm is a major hurricane or a regular hurricane. using

<within [ v] group?> :: sensing

I could do this script

if <within [major hurricane v] group?>then
switch costume to [Major Hurricane Ivan v]
end

yyes

ThisIsTemp1 wrote:

Let's say I am making a hurricane track and I want to represent when a storm is a major hurricane or a regular hurricane. using

You could also use a variable.

(how?)

pippy2011eight wrote:

(how?)

If it's in a major hurricane, set the hurricane variable to 1.

What????

pippy2011eight wrote:

What????

example:

set [hurricane variable v] to [major hurricane]