When <[applepie2] = [awesome]> ::sensing hat
Do until <not <[applepie2] = [awesome]>> ::extension cstart
set [applepie2 v]'s status to (pick random [awesome] to [SUPER AWESOME]) ::list
when this is over ::celse
fix scratch's block bugs ::sound
then ::celse
use [applepie2's awesomeness v] ::motion cstart
to [eat pie v] ::control
end
after that, ::celse
travel in time {till im awesome <and ::custom> stop traveling ::motion hat} ::variables
end
set [applepie2 v]'s status to [Hungry] ::list
eat more (waffles::custom) until {I shouldn't anymore::operators} then ::pen cstart
eat (pancakes::custom) for (999999) seconds::looks
then ::celse
i'm probably not [awesome v] anymore ::sensing
so, ::celse
travel in time, with effect {Rotate (15) degrees [counter clock wise v] every (0.5) seconds::motion hat} ::variables
and eat [more waffles v] on the way ::control
end
set [applepie2 v]'s status to [Exited] ::list
act [exited v] for (Until i'm bored ::operators) seconds ::motion cstart
jump [up v] and [down v] until {When <[applepie2] = [doesn't want to]>::sensing hat} ::events
next, ::celse
set pen color to [#3333FF]
and ::operators
dance [all over the place v] for (60) seconds ::looks
now ::celse
[applepie2] = [bored] ::operators
end
set [applepie2 v]'s status to [talkative] ::list
wile <i'm talkative ::operators>, do ::sound cstart
say {stuff{and{stuff{and{when i'm bored, move on ::control hat}::hat}::control hat}::hat}::control hat} ::custom
to doing ::celse
eating [waffles v] ::sensing
play sound {scratching waffles ::control hat} until [I ate my waffles v] ::list
Now I will wait until <(timer) > (Waffles ::extension)> ::celse
and then {eat [waffles v] for (20) seconds:: events} ::pen
end
set [applepie2 v]'s status to [king] ::list
Demand more [waffles v] for (Infinity ::looks) seconds, and then ::cstart
Demand more [pancakes v] for (Infinity ::looks) seconds, and then ::control cstart
Demand more [waffles v] for (Infinity ::looks) seconds, and then ::operators cstart
Demand more [pancakes v] for (Infinity ::looks) seconds, and then ::sensing cstart
Demand more [waffles v] for (Infinity ::looks) seconds, and then ::looks cstart
Demand more [pancakes v] for (Infinity ::looks) seconds, and then ::custom cstart
get fired (((((((())))))))------------------(((((((()))))))) ::extension
and ::custom
end
and ::looks
end
and ::sensing
end
and ::operators
end
and ::control
end
and
end
stop [everything in the universe v]

{why does this page not teach to do this? :: Looks hat} :: grey ring

InsaniacGuru77 wrote:

excelguru wrote:

Blocks new to BYOB 3.0:

run {:: grey cap} ► :: control // runs the blocks in it

launch {:: grey cap} ► :: control // runs the blocks in it simultaneously to the script
call {:: grey cap} ► :: control reporter // allows the user to call a variable that is a reporter
report [] :: control cap // for custom reporters and Booleans, it tells what to report
stop block :: control cap // stops a custom block without reporting anything
debug :: control // an experimental block
debug () :: control reporter // ''
true :: operators boolean // reports true
false :: operators boolean // reports false
ascii code of [] :: operators reporter // reports the ascii code of a character
ascii () as letter :: operators reporter // reports the character for an ascii code
is [] a [number v] ? :: operators boolean // dropdown also contains text, boolean, list, command, reporter, and predicate; reports whether the input is of that
// data type (yes, BYOB has more data types than scratch)
the script ► :: operators cstart // returns the script inside. It is supposed to be a hybrid c-reporter thing, but scratchblocks doesn't support that type of block.
the () block :: operators reporter // works like [the script] but with a reporter/predicate block.
script variables ()► :: grey // this block creates variables that can only be used in the script. It is a variable block, but it is gray.

list [] ◄► :: list // it reports a list with that name.
[ v] as text :: list reporter // in BYOB, lists do not normally report as text, but as list monitors do. This converts a list to text. 
copy of () :: list reporter // if a variable is set to a list, it updates with the list. Here is how to avoid that.

Blocks new to BYOB 3.1:

object [ v] :: sensing reporter // reports a sprite, a list of all sprites, or the stage
attribute [ v] :: sensing reporter // reports an attribute of the sprite
[ v] of [ v] :: sensing reporter // now you can drag any sprite to the right and any sprite to the left
clone :: operators reporter // reports a clone of the sprite
is [] a [ v] :: operators boolean // now has object in the menu of types
delete [ v] :: operators // deletes the object, attribute, or variable

Blocks new to snap 4.0

warp :: grey cstart // it is a control block, but it is gray. It runs everything in it at once

Some of the blocks seem meaningless, but that is because of BYOB's expanded data types.

I've always wanted a block that says,

repeat until <I receive [] :: events boolean>

end

Techno-CAT wrote:

theonlygusti wrote:

-snip-
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] the rest is self explanatory.

Yes, but what point is it teaching people how to do blocks that Scratch doesn't even support?

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

run {{}►::grey ring} ►::control
launch {{}►::grey ring} ►::control
(call (()►::grey ring) ►::control)
report []::control cap
stop block::control cap
debug::control
(debug []::control)
<true::operators>
<false::operators>
(ascii code of [a]::operators)
(ascii (65) as letter::operators)
<is [5] a [number v]?::operators>
(the script ►::operators cstart)
(the (()►::grey ring) block ►::operators)
script variables ((a)::grey) ► ::grey
(list [] ◄►::list)
([ v] as text::list)
(copy of [ v]::list)

(object [ v]::sensing)
(attribute [ v]::sensing)
(clone::operators)
delete (()►::grey ring)::variables

fill::pen
(message::control)
warp::grey cstart
end
create a clone of [ v]::control
delete this clone
when I start as a clone
run {{}►::grey ring} w/continuation::control
(call {{}►::grey ring} w/continuation::control)
(http://[snap.berkeley.edu]::sensing)
<turbo mode?::sensing>
set turbo mode to <>::sensing
(current [date v])
{{}►::grey ring}
(()►::grey ring)
<<>►::grey ring>
(Unicode of []::operators)
(Unicode () as letter::operators)
<Is [] identical to []?::operators>
([] in front of [ v]::list)
(all but first of [ v]::list)
(item (1 v) of [ v])

gengar16 wrote:

Just testing a spoiler.

SPOILER: Swimmingbird is not a bird!

Edit: Just ‘select’ the invisible text!

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 gf clicked
repeat (1)
    
else

end

when gf clicked
repeat (1)
    
else

end

when gf clicked
repeat (1)
     move (<mouse down?> + <mouse down?>) steps
else
say (join [(this is a )] [world of minecraft]) for (pick random (1) to (10)) secs
end

when gf clicked
repeat (1)
     move (<mouse down?> + <mouse down?>) steps
else
say (join [(this is a )] [world of minecraft]) for (pick random (1) to (10)) secs
else
summon [Wolf v]f at x: (x) y: (y) z: (z) attributes:(Owner:(username)CollarColor:(blue(white(lightblue))))
spawn :: control cstart
creeper 
end

when gf clicked
repeat (1)
     move (<mouse down?> + <mouse down?>) steps
else
say (join [(this is a )] [world of minecraft]) for (pick random (1) to (10)) secs
else
summon [Wolf v]f at x: (x) y: (y) z: (z) attributes:(Owner:(username)CollarColor:(blue(white(lightblue(t(e(s(t))))))))
spawn :: control cstart
creeper 
end

When gf clicked
repeat (10)
repeat (10)
repeat (10)
repeat (10)
repeat (10)
end
end
end
end
end

when I hide :: looks hat

when [sprite1 v] hides
say [Hihi! You wont find me!] until <[sprite1 v] was found>
say [aww, can you define sadness] for (2) secs

MinePlayersPE wrote:

when [sprite1 v] hides
say [Hihi! You wont find me!] until <[sprite1 v] was found>
say [aww, can you define sadness] for (2) secs

cristobal_Scratch wrote:

when I hide :: looks hat

cristobal_Scratch wrote:

testing a little see down
IIIIIIIII
vvvvv

When gf clicked
repeat (10)
repeat (10)
repeat (10)
repeat (10)
repeat (10)
end
end
end
end
end

cristobal_Scratch wrote:

testing a little see down
IIIIIIIII
vvvvv

when gf clicked
repeat (1)
     move (<mouse down?> + <mouse down?>) steps
else
say (join [(this is a )] [world of minecraft]) for (pick random (1) to (10)) secs
else
summon [Wolf v]f at x: (x) y: (y) z: (z) attributes:(Owner:(username)CollarColor:(blue(white(lightblue(t(e(s(t))))))))
spawn :: control cstart
creeper 
end