Mattdrenaline

What is the purpose of GDD? A Game Design Document (GDD) is a blueprint for the design and development of a game. The GDD is a way of being creative and documenting the approach to the development of the game. Gonzale (1999) states that “ the important thing is to have something that describes your game project (or any other project for that matter) before jumping into production.( Gamasutra ) It should help to plan out your game. Though it is recommended that the GDD should be short it needs to be detailed enough so as game developers and artists can coordinate the development of the game independently whilst still keeping to the design.  The GDD is a blueprint for how the game is going to be designed and built, similar to a mind map. In conclusion, the game design document is vital to making a game and it is important to have in order to describe your game project. How do we create one? There are a variety of tools that could be used to create a GDD. These include word processing...

  Unity Engine Logo This weeks tutorial we were introduced to objects colliding with one another. This was a very interesting lesson and has opened my eyes to endless possibilities. It was basic, once an item collides it was set to make both objects disappear. This was achieved by adding Collider components to our objects in the game, then writing a CSharp script in Visual Studio. With the completion of the tutorials however, the game felt like it didn't run as well as it could have. There's many speed values I would like to change along with the size of my game. I felt everything was quite crowded and it became difficult to progress in the game as the animals spawned frequently and the speed of the character was just not capable of catching them all.  Another mechanic that we were very briefly introduced to is gravity. By removing gravity from our pizza slice in the game, the slice would fly along the ground endlessly. That's really all the introduction we got, disabling g...

  Here is a current image of my progress in Unity, following the tutorial I have been following. I've really been enjoying learning about Unity and progressing. It most definitely is getting more complex and the code is becoming a lot more difficult to follow, remember and has a lot more to it.  It's worrying me a little bit going from following a step by step video tutorial to creating something original and somewhat unique. I hope there will be further tutorials to prepare me for what is to come in the future when developing my game and am hopeful that Youtube will provide some video tutorials on how to design games, similar to the First Person Shooter that I will begin developing shortly. I've had a similar experience like this. Last year studying web development we began by following easy tutorials that would become more difficult but any problems we had the solutions would be clearly visible. When we were left to develop the sight on our own it quickly became frustrati...

Taken via Google Images (Click for link)  The game I am choosing to create for the remainder of this project is going to be a FPS style shooter. Now, right off the bat that seems complex and, in all honesty I am a little sceptical about the workload that may be involved but after doing quite a lot of research I definitely think it is manageable. I don't plan on creating anything too spectacular my main goal is to have the basic mechanics of the game to work properly along with some basic graphics. If in time I'm capable of creating more detailed graphics and find the time and resources to do so, I most definitely will but the priority is for my game to run as intended. I will begin with the sheer minimum. an open plane, untextured perhaps with some 3D objects to add some atmosphere and to create placeholders for future development. ideally I would like the game to run as a quick response, precision shooter which while having fun and exciting aspects to the game, can be used to ...

  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 ...

  Just learned how to add a twitter widget to my blog! This displays as a sidebar to my blog which is linked to my twitter, showing all my most recent twitter posts.  Pretty cool little feature definitely adds a little extra to the blog and people can keep up with me a little easier. Definitely something I would consider using in the future.

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...