Discuss Scratch
- Discussion Forums
- » Suggestions
- » Helpful Workarounds for Frequently Suggested Blocks!
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Ugh…. Same… I don't understand what you are talking about xD
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Btw, this is what I usually do :
When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whatever
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Btw, is there a way to detect custom keys? I used join but it didnt work… I asked a few scratchers who made them but they said its a secret…?
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whatever
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 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
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Oops, wrong one, its supposed to be : Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whatever
When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
reset timer
broadcast [message 1 v]
forever
set [timer v] to (timer)
end
When I receive [message 1 v]
... // do whatever
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
please remove the “timer + 0.02”.Oops, wrong one, its supposed to be : Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateverWhen green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
reset timer
broadcast [message 1 v]
forever
set [timer v] to (timer)
end
When I receive [message 1 v]
... // do whatever
Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateveroh 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
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Why? It's just to make sure…please remove the “timer + 0.02”.Oops, wrong one, its supposed to be : Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateverWhen green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
reset timer
broadcast [message 1 v]
forever
set [timer v] to (timer)
end
When I receive [message 1 v]
... // do whateverBtw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateveroh 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
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
then test it withought the timer + 0.02.Why? It's just to make sure…please remove the “timer + 0.02”.Oops, wrong one, its supposed to be : Btw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateverWhen green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
reset timer
broadcast [message 1 v]
forever
set [timer v] to (timer)
end
When I receive [message 1 v]
... // do whateverBtw, this is what I usually do :When green flag clicked
reset timer
forever
set [timer v] to (timer)
end
When [timer v] > ((timer::variables)+[0.02])
... // do whateveroh 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
- BearSlothCoding
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Please snip your posts if there are unnecessary pieces of text in it, it makes it incredibly hard to scroll through and is pretty close to spamming.
- Just_ng
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
then test it withought the timer + 0.02.Oh…yea it works but its just to makw sure
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
but you're already sure.then test it withought the timer + 0.02.Oh…yea it works but its just to makw sure
- gosoccerboy5
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Like BSC said, please snip the posts.
- SeuAmigo35
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
guess i'll leave this topic for a whilei can't understandugh nevermindoh my god. nevermind. here goes the next one.no one is gonna quote this??? -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 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
- Vanilla2011
- Scratcher
500+ posts
Helpful Workarounds for Frequently Suggested Blocks!
Oh yeah because you can't divide by 0.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)
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!
Yeah how could I understand you only snip occasionally which makes it very hard to read.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.
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!
then see the previous pages or snip it yourselfYeah how could I understand you only snip occasionally which makes it very hard to read.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-
tell the stop sing block script problems (not all of them)when(::#ff0000)clicked::hat eventsThe purpose of the Stop button is to stop everything in the project, not start some more scripts.
- patataman4
- Scratcher
3 posts
Helpful Workarounds for Frequently Suggested Blocks!
Hello! I have a suggestion, I know it's quite a lot, but it would be great if it were on Scratch. My suggestion is to add an option for two or more Scratchers to collaborate in real time on a project. Something similar to an online. That the cursor of the other scratcher can be seen in the editor and that you can work at the same time. For example, if there is a button in the editor that when you press it, it will show you a password, allowing the other Scratcher to work with you if it is shown to you.
I don't know if it's too much, but it would be great.
Thanks for your attention
This is an example: https://cdn.discordapp.com/attachments/683669228678676495/764520445142892554/Example.png
I don't know if it's too much, but it would be great.
Thanks for your attention
This is an example: https://cdn.discordapp.com/attachments/683669228678676495/764520445142892554/Example.png
- BearSlothCoding
- Scratcher
1000+ posts
Helpful Workarounds for Frequently Suggested Blocks!
In the future, please make your suggestions as a new topic or else very few people will see it. Also, that is a Hello! I have a suggestion, I know it's quite a lot, but it would be great if it were on Scratch. My suggestion is to add an option for two or more Scratchers to collaborate in real time on a project. Something similar to an online. That the cursor of the other scratcher can be seen in the editor and that you can work at the same time. For example, if there is a button in the editor that when you press it, it will show you a password, allowing the other Scratcher to work with you if it is shown to you.rejected suggestion. In the future, you'll need to make sure it isn't rejected because if it is, it will never be added.
I don't know if it's too much, but it would be great.
Thanks for your attention
This is an example: https://cdn.discordapp.com/attachments/683669228678676495/764520445142892554/Example.png
However, there currently is a suggestion for a turn-based collaboration system that is not rejected 2.1 Adding users to work on projectshere.
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations, but also because it could lead to private messaging; for more information, see #7.1 on this list. This suggestion includes live editing (similar to Google Docs) and other forms of private collaboration. If you would like to work on a project with another Scratcher, you can remix each others' projects.
- ViniBloxEr
- Scratcher
64 posts
Helpful Workarounds for Frequently Suggested Blocks!
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…i'm so sorry pleasehello i'm her to try to help finding the workarounds<<>()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
- 12944qwerty
- Scratcher
100+ posts
Helpful Workarounds for Frequently Suggested Blocks!
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.
- Discussion Forums
- » Suggestions
- » Helpful Workarounds for Frequently Suggested Blocks!