The Art Of Gaming

 I finally finished my game and I'm extremely proud of it! I might not have been as accurate with my game design document as I hoped but I still made a working game at the end of the day and that's all that matters. I tried to work with what I had and if something didn't go the way I wanted it to then I would move on to the next thing.  This week I decided to focus on the start menu and I followed a tutorial that I found on Youtube here . It was a really easy tutorial to follow and I spent some time looking for the best possible main menu image and how the text was going to look. I managed to get it working without any issues and I was so excited that I didn't break the game or anything.  I also worked on the end screen and I followed this tutorial on Youtube and I put in a very simple "You Win!" text and changed the background to a dark blue / purple. I had to player test my game and I kept dying but I finally managed to get to the end and it worked. I hate

 Lesson 5.4 In this tutorial we made a title screen which include different types of difficulties - easy, medium and hard. We changed the spawn rate by coding the difficulty button scripts as well as the game manager. For some reason my lesson didn't save and I only have a blank screen but you can see the difficulty button texts on the side as well as the "difficulty button" script.  As you can see in the photo nothing is showing, I don't really know what's wrong Challenge 5  In this challenge I was able to mess around with the placement of the difficulty buttons as it was easy enough since they were messed up in the title screen. As usual for the rest of the challenge I went to look through Youtube tutorials because I was stuck on what to do. I was able to go back in the previous unity tutorial I did before the challenge and I changed it so the difficulty buttons actually changed the difficulty. There's a really cool Youtuber who goes through the process of e

7 Different types of game testing techniques   Gaming companies need to play-test before they release a game in order to find any faults, glitches and bugs. A recent example of this would be Assasins Creed Valhalla which caused uproar in the gaming community. If a company releases their game without figuring out the errors, it will bring talk amongst the community which can bring down sales.  Game manufacturers need to know who their fanbase is first of all, they need to test their games in order to perfect their end product.  These are the big risks when it comes to game testing: If the game isn't compelling enough for your target audience. If the game has boring aspects. If the game is too repetitive and common for the users.  With risks there are many different game testing techniques that big companies such as KiwiQA, TestBytes etc. use. The errors are documented and brought to attention.  1) Functionality testing - Generic problems are hunted such as game mechanics, sound, gra

 Lesson 5.1 This game was very simple and it didn't need too much coding as the only 3D aspects were the objects. The tutorial made it so objects were tossed into the air randomly and whenever the player clicks on the objects the object gets destroyed.  Lesson 5.2 I remember doing this in my unity tutorial but it was probably way more complicated. This was to do with the scoring system that you put into the game which is a UI element. You can change the font size, the font family, the name of the text to score and so forward. The tutorial made it so whenever you press the boxes you get a set amount of points and when you press the skull the points decrease by 10. We also put in particles whenever we click on the objects!  Lesson 5.3 In this tutorial we made a restart button with the text UI so when the player misses a box, the restart and game over button appears on the screen and the player will have to restart the game. I wanted to do this tutorial as I want a similar concept wit