Scratch

You cant say your a Pro Scratcher because you dont become a professional unless you get paid to do it! But other than that i like how you are offering to help ppl!   Have A Great Holiday With Your Family

Thank You! Sorry If I sounded rude i did not mean it like that! I always said i was a pro at stuff and my dad said well ur only a pro if u get paid to do it! lol But yes u are an amazing scratcher 

Same! i hate ( most of the time ) doing big projects because there are so many scripts and when u mess up on something you have to find the script with the mistake and my mind goes crazy!

yeah because when i broadcast im reciveing im like, "oh shoot! whitch on is it!" since i have so many broadcasts! 

Giving broadcasts and variables meaningful names (like "start scene 3" or "hide enemy2") helps a lot in subsequent debugging.  I think it is a major flaw of the Scratch user interface that you can't easily change the names of variables or messages, since further development on a project often changes exactly what a message does.

OK ..... how do you broadcast & receive values within a topic ?

Say sprite_1 sends "move_x", value 50 ?   
Later (from same sprite) a different event "turn_left" 30 degrees ?

With v1.2.1 you can now look at the variables (including previously hidden state variables, like costume#) of other sprites.  This opens up a new mechanism for passing parameters: setting your own variable, then sending a message so that other sprites will look at your variables.    Sometimes this is easier than using global variables, as you don't need to make copies of values, but it still is not as clean as passing parameters explicitly.  That will probably come when the Scratch Team figures out how to do "make-your-own-block".

So instead of passing arguments, we are signaling "come and fetch 'em".  Kind of homey!  Still awkward.

oh yeah and the post that got "moderated?" was soppused to have varibles and an equel.

Heybrian,

Sorry about deleting your other post.  There are a lot of posts each day that are just random collections of blocks (probably from kids playing with the buttons on the webpage), and if a message seems completely incoherent, I delete it.

It helps when using the blocks to remember remember to say [ blocks ] and [ /blocks ] around the code and to use  return (or enter) keys between lines.

repeat until costume# = 4
    next costume

should work just fine, as long as you have at least 4 costumes.  (I just tried it and it worked fine.)  The "costume" value will always be an integer from 1 to the number of costumes.

That should work , but it doesn't sound like it would do much different from
    switch to costume 4
(unless you also have a wait in the repeat loop).
Perhaps you need to display the costume# and see what it is. 

Perhaps you accidentally deleted a costume and there are only 3 now?

If you can't get it working, post it on the web site and ask others to look at it—you may be omitting the description of something essential.

How do you get a longer background.