Scratch

gbear605 wrote:

Well, not quite related to them, but the BBCode help page found here, references the old blocks, and doesn't mention the new system.

I noticed that too. Is there anywhere where we can find out the text that produces the blocks?

Lucario621 wrote:

RedRocker227 wrote:

gbear605 wrote:

Well, not quite related to them, but the BBCode help page found here, references the old blocks, and doesn't mention the new system.

I noticed that too. Is there anywhere where we can find out the text that produces the blocks?

More help on how to use the plugin is available on this wiki page.

Well, the main reason I mentioned what I did, is because it is out of date, and needs to be changed.

I haven't seen any yet but it's really amazing    Nice job!

Is there a list of blocks and their codes somewhere? Cause <abs (-10)> or <touching [sprite v]> don't seem to work and I'm not sure if there are other codes for those blocks.

Jonathanpb wrote:

The blocks are generally typed the way they look in the Scratch program, so um the abs block would be ([abs v] of (10)) :S

Most sensing blocks have a question mark on the end; you have to include those too ^^

if <touching [Sprite1 v]?>
 say ([abs v] of (10))

Ah, okay, thanks!

joefarebrother wrote:

It won't let me make dropdown don't appear in reporters

 (fake reporter [dropdown v])//fake reporter
([slider v] sensor value)//real reporter

<you can do it with [booleans v] which have the same shape>

scimonster wrote:

veggieman001 wrote:

joefarebrother wrote:

It won't let me make dropdown don't appear in reporters

 (fake reporter [dropdown v])//fake reporter
([slider v] sensor value)//real reporter

<you can do it with [booleans v] which have the same shape (for [now v])>

Edited.

Well yeah

Mokat wrote:

The Forever blocks have a hump thingy at the bottom

 forever 
a;lkgj;al
end

Don't put "end" at the end. 

 forever 
a;lkgj;al

sparks wrote:

I've noticed a glitch to do with unrecognise block argument problems in reporters. In the script I drew out in AT, I wanted this:

if  <(connect to internet?) = [true]>
if <not <<contents of file at url [accidentalgames.com/ping.php?ping=test]> = [1]>>//returns 1 for a success
set [connect to internet v] to [false]
end
end

Contents of file at url [] being a Panther reporter block. However, I ended up having to enter it into the scratchblocks code as a boolean in order for the string argument to appear as an argument not as text. Entered as a reporter it looks like this:

if  <(connect to internet?) = [true]>
if <not <(contents of file at url [accidentalgames.com/ping.php?ping=test]) = [1]>>//returns 1 for a success
set [connect to internet v] to [false]
end
end

since

(contents of file at url [accidentalgames.com/ping.php?ping=test])

as a reporter has the same problem, I decided the problem wasn't to do with nesting as I first thought when I began this post. More likely, arguments are not accepted in reporters that are not listed by the script whilst booleans will accept strings whilst obsolete.

However, you're probably not too interested in supporting blocks correctly that aren't in Scratch, which is a shame, since Panther and BYOB are used a lot, but understandable. Nevertheless, this is a glitch I found, now you know!

The rendering machine basically picks up any reporter that doesn't match the block library as a variable.
So this isn't really a bug.  It's actually intended.
(And as for how I know this, the wiki got the block plugin before the forums, so I've had time to play around with it in my sandbox)

mattlai2 wrote:

Mokat wrote:

The Forever blocks have a hump thingy at the bottom

 forever 
a;lkgj;al
end

Don't put "end" at the end. 

 forever 
a;lkgj;al

testing:

 
forever
'alkjaluih894

joletole wrote:

Why is the if button messed up.

if [ ]
   practice script
end

Use <>:

if < >
   practice script
end

turkey3 wrote:

Greenatic wrote:

joletole wrote:

Why is the if button messed up.

if [ ]
   practice script
end

Use <>:

if < >
   practice script
end

That appears to mess up for me too.