Mattdrenaline

  Upon completion of this beginner tutorial I felt very achieved. Although most of the work was done and was following a step by step guide. It's very rewarding to start a project and have it operating properly by the time you finish. I thought I would run into a lot of problems along the way but the software was really quite straight forward.    Coding came easy enough, I did however get an error when attempting to go into G ameview as I forgot to add the ";" at the end of my code. Looking back over my lines of code I was able to locate the problem, mainly because of how many times I've made this same mistake in Brackets while developing websites so the problem was quite noticeable to me. It's great to see similarities like that between modules that I'm doing currently. Web development I'm sure will fit in nicely to future coding that I will need to do I'm sure.    I do feel I will forget a lot of the code in the future, I think that will be my main ...

Taken via Google images When I think of designing a game I instantly think of the end result and how I want the game to look, it's very easy to overlook the game elements and the birth of the game. I need to take a step back and realise although I've been playing these huge triple A titles for years with countless people and resources there to develop such a game I must first realise that I'm just one person and am extremely new to any game design or development. Reading these articles have enlightened me and showed me the importance of early stage game design. A couple points I found interesting is finding the reason why a player enjoys a game. As stated in the first text, as a player saying you enjoy a game because it is fun is not very beneficial to a game designer, although it's a nice comment you would be happy to hear it gives the designer no insight into what factors of the game are enjoyable. The same could be said for a game being unenjoyable. In-depth feedback...