Wednesday, June 18, 2014
Monday, June 16, 2014
Saturday, June 14, 2014
The level is given a variable so you can start at a certain level. This allows the game to start at one and move on as you complete each level.
Thursday, June 12, 2014
Debug 1- http://scratch.mit.edu/projects/23545854/
Debug 2- http://scratch.mit.edu/projects/23546176/
Debug 3- http://scratch.mit.edu/projects/23546342/
Debug 4- http://scratch.mit.edu/projects/23546470/
Debug 5- http://scratch.mit.edu/projects/23546650/
Like debugging before, a prompt was presented to us and explained what was supposed to happen in the project but for whatever reason, it wasn't happening. We had to go in the script of the project and remix it so whatever the prompt asked for was done.
One strategy I used, like before, was simply experimenting and seeing what would happen if one of the blocks were altered. Also, it's usually the command blocks that need to be changed (repeat 10x, forever, wait until ___ = ___) or the broadcast blocks, and not what the sprite is saying.
For someone who was trying to debug, I'd say the best way to figure it out, even if you have no clue and are just staring at the script, is to experiment. The worst thing that could happen is you would have to change it back to how it was at the beginning, but if you play around with the command blocks or the broadcast blocks you're bound to find an answer.
Tuesday, June 10, 2014
For each of these projects, we were given a scenario that had to be completed in the script. I worked on 1, 3, and a variation of 4 to make it my own and more realistic to the backdrop I used. For solving the puzzles, again, the best thing to do was to experiment around with various blocks. The first puzzle I did, where the sprite grows and shrinks, got me thinking of what game I may do.