Beta

 "Beta"

The game has finally come to an end, wo, what a ride!!!. At the beginning I was dreading this process, I thought my opinion would change, no, it hasn't. I'm so happy that this is done, anyway let's get in to the real stuff.

So from the get go, I said my game was going to be extremely basic, I wasn't going to kill myself trying to make this because I have no interest in making games, not yet anyway. I spent ages trying to add extras to my game this week, and after hours and no results, I said no, and said "I'm done", and closed my laptop and went and ate a whole share size bag of Doritos chili heatwave, that made me feel amazing, for ten minutes and after I felt terrible.

But in my opinion I reached my target, depending on the person, goals and targets range in levels, my game is basic, I just wanted to make a game that works, let alone looks good, you can't always get the best of both worlds!! My game is what I said it was going to be, a game where you run and jump over obstacles and if you hit one, you die.

Image Source: Unity Screenshot

A lot of things went wrong during the game creation process, as would happen with anything, but a lot of things went right and that meant me crying less to myself in my room wanting to smash my laptop against my wall and say screw this, "I never wanted to make a game anyway", but I worked through a lot of the wrongs, the game is very basic, other students games are way better made than mine and I'm ok with that. I'm still very confused when reading code, and not understanding what code goes where and why it doesn't work, so Shaun if you've read this far, NO GAME DEVELOPMENT IN SEMESTER 2!!!! please and thank you. I met the targets I set myself weekly, so that made this process more easy, seeing that progress, week by week makes you want to quit less. 

But in all seriousness I've learned a lot this semester and I learned a lot about things I thought I'd never learn anything about so, anything seems possible right about no, I wouldn't count anything out. Thanks for reading have a good one, comment only nice things on my blogs otherwise you will be reported for cyberbullying me online, that's serious you can get in real trouble so, just think before you type, thanks.

Games Testing

 "Game Testing"

During making my game I never once thought about game testing, ever, thank god that this game isn't being distributed to the public otherwise, it would be a flop!!!. From reading the different types of game testing I realized that it's very similar to testing a new kids cereal or product. You bring your target audience into a room, I think it's called a control group testing. You basically bring a group of kids into a room, you put the product in front of them, without a name, or if it's yours, and you compare through reactions, facial expressions and more obvious signs of opinion.

From completing the reading I've learned that game testing can be very scary and off putting because you don't want a bunch of random kids or strangers just saying your game, that you spent hours creating is not good at all!!!.  So any form of testing is off putting but if you want a game to succeed you have to go through with it.

Image Source: Icon

When I thought about game testing I thought it would be as easy as putting some people in a room, then just letting them play until they wanted to stop, they completed the levels or they wanted to stop, I was wrong!!! The amount of different testing these gaming companies is insane, no wonder it takes years for games to be released. 

The testing that's involved are functionality testing to performance testing, and everything in between, each testing phase consists of something completely different, and you think it's impossible for them to build on or fix anything else. One of the main things to take away from the video is to start testing your game as soon as you have a functioning game, don't wait until all the coding and designing is done, it's too late to start then and you could end up having way more corrections you would have if you started testing when it becomes functional.