theonlygusti wrote:

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?

For the suggestions forums?
For their signatures?

Don't title your post tricks if it doesn't contain any.

When {Wow a hat block in a hat block with an (input::operators)::hat control} clicked::hat events

customize block colors::#66ff99//and add comments

cat_tap wrote:

theonlygusti wrote:

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?

For the suggestions forums?
For their signatures?

Don't title your post tricks if it doesn't contain any.

Yeah, I was kinda hoping to learn how to make something like this:

When {Wow a hat block in a hat block with an (input::operators)::hat control} clicked::hat events

Or to learn how to

customize block colors::#66ff99//and add comments

You should really add these. So… Please do!

Hearst10 wrote:

please delete the part where it says “due to technlogical limits, boolean blocks look like reporter blocks” since it is fixed now.

Im acually a red block :: grey

hi { hi :: hat
}

Techno-CAT wrote:

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)

Chiroyce wrote:

Techno-CAT wrote:

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)

Someone please explain how this works.

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

wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat
is this too much? :: motion stack

issac_the_scratcher wrote:

wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {wow {} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat} :: events hat
is this too much? :: motion stack

whitelily1196 wrote:

InsaniacGuru77 wrote:

excelguru wrote:

Blocks new to BYOB 3.0:

run ({} @addInput) :: control // runs the blocks in it

launch ({} @addInput) :: control // runs the blocks in it simultaneously to the script
call (() @addInput) :: 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 ({} @addInput)::operators) // 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 (a) @addInput :: grey // this block creates variables that can only be used in the script. It is a variable block, but it is gray.

(list [] @delInput @addInput :: 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 // 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

Cloneable wrote:

whitelily1196 wrote:

InsaniacGuru77 wrote:

excelguru wrote:

Blocks new to BYOB 3.0:

run ({} @addInput) :: control // runs the blocks in it

launch ({} @addInput) :: control // runs the blocks in it simultaneously to the script
call (() @addInput) :: 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 ({} @addInput)::operators) // 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 (a) @addInput :: grey // this block creates variables that can only be used in the script. It is a variable block, but it is gray.

(list [] @delInput @addInput :: 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 // 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 [ v] :: events boolean>

end

Just like Snap!

({}::ring)

({}::ring)

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

define report [report] :: reporter
report (report) :: custom cap

when green flag clicked : :  operators
oh my god : :  operators

when green flag clicked
make ({Its over 9000!!!!!!!!!!}: :ring)