Thursday, October 29, 2015

Whack-A-Mole

11:04 AM Posted by Unknown No comments
Download here: https://drive.google.com/file/d/0B5IR0RGtQFb5Qm5CZTFLajVZZEU/view?usp=sharing

My Partner David and I created an app in MIT App Inventor 2, a web application used to create software applications for the Android operating system using visual, drag-and-drop building blocks. Our app is the game whack-a-mole, where the user tries to tap on moles that randomly pop out of the ground. The user scores a point if they can successfully tap the mole, and our app also keeps track of how many times the user attempts to hit the mole and misses.

We started out our final project by doing the mole mash tutorial on the app inventor website. We set up the an image sprite of a mole and a clock to have it change positions, a procedure to have the mole move to a random new position if the timer runs out or the mole is tapped, a score counter to keep track of how many times the mole has been touched, and a reset button to set the score back to zero. 



We then added another score counter to keep track of how many times the mole was missed and the canvas was touched.  Because the image sprite of the mole is located on the canvas, our new program added a point to the miss counter every time the screen was touched, including when the mole was touched at the same time.  We fixed this problem by subtracting a point from the miss counter every time the mole is touched to counteract the extra  point that was being added.

The next step was to add a background with set locations on the screen that the mole could appear to make the app look more like a game.  We also added a sound component that makes the android vibrate when the mole is hit.  The next thing we added was a "pow" animation that appears when someone's finger taps down on the mole and disappears when the finger is lifted away from the screen.

The final thing that my partner and I added to our app was a start screen.  We did this by adding a second screen to our app.  We added a button to the second screen and set the program to when the button is pressed, the app switches back to the first screen.  We also added to the reset button to take the app back to the second screen (the start screen) when it is pressed.




Wednesday, September 16, 2015

What we Implemented into our Game

7:50 PM Posted by Unknown No comments
For the program we began to build in Scratch, outside help was needed. One thing we learned about how to use appropriately were "Variables." The variable "rightarrow" in our program determined how the background images (castle wall's) were to move and duplicate across the screen. 

Screenshots below help as a visual guide:



Uploading our game

7:48 PM Posted by Unknown No comments
Despite our attempts at making a scrolling background, Jenna and I were not able to do so. The result is this unfinished Scratch Project of which we came very close to completing all the tasks required of us. Our plan is to finish this "game" or lack-thereof once we have the knowledge and resources to do so.


<iframe allowtransparency="true" width="485" height="402" src="//scratch.mit.edu/projects/embed/74483004/?autostart=false" frameborder="0" allowfullscreen></iframe>

Monday, September 7, 2015

7:06 PM Posted by Unknown No comments


My partner David and I asked our partners to create a standard maze game on scratch, an MIT developed programming language and online community where people can program and share interactive media such as stories, games, and animation with people from all over the world.We asked Sam and Miles to create a maze game that included

  • Three difficulty levels
  • Randomly generated mazes
  • An instructions menu
  • A timer
  • A bird's eye view