This goes with the color, brightness, pixilate, swirl, mosaic and such block.

And I'd like to see saturation control for the pen, too.
(See this project for custom blocks that provide hue, saturation and lightness control for the pen for now, until the Scratch devs give us built-in saturation control… pretty please )

However, I think one of the reasons it's not there now (both pen & sprite effects) is because many Scratchers would not understand what it means.
I'd be tempted to use a word like “greyness” instead, and have it be the reverse of saturation (so zero is the current default, and 100 would be totally grey, at which point the colour plays no part).

So:

set pen color to ()
set pen shade to () // why isn't this "brightness', like below?
set pen greyness to () //category=pen

set [color v] effect to ()
set [brightness v] effect to ()
set [greyness v] effect to ()

Note that the brightness effect is slightly different to the pen's “shade” block, in that it can both brighten (positive values) and darken (negative values) a costume. I wonder if that's why the name is different…?

I've been supporting a duplicate this entire time…
Support! It could be useful for my strange purposes of creating some sort of strange dress up game



I have the strangest priorities

go [in front of v] sprite [sprite1 v] :: looks

Support for a “greyness” effect as per DadOfMrLog.

BurnedCrystal wrote:

I am the lord of potatoes

How dare you steal my title

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

I only half support as I did in said duplicate:

BurnedCrystal wrote:

Duplicate

Me wrote:

75%, just use the art editor if you want a greyscale game.

Scratcher1002 wrote:

I only half support as I did in said duplicate:

BurnedCrystal wrote:

Duplicate

Me wrote:

75%, just use the art editor if you want a greyscale game.

Isn't just for greyscale (I realize you know this)

go [in front of v] sprite [sprite1 v] :: looks

BurnedCrystal wrote:

Scratcher1002 wrote:

I only half support as I did in said duplicate:

BurnedCrystal wrote:

Duplicate

Me wrote:

75%, just use the art editor if you want a greyscale game.

Isn't just for greyscale (I realize you know this)

I know, but all the things that this block accomplishes is already in the art editor.

Scratcher1002 wrote:

BurnedCrystal wrote:

Scratcher1002 wrote:

I only half support as I did in said duplicate:

BurnedCrystal wrote:

Duplicate

Me wrote:

75%, just use the art editor if you want a greyscale game.

Isn't just for greyscale (I realize you know this)

I know, but all the things that this block accomplishes is already in the art editor.

This property is shared by the Brightness and Color effects (And you're also still wrong, the art editor still doesn't have a desaturate button- technically you still have to do that yourself)

We already have the libraries too :^

go [in front of v] sprite [sprite1 v] :: looks

DaSpudLord wrote:

Support for a “greyness” effect as per DadOfMrLog.

Support for this, but since Scratch is made in America, it should be called “grayness.”
Reason: color (hue) and brightness (value) exist, so why not grayness (saturation)

BurnedCrystal wrote:

Scratcher1002 wrote:

BurnedCrystal wrote:

Scratcher1002 wrote:

I only half support as I did in said duplicate:

BurnedCrystal wrote:

Duplicate

Me wrote:

75%, just use the art editor if you want a greyscale game.

Isn't just for greyscale (I realize you know this)

I know, but all the things that this block accomplishes is already in the art editor.

This property is shared by the Brightness and Color effects (And you're also still wrong, the art editor still doesn't have a desaturate button- technically you still have to do that yourself)

We already have the libraries too :^

I know it doesn't have de-saturate button, but this doesn't make sense, why would you need to grayscale the sprite IN the project? Just design it yourself.

Scratcher1002 wrote:

I know it doesn't have de-saturate button, but this doesn't make sense, why would you need to grayscale the sprite IN the project? Just design it yourself.

I could say the same for color blocks

what's your point?

go [in front of v] sprite [sprite1 v] :: looks

BurnedCrystal wrote:

Scratcher1002 wrote:

I know it doesn't have de-saturate button, but this doesn't make sense, why would you need to grayscale the sprite IN the project? Just design it yourself.

I could say the same for color blocks

what's your point?

My point is we don't NEED it. But nonetheless, support.

bunp

go [in front of v] sprite [sprite1 v] :: looks

Bump

bunp

go [in front of v] sprite [sprite1 v] :: looks

Bump.

Support! This would make for some fun projects Animators would find it useful too!

(Foo)

DadOfMrLog wrote:

And I'd like to see saturation control for the pen, too.
(See this project for custom blocks that provide hue, saturation and lightness control for the pen for now, until the Scratch devs give us built-in saturation control… pretty please )

However, I think one of the reasons it's not there now (both pen & sprite effects) is because many Scratchers would not understand what it means.
I'd be tempted to use a word like “greyness” instead, and have it be the reverse of saturation (so zero is the current default, and 100 would be totally grey, at which point the colour plays no part).

So:

set pen color to ()
set pen shade to () // why isn't this "brightness', like below?
set pen greyness to () //category=pen

set [color v] effect to ()
set [brightness v] effect to ()
set [greyness v] effect to ()

Note that the brightness effect is slightly different to the pen's “shade” block, in that it can both brighten (positive values) and darken (negative values) a costume. I wonder if that's why the name is different…?

set pen greyness to () :: pen

use that to stop the red blocks

when I start as a clone
delete this clone

I do support but it’s a rejected feature that caused too much lag and was removed… I suppose it could’ve crashed Scratch

humphrey4444444444 wrote:

I do support but it’s a rejected feature that caused too much lag and was removed… I suppose it could’ve crashed Scratch

It doesn't specifically say here that the saturation block is rejected; also since Scratch 3.0 is being made with HTML5 there's a chance implementing the block could work better this time.