Posts

Showing posts with the label Week 6

Game Design Document

Image
Source: flickr Here is the link to my game design document   I have researched several aspects for my project. I created my GDD with Dundoc, which also helped me arrange my document. The game design document is a work in progress, I love the how each document is different and there is no specific layout. I'll keep track of the game's details and decisions, such as characters, levels, and systems.  A GDD is a document that documents the aspects and mechanics of a game. I will used this as a communication tool to show my lecture all my decisions I have taken for this project.   

Games GDD

Image
  Source: flickr This week, in reading week I read about Game Design Document (GDD ), which all game designers should have, containing all their ideas for the game. A GDD is a great structure to put all your information and ideas about the game.A game's mechanics are defined in detail by a number of key design considerations.  Designers use design documents to keep track of their design decisions. You won't have to solve the same design challenge twice this way. It also used for yourself to help everyone understand the game ideas and what direction the game going in. It learned that a GDD is very fluid, and there is no actual format to follow.  If you do not create a document or any prier planning, you may find yourself backing into a corner leaving you with no more ideas. Distinct game development teams have different documentation requirements. This will vary depending on the size of your team and the complexity of your project, but in general, it separates design...

Unity Tutorial 05

Image
  This lesson is by far one of the most enjoyable and definitely the most interesting, as I stated in my last post the coding and mechanics for my final game will definitely be similar. The agenda for this lesson is the background moves in perfect sync with the obstacles, and the obstacles disappear as they leave the game borders. When the player collides with an obstacle, the background and spawn manager will come to a halt thanks to script communication. When you collide with an obstacle, you'll get a game over notice in the console log, and the background and spawn manager will stop working. The one thing I find confusing is the script communication.  I needed to communicate to the Spawn Manager script and tell it to stop when the game is ended.I could not wrap my head around the code.I found myself not having a complete understanding of it, but hopefully moving forward I will start to understand it. Everything else in this lesson. went smoothly, and there was repeating cod...