Wednesday, June 18, 2014

Final Project Parts 2+3

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

When I started, I picked the sprites I would use and I also looked at the original blocks to see how they would fit into what I was doing. If I came across a problem, I would look to see if any of my instructions conflicted, causing the program to not work. This was usually the problem and it was a fairly easy fix. I just had to get rid of the conflict somehow. I would test it out by trying it every time I added something new to the game.On occasion the computer would glitch and a certain step wouldn't work one time, but it would work every other time I tried it. So, testing multiple times was important to my process.

Tuesday, June 17, 2014

Final Project Part 1

The purpose of this project is  to remix an already created project. I'm planning on changing the big fish into a dragon and having the dragon eat another sprite, but it has to stay away from the wizards. Every time the dragon eats a sprite he gains a point. Once the dragon gains a certain number of points, he will proceed to  the next level. However, if he touches a wizards, he will lose all his points and go back to level one.

Monday, June 9, 2014

Dialogue Broadcast


When a sprite says something, you can make them broadcast it. When the other sprite receives this broadcast, it will trigger their response. they can broadcast back to the other sprite as well.
You would use broadcast when you want the sprites to have a conversation. When you want the sprite to react with an action rather than a sentence or word.

Tuesday, June 3, 2014

Make Your Own Block

"Make a Block" allows you to create a sequence of blocks that cause a sprite to do something. Then, you can use that block you created if you wanted to use that sequence again.
This is useful because it shortens the sequence and the amount of time it takes to write the sequence.

Monday, June 2, 2014

Debug It Reflection

Sometimes I would completely reconstruct the scratch activity. I'd do it the way I would do it originally to see if that would work. Then I would go from there.
To help someone "debug" I would ask them how they would do it in the first place before debugging was necessary.

Debug It 5