ElectromanRocks718 wrote:

Hey, thanks for adding my suggestion!

Nambaseking01 wrote:

ElectromanRocks718 wrote:

Hey, thanks for adding my suggestion!

If it's frequently suggested, there's no proof that OP saw it exactly on your topic - there are more chances.

( pitch effect?)

(letter number () of ())

the_ck_empire wrote:

may I get

( pitch effect?)

set [pitch v] effect to (...::grey)::sound
set [pitch v] to (the pitch affect::grey)

bowsertendo666a wrote:

(letter number () of ())

(letter () of [world])

when clone clicked::hat control

when I start as a clone
forever
if <<mouse down?> and <touching [mouse pointer v]?>> then
...
end
end

IsaiahContreras wrote:

Suggestion:

when clone clicked::hat control

Can be done with this code:

when I start as a clone
forever
if <<mouse down?> and <touching [mouse pointer v]?>> then
...
end
end

IsaiahContreras wrote:

Suggestion:

when clone clicked::hat control

Can be done with this code:

when I start as a clone
forever
if <<mouse down?> and <touching [mouse pointer v]?>> then
...
end
end

bowsertendo666a wrote:

(letter number () of ())

(letter (...::grey) of [...::grey])

talk [Hello!] :: pen

say (quote)
speak (quote) :: pen
say []

Beamy68 wrote:

Here is a workaround for

previous costume :: looks

Create the variable “c”

switch costume to (c) // This variable is set to "previous costume"

That's it!
I figured this out in my project Tests which you should check out!

You know you can just do this:

switch costume to [... v]// do this (see †)
((costume #) - (1))//†

PixelYoshi wrote:

Scratch---Cat wrote:

Add a new category called “3D Scratch”

there would not be a reason to do that. nobody is posting workarounds for any 3D blocks, 3D code is extremely complicated most of the time, and most scratchers probably would not understand it. (i don't understand most 3D code XD) so really, there is no point in making a 3D blocks category.

no8pupil wrote:

PixelYoshi wrote:

Scratch---Cat wrote:

Add a new category called “3D Scratch”

there would not be a reason to do that. nobody is posting workarounds for any 3D blocks, 3D code is extremely complicated most of the time, and most scratchers probably would not understand it. (i don't understand most 3D code XD) so really, there is no point in making a 3D blocks category.

there could be for Scratch 4.0, probably, but please just be careful for… something. ¯\_(ツ)_/¯

render [rectangle v] height () width () length () ::pen

Seth_Zaw wrote:

Add this:

talk [Hello!] :: pen

=

say (quote)
speak (quote) :: pen
say []

no8pupil wrote:

PixelYoshi wrote:

Scratch---Cat wrote:

Add a new category called “3D Scratch”

there would not be a reason to do that. nobody is posting workarounds for any 3D blocks, 3D code is extremely complicated most of the time, and most scratchers probably would not understand it. (i don't understand most 3D code XD) so really, there is no point in making a 3D blocks category.

there could be for Scratch 4.0, probably, but please just be careful for… something. ¯\_(ツ)_/¯

no8pupil wrote:

Beamy68 wrote:

Here is a workaround for

previous costume :: looks

Create the variable “c”

switch costume to (c) // This variable is set to "previous costume"

That's it!
I figured this out in my project Tests which you should check out!

You know you can just do this:

switch costume to [... v]// do this (see †)
((costume #) - (1))//†

Yeah, I know, besides! I found a better way, Make a costume called “previous costume” then set the switch costume block to that costume, drag it into your backpack, and delete the costume named “previous costume” now the backpacked script will do previous costume.

<mouse down?>

<mouse down?>

<mouse down?>

hmcn4404 wrote:

I understand there is a mouse down block

<mouse down?>

but why can't there be a mouse up block?

im pretty sure other people who want to make projects were people can draw want they want would appreciate it because it would make there projects code easier to make.

forever
if <mouse down?> then
wait until <not <mouse down?>>
broadcast [run code v]
end
end

when I receive [run code v]
. . .