Multimedia Development Game Blog

  Image of my prototype This week I started work on my prototype for my final game. I did this by following the instructions of the first weeks Unity tutorials that I did. The idea for my final game is similar to Tony Hawk Pro Skater. I plan on having a skater skating around the screen similar to the first Unity tutorial and destroying crates that come along the way. I also decided that if my player falls off the road then you lose the game but if he destroys all the crates then you win in order to make it quite challenging. I also have the camera at an overhead view so I could see how I was positioning everything in my scene view and I may try do this in my actual game as I quite that look. The little green rectangle is a prototype of my skater and the two big cubes are prototypes off my crates. Setting up the prototype was surprisingly fairly easy however it was the coding that I found quite tricky as always. Thankfully I managed to get my first obstacle destroyed but I had diffi...

Image from the tutorial For this weeks Unity tutorial I had to continue on from last weeks one. This week I had to learn how to make the player going from a running state when using the running controls, a jumping state when using the jump controls and a death state when the player hit a barrier. To do this I had to use an animation controller.  Animation controller The animation controller is what is used to control the players animations which is pretty self explanatory. The animation controller controlled each state that the player is in so I needed to use it to get him into any one of these three states when needed. When I clicked on walk or run the players animation character walked or ran however when I clicked walk_static or run_static the animation character only ran or walked on the spot. I then had to edit the players condition. I had to change the speed from 0 in order to get him to move. I then had to make the player start off by running. To do this I had to go to the p...

( https://blogger.googleusercontent.com/img/proxy/AVvXsEg2qRVOQwZph6ZRbE8PNUXSMzIKkZttcCFI-SWuFzLoLpOygvoRtjGyVstcgPDFsD5tnxoN-H5RKuBPah5IzQZTN3-56ifoSsDQQslgKjlzk1hqFIVWY_6zHvxlBmEnG0-wE4EDj3VcVuFTXpw9hUOPnOq1hRkejru8p7T7jWj6xP4jqf69MBOkTJZA-5Eb6C7K8-3Z9mi7pg= ) For this weeks task I had to read two articles and watch a video on game decisions. The first article was called "Building A Saving Princess App".  The article talks about how to build learning and fun into your applications. It also talks about the difference between games and apps and how games are usually good at saving princesses and how apps don't do it half as well.  Image from the article The image above is an example of a typical app. The article tells us that everything that needs to be done is already in the box and basically done for us and that it focuses on the user utilitarian tools to get things done.  The article also talks about the learning curve for apps and about how skills are a useful tool t...