Discuss Scratch
- Discussion Forums
- » Suggestions
- » Helpful Workarounds for Frequently Suggested Blocks!
- Ihatr
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Keep in mind that these are frequently suggested blocks. If you find a block that's frequently suggested, and want it to be added, leave a reply to the post. I'm sure @shradibop will be more than happy to add it.I know but the are missing so manyI'm quite sure they plan to keep the sticky around for a while. Hey @shradibop, could I make the next one sometime?
- shradibop
- Scratcher
100+ posts
Helpful Workarounds for Frequently Suggested Blocks!
bruhI know but the are missing so manyI'm quite sure they plan to keep the sticky around for a while. Hey @shradibop, could I make the next one sometime?
hey. what's good
hopefully, i'm having fun right now
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
oh my god. nevermind. here goes the next one.no one is gonna quote this???ok ok… i will do this time 2 problems in each comment. let's get started.Which is a waste of time. The problem with your system is that you post one problem, then you wait for me (before it was me, now it will be shradibop) to respond to it. Once I respond, then I will have to wait for you to respond again with the other problem and then this repeats for however many problems there are. This is the reason I didn't keep going with it, I left the stop sign script wrong because it was such an irritating hassle that I wasn't in the mood for and never was. I don't expect shradibop to act any differently because very few people have the patience to keep responding, waiting for their “LOTS of problems” to get called out. All the while the person calling them out keeps acting somewhat rude by putting unnecessary phrases in bold that makes a lot of the post seem aggressive. And keep putting things in caps which shows that what they are talking about is important and needs to be emphasized, yet they take their time to tell you exactly what they are talking about. Most of this could not happen if you could just post them all in one post (or maybe two or three so you don't have a post that you need to spend a minute scrolling through) and there is no waiting at all.there is a LOT of problems, i will make the same thing as before: each time this comment get quoted, i tell one of the problems.But why not now? If you wait for 8 pages to pass, it will get popular and people will use the wrong workaround. Or you could do it now, and this topic won't have any problems.remember the problems i said about the “when stop sing clicked” block? you've only putted the solvement of 1 of them, an i only want to tell in this one when it gets popular. I'd suggest getting the link to each post and putting it in the OP like I did for easier navigation, otherwise it kind of defeats the purpose of having them in separate posts. Great job otherwise though, I think this one will turn out a lot better than mine did.Why? (gonna repost this when the forum reaches 10 pages)
Or I could just post the link to when you posted it and this could all be over.
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 clickedProblem 2: script stoping
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
...::cap
Have you ever used the stop sing block in a project that has thestop [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 towhen project stopped::events hatblock. to solve it, make a spirite and put only that:when green flag clickedthen put that to replace the
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
broadcast [stop sing v]stop [all v]block (in other spirite):...::hatfor the other spirites exept the stop sing spirite:
stop [other scripts from the spirite v]::control//i can't fix it help me
broadcast [stop v]
stop [this script v]when I receive [stop v]for the spirites you want to do something when stop sing is clicked:
stop [other scripts from the spirite v]when I receive [stop sing v]
...::cap
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 :: controlworkaround and the
when (::) clicked ::hat eventsat 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 clickedthe workaround that people do for “repeat for () scs” is this one:
forever
set [timer v] to (timer)
end
when [timer v] > (timer)
forever
reset timer
end
when [timer v] > (timer)
broadcast [stop sing v]
...::hathowever, it don't work (did you seen what happen when it happens 2 times?) i'm trying to find a better workaround.
reset timer
repeat until <(timer) = (wanted seconds)>
...
end
...::cap
- cooldude-222
- Scratcher
100+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Can you add workarounds for create a variable?
Have a nice day!
- Vanilla2011
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Why do we even need this block? -snip-
goes on and on and on about a block
when(::#ff0000)clicked::hat eventsThe purpose of the Stop button is to stop everything in the project, not start some more scripts.
aw heck naw someones' wanting to ban the sab spunch bop faec from scrathc
(ツ::#000)//Master Kakawam, slays evil kumquats.
- Vanilla2011
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Why do you need to add the 0 at the end? I already asked the previous owner of this topic to edit that, but they didn't edit it. I ask the new owner of the sticky the same.[sign v] of () :: reporter operators // reports "1" if the input is positive, "-1" if negative, and "0" when the number is 0.can be workarounded with:(((n) / ([abs v] of (n)))+(0))
aw heck naw someones' wanting to ban the sab spunch bop faec from scrathc
(ツ::#000)//Master Kakawam, slays evil kumquats.
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
you don't understand. i'm showing some problems with the “when stop sing clicked” script and the ways to solve them.Why do we even need this block? -snip-
goes on and on and on about a blockwhen(::#ff0000)clicked::hat eventsThe purpose of the Stop button is to stop everything in the project, not start some more scripts.
Last edited by SeuAmigo35 (Oct. 7, 2020 14:14:55)
- Ihatr
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
It's because the workaround won't report 0 if the number is 0. Without theWhy do you need to add the 0 at the end? I already asked the previous owner of this topic to edit that, but they didn't edit it. I ask the new owner of the sticky the same.[sign v] of () :: reporter operators // reports "1" if the input is positive, "-1" if negative, and "0" when the number is 0.can be workarounded with:(((n) / ([abs v] of (n)))+(0))
((foo) + (0))block, it reports "NaN. (if the value of foo is 0)
- DoubleDimensions
- Scratcher
3 posts
Helpful Workarounds for Frequently Suggested Blocks!
Can you add a if touching clones?
It will be usefull for a hotbar and can you make clone names? Thanks.
It will be usefull for a hotbar and can you make clone names? Thanks.
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
what Can you add a if touching clones?
It will be usefull for a hotbar and can you make clone names? Thanks.
- ViniBloxEr
- Scratcher
64 posts
Helpful Workarounds for Frequently Suggested Blocks!
hello i'm her to try to help finding the workarounds
i give up
<<>()secs ago? :: operators>Hmmmmmmmm…
i give up
I'm @SeuAmigo35ING acaunt. wat wawawat? Your thenk i'm fAIK? Then yall shiuld gol intro arestING.
if <on arestING?:: sensing> then
Yall donu't knaw wOAHt tok dok:: looks
end
(:D :: sensing)//mis (neAw) kumkuat protectur! :D
- ViniBloxEr
- Scratcher
64 posts
Helpful Workarounds for Frequently Suggested Blocks!
WHATwhat Can you add a if touching clones?
It will be usefull for a hotbar and can you make clone names? Thanks.
I'm @SeuAmigo35ING acaunt. wat wawawat? Your thenk i'm fAIK? Then yall shiuld gol intro arestING.
if <on arestING?:: sensing> then
Yall donu't knaw wOAHt tok dok:: looks
end
(:D :: sensing)//mis (neAw) kumkuat protectur! :D
- DoubleDimensions
- Scratcher
3 posts
Helpful Workarounds for Frequently Suggested Blocks!
Can you add cloud lists?
Last edited by DoubleDimensions (Oct. 7, 2020 23:31:56)
- scratchastroLOL
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
please don't blockspamclear
that idea is rejected Can you add cloud lists?
? ya
Edit: no
Give internet pliz | Take part in a Scratch project
Backup signatures:
First siggy:
Give internet pliz: http://internetometer.com/give/47737
Second siggy:
Third siggy:
Give internet pliz | Give meh some comic ideas | Decide the name for the new Scratch cryptocurrency
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
ugh nevermindoh my god. nevermind. here goes the next one.no one is gonna quote this???ok ok… i will do this time 2 problems in each comment. let's get started.Which is a waste of time. The problem with your system is that you post one problem, then you wait for me (before it was me, now it will be shradibop) to respond to it. Once I respond, then I will have to wait for you to respond again with the other problem and then this repeats for however many problems there are. This is the reason I didn't keep going with it, I left the stop sign script wrong because it was such an irritating hassle that I wasn't in the mood for and never was. I don't expect shradibop to act any differently because very few people have the patience to keep responding, waiting for their “LOTS of problems” to get called out. All the while the person calling them out keeps acting somewhat rude by putting unnecessary phrases in bold that makes a lot of the post seem aggressive. And keep putting things in caps which shows that what they are talking about is important and needs to be emphasized, yet they take their time to tell you exactly what they are talking about. Most of this could not happen if you could just post them all in one post (or maybe two or three so you don't have a post that you need to spend a minute scrolling through) and there is no waiting at all.there is a LOT of problems, i will make the same thing as before: each time this comment get quoted, i tell one of the problems.But why not now? If you wait for 8 pages to pass, it will get popular and people will use the wrong workaround. Or you could do it now, and this topic won't have any problems.remember the problems i said about the “when stop sing clicked” block? you've only putted the solvement of 1 of them, an i only want to tell in this one when it gets popular. I'd suggest getting the link to each post and putting it in the OP like I did for easier navigation, otherwise it kind of defeats the purpose of having them in separate posts. Great job otherwise though, I think this one will turn out a lot better than mine did.Why? (gonna repost this when the forum reaches 10 pages)
Or I could just post the link to when you posted it and this could all be over.
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 clickedProblem 2: script stoping
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
...::cap
Have you ever used the stop sing block in a project that has thestop [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 towhen project stopped::events hatblock. to solve it, make a spirite and put only that:when green flag clickedthen put that to replace the
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
broadcast [stop sing v]stop [all v]block (in other spirite):...::hatfor the other spirites exept the stop sing spirite:
stop [other scripts from the spirite v]::control//i can't fix it help me
broadcast [stop v]
stop [this script v]when I receive [stop v]for the spirites you want to do something when stop sing is clicked:
stop [other scripts from the spirite v]when I receive [stop sing v]
...::cap
Problem 3: other blocks
there are lots of “workarounds to frequently suggested blocks” that uses the timer. however, if we use therepeat for () secs{}@loopArrow :: controlworkaround and thewhen (::) clicked ::hat eventsat 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 clickedthe workaround that people do for “repeat for () scs” is this one:
forever
set [timer v] to (timer)
end
when [timer v] > (timer)
forever
reset timer
end
when [timer v] > (timer)
broadcast [stop sing v]...::hathowever, it don't work (did you seen what happen when it happens 2 times?) i'm trying to find a better workaround.
reset timer
repeat until <(timer) = (wanted seconds)>
...
end
...::cap
- ViniBloxEr
- Scratcher
64 posts
Helpful Workarounds for Frequently Suggested Blocks!
i can't understandugh nevermindoh my god. nevermind. here goes the next one.no one is gonna quote this???ok ok… i will do this time 2 problems in each comment. let's get started.Which is a waste of time. The problem with your system is that you post one problem, then you wait for me (before it was me, now it will be shradibop) to respond to it. Once I respond, then I will have to wait for you to respond again with the other problem and then this repeats for however many problems there are. This is the reason I didn't keep going with it, I left the stop sign script wrong because it was such an irritating hassle that I wasn't in the mood for and never was. I don't expect shradibop to act any differently because very few people have the patience to keep responding, waiting for their “LOTS of problems” to get called out. All the while the person calling them out keeps acting somewhat rude by putting unnecessary phrases in bold that makes a lot of the post seem aggressive. And keep putting things in caps which shows that what they are talking about is important and needs to be emphasized, yet they take their time to tell you exactly what they are talking about. Most of this could not happen if you could just post them all in one post (or maybe two or three so you don't have a post that you need to spend a minute scrolling through) and there is no waiting at all.there is a LOT of problems, i will make the same thing as before: each time this comment get quoted, i tell one of the problems.But why not now? If you wait for 8 pages to pass, it will get popular and people will use the wrong workaround. Or you could do it now, and this topic won't have any problems.remember the problems i said about the “when stop sing clicked” block? you've only putted the solvement of 1 of them, an i only want to tell in this one when it gets popular. I'd suggest getting the link to each post and putting it in the OP like I did for easier navigation, otherwise it kind of defeats the purpose of having them in separate posts. Great job otherwise though, I think this one will turn out a lot better than mine did.Why? (gonna repost this when the forum reaches 10 pages)
Or I could just post the link to when you posted it and this could all be over.
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 clickedProblem 2: script stoping
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
...::cap
Have you ever used the stop sing block in a project that has thestop [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 towhen project stopped::events hatblock. to solve it, make a spirite and put only that:when green flag clickedthen put that to replace the
forever
reset timer
end
when [timer v] > (0)
forever
reset timer
end
when [timer v] > (0)
broadcast [stop sing v]stop [all v]block (in other spirite):...::hatfor the other spirites exept the stop sing spirite:
stop [other scripts from the spirite v]::control//i can't fix it help me
broadcast [stop v]
stop [this script v]when I receive [stop v]for the spirites you want to do something when stop sing is clicked:
stop [other scripts from the spirite v]when I receive [stop sing v]
...::cap
Problem 3: other blocks
there are lots of “workarounds to frequently suggested blocks” that uses the timer. however, if we use therepeat for () secs{}@loopArrow :: controlworkaround and thewhen (::) clicked ::hat eventsat 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 clickedthe workaround that people do for “repeat for () scs” is this one:
forever
set [timer v] to (timer)
end
when [timer v] > (timer)
forever
reset timer
end
when [timer v] > (timer)
broadcast [stop sing v]...::hathowever, it don't work (did you seen what happen when it happens 2 times?) i'm trying to find a better workaround.
reset timer
repeat until <(timer) = (wanted seconds)>
...
end
...::cap
I'm @SeuAmigo35ING acaunt. wat wawawat? Your thenk i'm fAIK? Then yall shiuld gol intro arestING.
if <on arestING?:: sensing> then
Yall donu't knaw wOAHt tok dok:: looks
end
(:D :: sensing)//mis (neAw) kumkuat protectur! :D
- Za-Chary
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Totally missed whenever this was stickied — I didn't even realize there was a new topic about this. Nice work!
This is my forum signature! On a forum post, it is okay for Scratchers to advertise in their forum signature. The signature is the stuff that shows up below the horizontal line on the post. It will show up on every post I make.
I was a Scratch Team member from May 10th 2019 to October 29th 2021.
my notebook | scratch team essay | accessibility essay
- Discussion Forums
- » Suggestions
- » Helpful Workarounds for Frequently Suggested Blocks!