Scratch

when green flag clicked
think [Argh, this is so addicting!] for [2] secs
realise [Hey! I can make BYOB blocks now!]
post [Trolololol v]

RedRocker227_Test wrote:

joefarebrother wrote:

RedRocker227 wrote:

when green flag clicked
think [Argh, this is so addicting!] for (2) secs
realise [Hey! I can make BYOB blocks now!]
post [Trolololol v]

think [Yay! I can make BYOB blocks!] for (10) mins
wait (1) secs
realise [But what about list and script inputs? And colour?]
think [Maybe they should modify it to support that stuff?]

then I receive [joefarebrother's post v]
think [Hm... You've got a point there.] for [3] secs

Don't forget to close your tags or it gets messed up. 

Greenatic wrote:

Lucario621 wrote:

Greenatic wrote:

Would it be possible to add another one, but that allows you to define the parameters?  (i.e. [customblocks]"'blockspec' in 'category'"[/customblocks] )  That would allow us to bring back the Block Library to those who don't install the Antidote...

This is an idea that we considered during development. However, we did not proceed as we felt it would take too much of our resources to add, for a feature that only a small section of the forum and wiki articles would use.

I don't see how it would be too difficult.  All you have to do is tell it to set the color based on 'category', and parse the blockspec just like it already does.

 <See? [It] (already) [parses  v] blockspecs!> 

B.U.M.R. (Bring Up My Reply    )

Well spotted, Mokat    It's not really a problem, but it'd still be better if it was fixed.

Wow cool but last time when I was posting i made a script mistake then it turned into a fake block!

why fake block?
if post has [fake block v]
delete [fake block v]

Last edited by fetchydog567 (2012-02-01 03:42:20)

Okay, I can't seem to get an OR boolean to work with a pair of ">" comparisons on either side of it:

when gf clicked
repeat until <<(X) > (0)> or <(Y) > (0)>>
change (i) by (1)
end

This is what it makes:

when gf clicked
repeat until <<(X) > (0)> or <(Y) > (0)>>
change (i) by (1)
end

when gf clicked
repeat until <<(X) > (0)> or <(Y) = (0)>>
change (i) by (1)
end

Paddle2See wrote:

Okay, I can't seem to get an OR boolean to work with a pair of ">" comparisons on either side of it:

when gf clicked
repeat until <<(X) > (0)> or <(Y) > (0)>>
change (i) by (1)
end

This is what it makes:

when gf clicked
repeat until <<(X) > (0)> or <(Y) > (0)>>
change (i) by (1)
end

It seems to be the second > operator that is messing it up.  You can prove that by turning it into an = operator, which gives you this...

when gf clicked
repeat until <<(X) > (0)> or <(Y) = (0)>>
change (i) by (1)
end

...which is much happier.  Can anybody see what I am doing wrong here?  Or is it a bug?

Well I think the first error is because you forgot the [ block ] tags on the first one.

think [This is awesomeness!!!] for (all the users reading this!) secs //yay awesome

Last edited by tlangster (2012-02-01 18:46:22)

RedRocker227 wrote:

Paddle2See wrote:

By the way...since I'm not a big fan of trying to remember formats, I've built a ScratchBlock generating project over here

http://scratch.mit.edu/projects/Paddle2See/2307441

that you can play with.  Just remember, it needs to be downloaded if you are going to use it for real, because you can't export a list to a text file when it's running online.  Have fun and feel free to improve 

Wow, that's awesome 

Thanks!  I've made several improvements to it today.  Menu items now prompt you with a label.  There are also some prompts to help you figure out what your options are...but they are kind of annoying and may go away, or become optional.

Hmm, the blocks are square shaped, not smooth at the edges

rabbit1131 wrote:

How do I insert a variable into a switch to costume block?

switch to costume (Variable)

switch to costume (Variable)

8)