Support for the reasons stated above.

Sigton

KKGamer1610 wrote:

georgeskey wrote:

KKGamer1610 wrote:

:D

Note: You shouldn't have added that, people often browse only no reply topics.
Anyway, semi-support. There is a way around it, even if it isn't terribly convenient: every time you change a effect, also change a variable.

What if you do this-

change [color v] effect by (pick random (1) to (10))

What do you do?

Change [color effect v] by (pick random (1) to (10))

Set a variable to a random value and use the variable value in both of the blocks.

Still support, this is terribly inconvenient.

Ninkancho wrote:

This has been suggested time and time again, so… support, actually. It boggles the mind that so many blocks have reporters like this, but not the graphic effects ones. In a language like Scratchblocks, we shouldn't have to create unneeded variables for values of existing block functions like this arbitrarily excluded quintuple-reportationalizationality. Get my gist?

Actually no… Is “reportationalizationality” even a word?

Anyway, support for

([color v] effect::looks)

U^ｪ^U::motion//This is Blocky. He lives in my signature. He is a trained attack block. He protects my siggy from kumquats.

Support! I don't understand why we don't already have one.

So I'm working on this game. And the way you beat a level is by making it to a red stop sign. Now, in the second level, I have enemies crossing the screen. The way I make them different colors is by running this block:

change [color v] effect by (pick random (5) to (50))

Ok?

But here is the issue. The enemy…can become the color of the stop sign.

A fix for this would involve a new block, that could be handy for many other things too.

set [effect here v] effect to (40)

Not that ↑↑↑ block. But that block shows that the effect blocks are used to change invisible variables, right? They have a “change __ by” and a “set __ to”, right? So that would mean that, like a variable, they should have one of these babies to go with it.

(color)

Or maybe,

(fisheye)

And

(ghost)

With these, you could insert the numerical value of the effects into codes like this one:

when green flag clicked
forever
    
if <(color) = [10 ]> then
    
set [color v] effect to (pick random (1) to (100))
end

end

With that code, my project would be fixed! Assuming red was 10, I don't think it is. But it would allow a code to run when an effect is a certain number, because it IS a variable after all. So if the color was red, or 10, then it would run the new code and the number would change. They just need a Boolean for it!



So, what do you guys think? Necessary? Or is there an easy workaround. Tell me down THERE ↓↓↓ in those lovely New Reply boxes! Thanks!

This would definetly be a good feature!

You mean like a

[color v] effect :: looks reporter

block?

Support.

alexphan wrote:

You mean like a

[color v] effect :: looks reporter

block?

Support.

Yeah. I like the drop down better than mine, I think

ToadworksStaff wrote:

alexphan wrote:

You mean like a

[color v] effect :: looks reporter

block?

Support.

Yeah. I like the drop down better than mine, I think

So this isn't a boolean, it is a reporter? Support then!

Support for

alexphan wrote:

[color v] effect :: looks reporter

but for now you'll have to use variables that change their values along with the graphic effect blocks.

Support for this:

[color v] effect :: looks reporter

It seems like a very useful block!

-bigpuppy

Sheep_maker wrote:

Support for

alexphan wrote:

[color v] effect :: looks reporter

but for now you'll have to use variables that change their values along with the graphic effect blocks.

Thanks for the workaround!

I think that these blocks…

([color v] effect::looks)
(size)

..should be combined.

If that happens, then I'll support.

scrooge200 wrote:

I think that these blocks…

([color v] effect::looks)
(size)

..should be combined.

If that happens, then I'll support.

What would the new block be?

Sheep_maker wrote:

scrooge200 wrote:

I think that these blocks…

([color v] effect::looks)
(size)

..should be combined.

If that happens, then I'll support.

What would the new block be?

The effect reporter

ToadworksStaff wrote:

Sheep_maker wrote:

scrooge200 wrote:

I think that these blocks…

([color v] effect::looks)
(size)

..should be combined.

If that happens, then I'll support.

What would the new block be?

The effect reporter

Like this?

([size v] effect::looks)

No support, easy workaround. Sorry!

when green flag clicked
set [looks.color v] to (10)
set [color v] effect to (10)
if <(looks.color)=(10)>
say[The color is red! Or orange, or whatever.]

alexphan wrote:

You mean like a

[color v] effect :: looks reporter

block?

Support.

Support for this kind of block. Could benefit many with color-specific projects.

Sheep_maker wrote:

ToadworksStaff wrote:

Sheep_maker wrote:

scrooge200 wrote:

I think that these blocks…

([color v] effect::looks)
(size)

..should be combined.

If that happens, then I'll support.

What would the new block be?

The effect reporter

Like this?

([size v] effect::looks)

Yah, the drop down would include effects AND the size boolean

I agree that this would be a good new feature. I actually created my own topic about this without realizing that this one already existed.