12944qwerty wrote:

Hmm, nice idea! This could also be added to the wiki. Maybe join it to help with this? If you don't want to, I can do it instead, as well as with other wikians.

ViniBloxEr wrote:

sorry i can't find workarounds to blocks i'm not smart i won't be doing comments here for a while

Back in page 3…

ViniBloxEr wrote:

hello i'm her to try to help finding the workarounds

<<>()secs ago? :: operators>

Hmmmmmmmm…
i give up

i'm so sorry please

when green flag clicked
forever
set [ v] to []
end
define (this is a lot of ideas)
say [there are a ton of posts in this forum thread] for (2) secs

12944qwerty wrote:

Hmm, nice idea! This could also be added to the wiki. Maybe join it to help with this? If you don't want to, I can do it instead, as well as with other wikians.

when green flag clicked
forever
if <have [any ideas v]?> then
broadcast [discuss blocks v]
end

when I receive [discuss blocks v]
print [first v] instruction
broadcast [print instruction v]

when I receive [print instruction v]
set x to [0]
set y to [0]
type of ease: [Ease In v] glide to x: (0) y: (-240) speed: (5)
when gliding, [do ease in v] x squash: (30) y stretch: (30)
forever
if <on edge?> then
set ease out squash to [30]
set ease out stretch to [30]
end
end

SeuAmigo35 wrote:

ViniBloxEr wrote:

SeuAmigo35 wrote:

SeuAmigo35 wrote:

SeuAmigo35 wrote:

SeuAmigo35 wrote:

-the ultimate snip-
ok ok… i will do this time 2 problems in each comment. let's get started.
Problem 1: no continues (already solved)
did you know the script of the stop sing that everyone uses only happens once? the timer stops being reseted and if the person press stop sing 2 times, it won't acts. here the safe way:

when green flag clicked
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
...::cap

Problem 2: script stoping
Have you ever used the stop sing block in a project that has the

stop [all v]

block? well, if you do this, the script of the stop sing will stop and act.
that should be one of the worst problems. it's like a workaround to

when project stopped::events hat

block. to solve it, make a spirite and put only that:

when green flag clicked
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
broadcast [stop sing v]

then put that to replace the

stop [all v]

block (in other spirite):

...::hat
stop [other scripts from the spirite v]::control//i can't fix it help me
broadcast [stop v]
stop [this script v]

for the other spirites exept the stop sing spirite:

when I receive [stop v]
stop [other scripts from the spirite v]

for the spirites you want to do something when stop sing is clicked:

when I receive [stop sing v]
...::cap

no one is gonna quote this???

oh my god. nevermind. here goes the next one.
Problem 3: other blocks
there are lots of “workarounds to frequently suggested blocks” that uses the timer. however, if we use the

repeat for () secs{}@loopArrow :: control

workaround and the

when (::) clicked ::hat events

at the same time, it will repeat FOREVER.
that's where the second method stands for. however, it don't solve the previous problems, so we do it like this:

when green flag clicked
forever
set [timer v] to (timer)
end
when [timer v] > (timer)
forever
reset timer
end
when [timer v] > (timer)
broadcast [stop sing v]

the workaround that people do for “repeat for () scs” is this one:

...::hat
reset timer
repeat until <(timer) = (wanted seconds)>
...
end
...::cap

however, it don't work (did you seen what happen when it happens 2 times?) i'm trying to find a better workaround.

ugh nevermind

i can't understand

guess i'll leave this topic for a while

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

when green flag clicked

if <you have a new idea> then(post a new topic)
define (post a new topic)
(post a new topic)

end

define Previous Costume
switch costume to ((costume #) - (1))

Previous costume

---4k--- wrote:

Previous costume: WORKS!

define Previous Costume
switch costume to ((costume #) - (1))

Previous costume

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

JPOWERPUFFGIRLS wrote:

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

You wait

Ryzonno2 wrote:

JPOWERPUFFGIRLS wrote:

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

You wait

its been like a week

Ryzonno2 wrote:

JPOWERPUFFGIRLS wrote:

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

You wait

its been like a week

it may be a great idea, but kinda complicated to new scratchers and younger people

ninta-the-ferret wrote:

Ryzonno2 wrote:

JPOWERPUFFGIRLS wrote:

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

You wait

its been like a week

it may be a great idea, but kinda complicated to new scratchers and younger people

Ryzonno2 wrote:

ninta-the-ferret wrote:

Ryzonno2 wrote:

JPOWERPUFFGIRLS wrote:

Ryzonno2 wrote:

shradibop wrote:

Ryzonno2 wrote:

I came up with a get color input block. Though it has not been denied yet, I am pretty sure it will be. There is a way around it, but that would literally require over 5 million blocks of code. Info on my block below.

([a v] of [b v] from [c v])

([a v] of layer () from [c v])

a = color, saturation, or brightness

b = front layer, back layer, this sprite, (names of other sprites), backdrop, or all

c = this sprite, (names of other sprites), center, or mouse-pointer

If you want the idea to be suggested, you should make a new topic.

This is the topic you go to if your block was rejected and you want to find a way to simulate the effects of the denied block. You could also use this topic if you don't want to wait for an ST member to accept or create it.

I did, but the scratch team still has yet to respond. How do I get them to see it?

You wait

its been like a week

it may be a great idea, but kinda complicated to new scratchers and younger people

well, there are already multiple blocks like that, such as custom blocks,