Final Project

http://scratch.mit.edu/projects/23804977/

I started out by finding sprites that fit my theme but since I couldn't find any, I made my own.  I wanted to make a "home" screen so I decided to make a sprite that when you clicked it, it took you to the game part.  I wanted to make each level more difficult so I thought a great way to do that is start with a small amount of keys that you could click first (space and ones like that) then made it harder by giving more options for keys (like the whole alphabet).  The biggest problem I ran into was the fact that my computer crashed at the end of class today and I lost everything.  I also had an issue with not being able to get the score to increase on some sprites although it would on others.  I tested this by playing the whole game through a few times.  It worked perfectly so I hope you like my game!

***you told me I could do this at my house since it crashed so that is why I'm posting it now!***

Purpose of My Game.

  For my final project on Scratch, I decided to do a game involving bees.  Once you score 20 points, you will move onto the next level.  In the first level, you need to press the right key to get the flower, (space, right key, left key, up key or down key).  In the second round, you need to press the right number key to earn a point (0-9).  In the third level, you need to pick the right key in the alphabet to score a point (a-z).

Scoring

A variable is a way to change a certain number every time something happens. A great example of this is scoring. Everytime a fish is caught in this game, the variable increases by one.

Try it

http://scratch.mit.edu/projects/23530023/

The three puzzles I put in this project were; when you press B the sprite gets bigger and when you press S the sprite gets smaller, when the sprite touches something blue, it plays a high note and when it touches something red it plays a low note and when you move the mouse pointer the sprite follows but never touches.  When working on these, I found it really important to use the sensing blocks.  These triggered the action whenever it needed to happen.  These can be really helpful for my game since I can use sensing blocks if I want to win or lose.  The one with the sounds when I touch a color can be really helpful for the game.

Debug It Reflection

1) A lot of the debugging programs this time had to do with the broadcast and receive buttons.  Usually if something wouldn't move, it probably needed to be broadcasted to the other sprite.
2) When debugging, the most important thing to do is see where the problem actually is in the program.  Once you find it, you need to find the right block that can fix it.

Debug It 2.5

http://scratch.mit.edu/projects/23508097/

Debug It 2.4

http://scratch.mit.edu/projects/23507730/

Debug It 2.3

http://scratch.mit.edu/projects/23507490/

Debug It 2.2

http://scratch.mit.edu/projects/23504816/

Debug It 2.1

http://scratch.mit.edu/projects/23503998/

Background Reflection

1)  The stages use a similar technique to the sprites broadcasting.  Once one thing switches the program knows when to have the next person talk or the next movement.
2) You put them in the location that would be correct-looking before the scene changes.  They know to start talking when you use the "When backdrop switches" button.
3) You can use scene changes when you are making a game.

Background Switch

http://scratch.mit.edu/projects/23402526/

Broadcasting

1) Broadcast is an easy way to get two sprites to converse without having to use a ton of wait buttons.  It makes it less confusing and smoother.
2) I would use timing when two sprites are simply talking without an interruptions.  It would be clear how long each wait would be since you know how long someone is speaking.  I would use broadcast when more things are happening, like costume changes and background changes.  These types of blocks don't say how long they are so it would just be more simple to use the broadcast.

Make a Block

1) Make a block is really useful when you want to save room.   Instead of having a ton of blocks, there is only one.  You can make it do whatever you want.
2) I will use it when I need to make my sprite do something that is repeating often.  Instead of writing the program over and over again, I can use one block as many times as I need.

Debug It Reflection

1) One strategy I used was using more than one Start signal when things needed to go at the same time. This helped a lot on the last one.
2) I would help people by giving them a clear objective of what they needed and do one block at a time.

Debug It 1.5