Scratch

ErnieParke · 2012-11-02 20:52:17

Seeing as some scratchers don't know how to make scratchblocks, how others don't know how to make some scratchblocks, and that there really hasn't been a guide to scratchblocks, I decided to make a guide on scratchblocks in general. If you see something that needs to be added/changed, just say. wink

Content:

Making Scratchblocks

Fixing Scripts

Scratchblock Etiquette

Credits

{|Making Scratchblocks|}

I could give you the code for every scratchblock there is in scratch, but do you know how long that would take to type? Instead, I'll teach you a different way.

To make a scratchblock, put it in between [scratchblocks] [/scratchblocks] tags. Then, type what you would see in Scratch. For example, in scratch, the green flag hat block has "when gf (green flag) clicked", so you would type "when gf clicked".

Now, the one exception to this is the c-blocks (repeat, if, ect.. Excluding forever and forever if.) which you'll have to put "end" where you want the c-block to end. Other than that, there should only be one block per line.

Now into the finer details:
If you want to add a drop down menu, use [ v]. If you want to add a place where you can type, again use ( ) or [ ]. And if you want to add arrows, type cw (clockwise) or ccw (counter-clock wise).

Along with that, if you want to add a colored box, just type a color's HEX code inside [ and ], some of which can be seen here. Also, if you want to leave a comment, use // after a scratchblock and type your comment after the two dashes.

Into conditionals/variables:
Basically, they follow the same rules as above, except variables should have parentheses around them. Also, any block that normally has pointy ends should have < and > surrounding them. Now, your almost done. smile

The two exceptions:
One exception to all of the above happens to be the "when sprite clicked" hat block. For some reason, you always have to type it as "when [sprite2 v] clicked" when you really should type "when sprite2 clicked" My only tip is to memorize this, which should be easy. The other exception is the "stop all sounds" block which is red no matter what you do, unless you type "stop all pinks".

Anyway, here's a sample code:

when [sprite2 v] clicked
set [pie v] to (98)
if <not <(pie) < (5)>>
 repeat (5)
  turn cw (5) degrees
  say [Pie!] for (5) secs//This is a comment.
 end
end
forever if <touching color [#00FF00]?>
 go to x: (5) y: (4)
 stop all pinks

And this is what I wrote:

Code:

[scratchblocks]
when [sprite2 v] clicked
set [pie v] to (98)
if <not <(pie) < (5)>>
 repeat (5)
  turn cw (5) degrees
  say [Pie!] for (5) secs//This is a comment.
 end
end
forever if <touching color [#00FF00]?>
 go to x: (5) y: (4)
 stop all pinks
[/scratchblocks]

Congradulations on learning how to make scratchblocks!

Remember, if you ever want more practice, you can go here, or if you want to have a program create your code for you, you can go here.

{|Fixing Scripts|}

if (touching [mouse v]?
 if <(mouse)>(5)>
  go to x (5) y (6)
 end
end

Have you ever gotten an if statement like this? Do your scripts always look red when they shouldn't? Well follow these tips and you should be fixing scripts more quickly!

Conditionals:

When looking at a messed up conditional, my first tip is to look at the code and count the parentheses facing left and the ones facing right. You should have an equal amount of both, so if you don't, then that's part of your problem. The same thing should be true with <'s when you're excluding the ones in inequality statements.

Another tip that I have is that if an inequality doesn't seem to be right, then make sure that there is a space between the inequality sign and the two conditions. As seen above in the second if block, spaces weren't included before and after the inequality sign so the script became messed up.

Along with all of that, there are two common mistakes that are often made. Someone might forget to add a question mark, and British colour might be used instead of color, both of which will cause problems in your script. So, when fixing scripts, check those things.

Blocks:

If your scripts are becoming red when they shouldn't, then what might be happening is that you forgot to put a number in parentheses or you forgot a letter. For example, one common problem is that someone might use "seconds" instead of "secs" Another common mistake is that receive might be spelled as recieve. Other than that, problems here can vary greatly, so my next tip is that you could open scratch and compare the text in the actual block with the text in your block, or you could hunt for an example in the Scratchblocks testing area, find an example, quote it and look at the code.

{|Scratchblock Etiquette|}

Posting random scratchblocks in the forums is seen as, well, unnecessary and spamming. It is also frowned upon when you post a post just to test some script, because there's the preview button as well as the Scratchblocks testing area in the Help with Scripts forum to look at your scripts. Another thing that is considered annoying is posting scratchblocks tags before quote tags while having the inner two switched. This is considered annoying because it messes up the the web page as well as every post that follows it, so don't do it.

Now you're asking, If there are all these things not to do, what should I do? Well, what you could do is when you do post a script, try and include several comments as to help explain the purpose of the script. Another thing you could do is that if you see a script with some problems in it, you could quote it and fix it. I often do this as it helps clarify what the script is and it also helps the scratcher learn from their mistakes.

{|Credits|}

Thanks to joefarebrother for pointing out several missing pieces of info!

Thanks to Martiscratch for giving me the link to the HEX color page!

Thanks to awsomeness321 for pointing out what part of joefarebrother's post meant & pointing out two things I could add!

Paddle2See for his amazing scratch program!

Last updated: 1/12/13

Last edited by ErnieParke (2013-01-12 11:30:58)

Dazachi · 2012-11-03 23:20:57

Nice guide!

ErnieParke · 2012-11-04 09:03:42

Dazachi wrote:
Nice guide!

Thanks! big_smile

Anyway, I'm curious, did you find any part of the guide confusing? Is there anything you would like to see added to this guide? Thanks in advance for your feedback!

Borrego6165 · 2012-11-04 14:19:39

to be honest, I don't think I need to read it. not because I was put off by the start, because it's a topic where you can't really go wrong. Perhaps it's a bit long considering what you're trying to help scratchers do, perhaps you should start with an X-Step Quick Guide, then go into detail and keep everything you've written underneath. oh, and nice guide! tongue

ErnieParke · 2012-11-04 14:59:22

Borrego6165 wrote:
to be honest, I don't think I need to read it. not because I was put off by the start, because it's a topic where you can't really go wrong. Perhaps it's a bit long considering what you're trying to help scratchers do, perhaps you should start with an X-Step Quick Guide, then go into detail and keep everything you've written underneath. oh, and nice guide!

Part of the reason why it's long is due to the fact that I talk about etiquette and fixing scripts, though I agree, the Making Scratchblocks section does seem a bit long. I'll see what I can do. Anyway, thanks for the feedback!

GenChico · 2012-11-10 22:25:13

Pretty cool guide, helped a lot with understanding the basics of scratch blocks. I would definitely refer people to this If they needed help with scratch blocks.

ErnieParke · 2012-11-11 09:23:52

GenChico wrote:
Pretty cool guide, helped a lot with understanding the basics of scratch blocks. I would definitely refer people to this If they needed help with scratch blocks.

Well I'm glad to here that you've fully understood scratchblocks and that you trying to help others do the same thing! smile

Ideas · 2012-11-11 09:49:14

Excellent guide, you should add step by step guide to making variables and lists for each varible and list block.

Scratch on.

joefarebrother · 2012-11-11 10:00:41

You should mention that when scratchblocks go red even when they look the same as in scratch, it is usually a missing question mark or the British spelling of colour instead of color. Also mention that the stop all sounds blorck always goes red even when it looks just like the text in scratch is.

Edit: you forgot to mention how to add colours.

Last edited by joefarebrother (2012-11-11 10:02:36)

ErnieParke · 2012-11-11 10:15:24

Ideas wrote:
Excellent guide, you should add step by step guide to making variables and lists for each varible and list block.

Scratch on.

Well this guide already covers that; just type what you would see in Scratch. Other than that, thanks!

joefarebrother wrote:
You should mention that when scratchblocks go red even when they look the same as in scratch, [1] it is usually a missing question mark or the British spelling of colour instead of color. [2] Also mention that the stop all sounds blorck always goes red even when it looks just like the text in scratch is.

[3] Edit: you forgot to mention how to add colours.

1). I completely forgot about that, so thanks for reminding me. I'll add that when I have time.

Edit: Added.

2). I never knew about that, or at least I did at one point but I forgot afterwards. I'll add it when I can.

Edit: Added.

3). And what do you mean by adding colours?

Last edited by ErnieParke (2012-11-11 11:24:38)

awesomeness321 · 2012-11-11 10:33:13

ErnieParke wrote:
Ideas wrote:
Excellent guide, you should add step by step guide to making variables and lists for each varible and list block.

Scratch on.
Well this guide already covers that; just type what you would see in Scratch. Other than that, thanks!

joefarebrother wrote:
You should mention that when scratchblocks go red even when they look the same as in scratch, [1] it is usually a missing question mark or the British spelling of colour instead of color. [2] Also mention that the stop all sounds blorck always goes red even when it looks just like the text in scratch is.

[3] Edit: you forgot to mention how to add colours.
1). I completely forgot about that, so thanks for reminding me. I'll add that when I have time.

2). I never knew about that, or at least I did at one point but I forgot afterwards. I'll add it when I can.

Edit: Added.

3). And what do you mean by adding colours?

3. He means, for example:

<touching color [#FF0000]?>

is

Code:

 <blah blah [#FF0000]?>

ErnieParke · 2012-11-11 11:07:24

awesomeness321 wrote:
ErnieParke wrote:
Ideas wrote:
Excellent guide, you should add step by step guide to making variables and lists for each varible and list block.

Scratch on.
Well this guide already covers that; just type what you would see in Scratch. Other than that, thanks!

joefarebrother wrote:
You should mention that when scratchblocks go red even when they look the same as in scratch, [1] it is usually a missing question mark or the British spelling of colour instead of color. [2] Also mention that the stop all sounds blorck always goes red even when it looks just like the text in scratch is.

[3] Edit: you forgot to mention how to add colours.
1). I completely forgot about that, so thanks for reminding me. I'll add that when I have time.

Edit: Added.

2). I never knew about that, or at least I did at one point but I forgot afterwards. I'll add it when I can.

Edit: Added.

3). And what do you mean by adding colours?
3. He means, for example:
<touching color [#FF0000]?>
is
Code:
 <blah blah [#FF0000]?>

Oh... I'll add that.

Edit: Added.

Last edited by ErnieParke (2012-11-11 11:25:03)

Martiscratch · 2012-11-11 11:50:38

btw,If you want other colours use this.

Gravitation · 2012-11-11 11:58:23

Martiscratch wrote:
btw,If you want other colours use this.

Either that or you can use the color picker in Gimp, write your own (strongly recommended tongue ), or use http://www.2createawebsite.com/build/hex-colors.html

ErnieParke · 2012-11-11 12:00:25

Martiscratch wrote:
btw,If you want other colours use this.

I didn't even know about that, and I really like the program, so I'll use that link instead. Thanks!

awesomeness321 · 2012-11-11 12:09:46

ErnieParke wrote:
"stop all sounds" block which is red no matter what you do.

Actually,


stop all sounds//This doesn't work. Instead, use:
stop all pinks//This is what works.

Gravitation · 2012-11-11 12:11:52

awesomeness321 wrote:
ErnieParke wrote:
"stop all sounds" block which is red no matter what you do.
Actually,
stop all sounds//This doesn't work. Instead, use:
stop all pinks//This is what works.

Yeah, EP knows, but technically that's not "stop all sounds".

awesomeness321 · 2012-11-11 12:13:56

Gravitation wrote:
awesomeness321 wrote:
ErnieParke wrote:
"stop all sounds" block which is red no matter what you do.
Actually,
stop all sounds//This doesn't work. Instead, use:
stop all pinks//This is what works.
Yeah, EP knows, but technically that's not "stop all sounds".

Well, he should at least mention it.

ErnieParke · 2012-11-11 13:57:31

awesomeness321 wrote:
Gravitation wrote:
awesomeness321 wrote:
Actually,
stop all sounds//This doesn't work. Instead, use:
stop all pinks//This is what works.
Yeah, EP knows, but technically that's not "stop all sounds".
Well, he should at least mention it.

If you look again, you'll see that I added it. I think that it's nice to know, even though it's not going to be used very often. Also, you could get a lugh or two from it.

Last edited by ErnieParke (2012-11-11 14:05:51)

awesomeness321 · 2012-11-12 18:01:51

Another thing:

Many people type:

say [whatever] for (2) seconds

So you should explain that you need to type 'secs' instead of 'seconds'.

ErnieParke · 2012-11-12 18:38:42

awesomeness321 wrote:
Another thing:

Many people type:
say [whatever] for (2) seconds
So you should explain that you need to type 'secs' instead of 'seconds'.

I should have added that, but I hadn't, so thanks for pointing this out! If you look above again, you'll see that I added it.

warlordx2 · 2013-04-02 05:04:21

ErnieParke wrote:
awesomeness321 wrote:
Gravitation wrote:

Yeah, EP knows, but technically that's not "stop all sounds".
Well, he should at least mention it.
If you look again, you'll see that I added it. I think that it's nice to know, even though it's not going to be used very often. Also, you could get a lugh or two from it.

but the problem is that

stop all pinks

is'ent a real block! neutral

warlordx2 · 2013-04-02 05:06:49

say [great guide] for (2) secs
stop all

topazdragonlord · 2013-04-02 06:14:12

awesome post really helped a lot smile

GiorgosKarvelas365 · 2013-04-08 04:37:33

stop all pinks
motion on
reset timer
add (volume) to [scratchblocks v]
set tempo to <(HP or (Timer)>
stop all

Scratch

archived forums

#1 2012-11-02 20:52:17

A Guide to Scratchblocks

Code:

#2 2012-11-03 23:20:57

Re: A Guide to Scratchblocks

#3 2012-11-04 09:03:42

Re: A Guide to Scratchblocks

Dazachi wrote:

#4 2012-11-04 14:19:39

Re: A Guide to Scratchblocks

#5 2012-11-04 14:59:22

Re: A Guide to Scratchblocks

Borrego6165 wrote:

#6 2012-11-10 22:25:13

Re: A Guide to Scratchblocks

#7 2012-11-11 09:23:52

Re: A Guide to Scratchblocks

GenChico wrote:

#8 2012-11-11 09:49:14

Re: A Guide to Scratchblocks

#9 2012-11-11 10:00:41

Re: A Guide to Scratchblocks

#10 2012-11-11 10:15:24

Re: A Guide to Scratchblocks

Ideas wrote:

joefarebrother wrote:

#11 2012-11-11 10:33:13

Re: A Guide to Scratchblocks

ErnieParke wrote:

Ideas wrote:

joefarebrother wrote:

Code:

#12 2012-11-11 11:07:24

Re: A Guide to Scratchblocks

awesomeness321 wrote:

ErnieParke wrote:

Ideas wrote:

joefarebrother wrote:

Code:

#13 2012-11-11 11:50:38

Re: A Guide to Scratchblocks

#14 2012-11-11 11:58:23

Re: A Guide to Scratchblocks

Martiscratch wrote:

#15 2012-11-11 12:00:25

Re: A Guide to Scratchblocks

Martiscratch wrote:

#16 2012-11-11 12:09:46

Re: A Guide to Scratchblocks

ErnieParke wrote:

#17 2012-11-11 12:11:52

Re: A Guide to Scratchblocks

awesomeness321 wrote:

ErnieParke wrote:

#18 2012-11-11 12:13:56

Re: A Guide to Scratchblocks

Gravitation wrote:

awesomeness321 wrote:

ErnieParke wrote:

#19 2012-11-11 13:57:31

Re: A Guide to Scratchblocks

awesomeness321 wrote:

Gravitation wrote:

awesomeness321 wrote:

#20 2012-11-12 18:01:51

Re: A Guide to Scratchblocks

#21 2012-11-12 18:38:42

Re: A Guide to Scratchblocks

awesomeness321 wrote:

#22 2013-04-02 05:04:21

Re: A Guide to Scratchblocks

ErnieParke wrote:

awesomeness321 wrote:

Gravitation wrote:

#23 2013-04-02 05:06:49

Re: A Guide to Scratchblocks

#24 2013-04-02 06:14:12

Re: A Guide to Scratchblocks