YubNubEwok wrote:

aceacerockscool wrote:

repeat <forever>
say (this is amazing)
end

aceacerockscool wrote:

<either [] or []>

I always wanted it...

aceacerockscool wrote:

when I receive [boredom v]
broadcast [I'm bored!!! v] and wait
if <really bored = [true v]?> then
do {
start [scratch v]
turn [life v] around
set [looks v] to [cool]
be yourself
define change
} in life

aceacerockscool wrote:

({
  })

aceacerockscool wrote:

add variable [var]
delete variable [var]
add list [list]
delete list [list]
<var [] exists?>
<list [] exists?>
report the script {
} with inputs (#1) (#2)[-> v]

(removed by moderator - your username is too long) wrote:

(removed by moderator - please don't spam or necropost)

• please
  use
  only
  numbers
  for
  lists
  

(removed by moderator - your username is too long) wrote:

[ pi v] = ( 3. ) :: sound hat
( ( 1 v) :: motion stack ) ( 4 @greenFlag :: hat events ) ((  1 v):: motion stack ) ( [ 5 v] :: cap control ) ( ( 9 ) :: variables ) ( [2] :: looks stack ) ( [ 6 v] :: sensing  boolean ) ( [ 5 v] :: cap control ) ( ( 3 - hit-hat v) :: sound stack loop ) ( [ 5 v] :: cap control ) {
( 8 [#888888] :: pen stack ) ( ( 9 ) :: variables ) ( <> 7 <> :: operators boolean ) ( ( 9 ) :: variables ) ( ( 3 - hit-hat v) :: sound stack loop ) ( [2] :: looks stack ) ( ( 3 - hit-hat v) :: sound stack loop ) ( 8 [#888888] :: pen stack ) ( 4 @greenFlag :: hat events ) ( [ 6 v] :: sensing boolean ) :: grey loop
} ( [2] :: looks stack ) ( [6 v] :: sensing boolean ) ( 4 @greenFlag :: hat events ) ( ( 3 - hit-hat v) :: sound stack loop ) ( ( 3 - hit-hat v) :: sound stack loop ) ( 8 [#888888] :: pen stack ) ( ( 3 - hit-hat v) :: sound stack loop ) ( [2] :: looks stack ) ( <> 7 <> :: operators boolean ) ( (9) :: variables ) {
( [ 5 v] :: cap control ) ( [ 0 v] :: list ) ( [2] :: looks stack ) ( 8 [#888888] :: pen stack ) ( 8 [#888888] :: pen stack ) ( 4 @greenFlag :: hat events ) ( ( 1 v) :: motion stack ) ( ( 9 ) :: variables ) ( <>7<> :: operators boolean ) ( ( 1 v) :: motion stack ) :: extension loop
} ( [ 6 v] :: sensing boolean ) ( (9) :: variables ) ( ( 3 - hit-hat v) :: sound stack loop ) ( ( 9 ) :: variables ) ( ( 9 ) :: variables ) ( ( 3 - hit-hat v) :: sound stack loop ) ( <>7<> :: operators boolean ) ( [ 5 v] :: cap control ) ( ( 1 v) :: motion stack ) ( [0 v] :: list ) :: custom-arg cap loop

Original version

YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEET

Techno-CAT wrote:

Hello there!

Have any of you found it confusing to use the Scratchblocks plugin on the forums? Today I'll be explaining how to make them step-by-step in this easy to understand guide.

For more info, see the wiki.
If you want to test any of this out, please see here instead
—————————————————————————————————————

Reporter
Reporter blocks can be made using:

[scratchblocks]
(input)
[/scratchblocks]

For example:

(input)

Boolean
Boolean blocks are similar to reporter blocks, however they use <'s and >'s instead of ('s and )'s.

[scratchblocks]
<input>
[/scratchblocks]

For example:

<mouse down?>

Due to technological limits, boolean blocks look like reporter blocks.

Stack Blocks
Stack blocks can be formed by the following script:

[scratchblocks]
input
[/scratchblocks]

For example:

input

But what if it has a dropdown menu, number entry or string thread?

Well, we do this instead

[scratchblocks]
choose [input v]
[/scratchblocks]

Which will turn out to be

choose [input v]

For number entries, do

[scratchblocks]
input ( )
[/scratchblocks]

C block
C blocks must be closed by typing “end” after the last stack block inside it.

[scratchblocks]
repeat (10)

end
[/scratchblocks]

If there is no number input, leave out the ()'s
which makes:

repeat (10)
    
end

That's great! We now know the basics of the ScratchBlocks plugin.
But how does it all piece together?

Well, just piece together the blocks like this:

[scratchblocks]

when green flag clicked
if <mouse down?> then
    
play drum (3 v) for (0.2) beats
end

[/scratchblocks]

Which will turn out to look like this:

when green flag clicked
if <mouse down?> then
    
play drum (3 v) for (0.2) beats
end

—————————————————————————————————————
Other BBCode (BulletinBoardCode) help
—————————————————————————————————————

Have you ever seen Colour Text but not known how to do it? Well, enter the following code:

[color=red]yourtext[/color]

Have you also wanted some coding show up? Then do this:

[code]
[scratchblocks]
yourtext
[/scratchblocks
[/code]

There's some other stuff you ought to know too!

Here's a way to generate a big pile of scratchblocks if you already have the code created as a project.

* Shift-click the File menu and save project summary.
* Open the project summary and copy all the text.
* Paste it in between { scratchblocks } tags.
* Delete the parts you don't want.

(As suggested by Noumenon72)

Well, that hopefully sums it all up

Techno-CAT

when green flag clicked
if <helpful> then
forever
say [THANK YOU!!!!!!]
end
end

C stack{
hat::grey hat
}::grey stack

When gf clicked::pen

Say [hello]::motion

Techno-CAT wrote:

Paddle2See wrote:

Nice guide! Is there any way to make it so that the square brackets are shown so people get less confused? I think if you put code tags around your markup, you might be able to do it

[scratchblocks]


[/scratchblocks]

Yep! It works

There we go! It's all complete
I've also added some other BBcode tricks

<[((10) + (10))] = [20]>

Mandalorian1001 wrote:

when green flag clicked
if <helpful> then
forever
say [THANK YOU!!!!!!]
end
end

theonlygusti wrote:

You can aslo do this:

[[]scratchblocks]
[[]/scratchblocks]

To show the square brackets. It looks like:

[scratchblocks]
[/scratchblocks]

And this guide isn't really about tricks, I'd say learning how to do this:

when gf clicked :: operators hat
if :: sound cstart
this {block :: sensing stack} is a [block v] :: custom-arg cstart
    these :: motion cstart
        amazing {skills :: pen hat} :: extension stack
    are what I call tricks :: motion cend cap
and <you should :: custom reporter> :: custom-arg celse
    teach [people v] :: variables stack
    how to do this :: sensing stack
because :: custom-arg celse
    only these {turn cw (20) degrees :: motion hat} :: grey stack
are true tricks :: motion cend
end

is all that qualifies as [scratchblocks] “tricks”, the rest is self explanatory.

if <> then {when green flag clicked} :: control

if <> then {(x position)} :: control

broadcast [] []

broadcast []

stop [all v] :: hat
{
say [Hi!]
play sound [meow v]
next costume
} forever :: control
when gf clicked :: cap

peng64 wrote:

This isn't a bad guide, but I'd like to know how to force a color of a certain block so

broadcast [] []

can look like

broadcast []

but with two strings instead of one.

// motion
move () steps

turn cw () degrees

turn ccw () degrees

point in direction ( v)

point towards [ v]

go to x: (0) y: (0)

go to [ v]

glide () secs to x: (0) y: (0)

change x by ()

set x to ()

change y by ()

set y to ()

if on edge, bounce

set rotation style [ v]

(y position)
(x position)
(direction)

// looks
say [] for (2) secs

say []

think [] for (2) secs

think []

show

hide