Scratch

ScratchReallyROCKS wrote:

Kingdaro wrote:

Then please explain to me why no clones are created on green flag click. (when I put "clone me" under "when green flag clicked") The clone should show, according to this script.

Actually it does work, it just stacks them on top of each other which makes it look like nothing happened

What do you mean? In the sprites' panel, or the project window? Seems like you're saying both to me, judging by my results. So why aren't they showing? Is there something wrong with my script? (Besides the "if not a clone: delete" that was a mistake I corrected.

ScratchReallyROCKS wrote:

Kingdaro wrote:

What do you mean? In the sprites' panel, or the project window? Seems like you're saying both to me, judging by my results. So why aren't they showing? Is there something wrong with my script? (Besides the "if not a clone: delete" that was a mistake I corrected.

Sorry, I must not have been clear enough, I meant that in the actual viewer, all the clones are in front of the real sprite. It's like stacking 2 identical pieces of paper on top of one another, you can't see the bottom one.

Oh and the clones won't show up in the sprite panel because they are not actual sprites, just clones. They have the same scripts in them as the real one

Then why, again I ask, do the clones not show up, when in the script, it asks if it is a clone, and if it is, it will SHOW.

Kingdaro wrote:

ScratchReallyROCKS wrote:

Kingdaro wrote:

What do you mean? In the sprites' panel, or the project window? Seems like you're saying both to me, judging by my results. So why aren't they showing? Is there something wrong with my script? (Besides the "if not a clone: delete" that was a mistake I corrected.

Sorry, I must not have been clear enough, I meant that in the actual viewer, all the clones are in front of the real sprite. It's like stacking 2 identical pieces of paper on top of one another, you can't see the bottom one.

Oh and the clones won't show up in the sprite panel because they are not actual sprites, just clones. They have the same scripts in them as the real one

Then why, again I ask, do the clones not show up, when in the script, it asks if it is a clone, and if it is, it will SHOW.

They have the exact same costume and are in the exact same place; therefore you cannot tell the difference.

nXIII wrote:

Kingdaro wrote:

ScratchReallyROCKS wrote:

Sorry, I must not have been clear enough, I meant that in the actual viewer, all the clones are in front of the real sprite. It's like stacking 2 identical pieces of paper on top of one another, you can't see the bottom one.

Oh and the clones won't show up in the sprite panel because they are not actual sprites, just clones. They have the same scripts in them as the real one

Then why, again I ask, do the clones not show up, when in the script, it asks if it is a clone, and if it is, it will SHOW.

They have the exact same costume and are in the exact same place; therefore you cannot tell the difference.

Oh hold on, I found the solution. Thanks. Sorry for causing any trouble, carry on. :3

Sperry wrote:

Jonathanpb wrote:

Just got Panther!    But a lot of the new blocks don't work (the <[ ] received?> doesn't work!  ), and when I tried to show a new block's Stage Monitor, I got one of those Squeak error messages. >_< Does this happen to anyone else?

w00T    Someone else got Panther!

1) The <I recieve []> does work, do this:
When =/ clicked
broadcast something


When I receive something
wait (5)

PUT HAT HERE
wait until something is recieved
DO SOMETHING HERE


After the 'when I receive ___" script is done, it reports false, that's what wait 5 is for.

2) A lot of people complain about that, we are working on fixing that right now!

Hmmm... I took the [wait until < >] block and put the <[ ] received> block in it (with a specified broadcast), and then activated my script - when I tried broadcasting the broadcast, the script didn't stop! 
EDIT: Oh, now I see what's going on... I'm using it for the wrong purpose. ^_^

At your second point - YES YES YES YES YES

Panther is awesome! 

Last edited by Jonathanpb (2010-05-18 18:52:18)

ScratchReallyROCKS wrote:

Is it possible to make booleans or reporters in CYOB, or can you only make command blocks?

Change the block type (small top-right textbox)
r for reporter
b for boolean
_________________

I accidentally killed my download counter >.>
If you downloaded it recently you have not been counted 

Last edited by nXIII (2010-05-18 19:39:07)

ScratchReallyROCKS wrote:

nXIII wrote:

ScratchReallyROCKS wrote:

Is it possible to make booleans or reporters in CYOB, or can you only make command blocks?

Change the block type (small top-right textbox)
r for reporter
b for boolean

Oh THAT'S what that's for

I downloaded it yesterday.

EDIT: can you make hats?

No, I'm afraid you can't.

EDIT: Although, in some later version (when I have more time over the summer) I am redesigning the hat-block system entirely; you will be able to trigger the same script  from multiple events, be able to name scripts (and access them once they are named), and possible even be able to take arguments (although this is a bit harder and starting to run into BYOB)

Last edited by nXIII (2010-05-18 20:08:49)

nXIII wrote:

be able to name scripts (and access them once they are named), and possible even be able to take arguments (although this is a bit harder and starting to run into BYOB)

Don't reinvent BYOB, just steal the code!  (Then I can start bugging you all the time instead of Jens.    )

bharvey wrote:

nXIII wrote:

be able to name scripts (and access them once they are named), and possible even be able to take arguments (although this is a bit harder and starting to run into BYOB)

Don't reinvent BYOB, just steal the code!  (Then I can start bugging you all the time instead of Jens.    )

Teehee... no, this isn't really BYOB, more an extension of hat blocks, but yes, the difference is subtle. I guess I might steal (with credit, of course) some code for reporting values and such, but I do like my idea that you (might) have seen with the event blocks.

bharvey wrote:

nXIII wrote:

All clones are deleted when the green flag or the stop all button is pressed.

Oh!  I didn't understand that.  What's your model about how clones are used?  I keep thinking about the bricks in a Breakout game, and you'd want those to be persistent, at least I would.  (I want to see them on the stage between games.)

Hm... well, clones are kind of temporary copies of sprites, they follow their original's scripts and have their own hat block fired when they are created. I guess there could be an option in the settings about permanent vs. temporary clones; the problem with permanent: how do you know if you should make the hundred-or-so clones of bricks if they stay there after the game is over?

Last edited by nXIII (2010-05-18 21:37:50)

nXIII wrote:

Teehee... no, this isn't really BYOB, more an extension of hat blocks, but yes, the difference is subtle. I guess I might steal (with credit, of course) some code for reporting values and such, but I do like my idea that you (might) have seen with the event blocks.

It's not just reporting values; it's first class scripts.  If you have named hat blocks (I mean, named specific hat blocks, not named categories like WHEN <foo> CLICKED), then basically they're procedures, and semantically equivalent to an unnamed hat block followed by a (named) custom command block that runs the script.  So, even if you want to use a different notation, I think you're pulling at the end of a long string that we've already unravelled for you.

(And my latest fiendish plan for taking over the world is to get BYOB into everyone's mod, starting of course with our chief competition.    )

nXIII wrote:

the problem with permanent: how do you know if you should make the hundred-or-so clones of bricks if they stay there after the game is over?

Oh, you don't make them on green flag clicked; you make them on I (for Initialize) clicked, which says to delete all clones, and create fresh ones.  Or maybe you make it control-meta-shift-I so the users don't do it by accident.     And then they do stay around after the game is over, ready for the next game.

Hey, how about implementing a spot where you can build your own blocks? You'd completely pwn BYOB! 

iCode-747 wrote:

Jonathanpb wrote:

Hey, how about implementing a spot where you can build your own blocks? You'd completely pwn BYOB! 

They did... right?

I didn't see it...