TheFlamer wrote:

Great guide techno-CAT!

if <mouse down?::operators> then::operators
    
say [Hello!] for (2) secs::operators
end

if <> then
    
else

or otherwise :: control celse

end

if <> then

else

or otherwise :: control celse

end

repeat ()
    
then repeat () :: control celse

end

repeat ()

then repeat () :: control celse

end

ultimateboy144 wrote:

making an extended C Block uses the following example
1.

if <> then
    
else

or otherwise :: control celse

end

if <> then

else

or otherwise :: control celse

end

if <> then

else if <> :: control celse

else
end

[scratchblocks]
if <> then

else if <> :: control celse

else
end
[/scratchblocks]

if() {
} else if() {
} else {
}

Tropic wrote:

ultimateboy144 wrote:

making an extended C Block uses the following example
1.

if <> then
    
else

or otherwise :: control celse

end

if <> then

else

or otherwise :: control celse

end

In some programming languages that would be:

if <> then

else if <> :: control celse

else
end

[scratchblocks]
if <> then

else if <> :: control celse

else
end
[/scratchblocks]

In JavaScript I think it's like this:

if() {
} else if() {
} else {
}

(OMG_time)

when green flag clicked
if <[omg] = [true ]> then    
say [omg!! scratch in commets] for (OMG_time) secs
set [OMG_time v] to [0 ]
end
stop [all v]

when green flag clicked
say [bleep!!!]
move (OMG_time) steps

block :: grey

when green flag clicked
forever
    
if <happy>
repeat ([2^ v] of (53)
say [We love scratch!] for (2) secs
    
end

    
end

((<[MY QUESTION:] = [How do you change the color of a block in BBcode formatting?]>) in this (forum))

((1) + (2) = (0)) (<[5] = [8]> / (0)) ((3) @ (2)) (pick random (1) / (10)) ((say [hi] for (2) secs) + <key [enter] pressed?>

Repeat until (i get an answer)
Ask [How do you create discussions?]

when green flag clicked
say [Hello!] for (2) secs

when green flag clicked
forever
   play sound [forever love, program, share v]until done
end

forever
    love::looks
    program::sensing
    share::sound
end

snaps1 changed not the wrote:

Try this :

when gf clicked :: operators hat
if :: sound cstart
this {block :: sensing ring} is a [ring v]  :: custom-arg cstart
    these :: motion cstart
        amazing {skills :: pen ring} :: extension ring
    are what I call ring partys :: motion cend ring
 < will :: custom reporter> :: custom-arg cring
    teach [scratchers v] :: variables ring
    how to mess this :: sensing stack
because :: custom-arg celse
i love rings! :: sensing ring

Thats A Ring Party! Rings Rings Rings!

quotes!

test wrote:

Into This:

(color=red) R (/color) (color=orange) A (/color) (color=yellow) I (/color) (color=green) N (/color) (color=blue) B (/color) (color=indigo) O (/color) (color=purple) W (/color) wrote:

<–Go's Here——–> (color=red) R (/color) (color=orange) A (/color) (color=yellow) I (/color) (color=green) N (/color) (color=blue) B (/color) (color=indigo) O (/color) (color=purple) W (/color)]

snaps1 wrote:

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 ring} 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 cring
    teach [people v] :: variables stack
    how to do this :: sensing stack
because :: custom-arg celse
    only these {turn cw (20) degrees :: motion ring} :: grey stack
are true tricks :: motion cend
end

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

Hope It Wprks

if <> then

else

or otherwise :: control celse

end

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

when green flag clicked
You Need A Mircophone Like This:

COLORS :: grey hat
pink :: stack
red :: list stack
orange :: variables stack
brown :: events stack
yellow :: control stack
green :: operators stack
teal :: pen stack
cyan :: sensing stack
blue :: motion stack
indigo :: custom-arg stack
purple :: looks stack
magenta :: sound stack

InsaniacGuru77 wrote:

Oh, wait, I'm exploring you're code right now. Yep, I learned it!

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

Tropic wrote:

InsaniacGuru77 wrote:

Oh, wait, I'm exploring you're code right now. Yep, I learned it!

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

Someone else has already made a topic that explains how you do that

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.

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

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

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.

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

end