The main purpose of this meeting is to formally define the game play. As result every team member will have to work on a portion of tha game.

Moreover at the end of the meeting the Game Design Document will be published. It will contains the following:

• Executive summary – the 1 page “big picture” summary – specifies the FOCUS of the game.
• Game mechanics - how the user reacts to the world. What can the user do in the world?
• Artificial Intelligence – how the world reacts to the user. How do opponents respond to the users?
• Game Progression – the events the player experiences. Game levels. What happens when the player finishes a task? What happens when you finish the level? What is different in the next level?
• Game Elements -  Characters, items, objects/mechanisms – elements that are encountered, accessible, at each level of the game.
• Story – if there is one, the story helps define why certain gameplay elements make sense- e.g. why can the player fly?
• Script – final execution of the story and cutscenes will require a script.
• Sound effects – elements in the story that generate sound effects and the sound effects they generate. Background sounds.
• Menus and interface design – how users control the environment, game dashboard, opening menus, save/load screens, options & cheat screens.
• Art Bible – sketches and mockups of objects, characters, items.
• Storyboards – useful in illustrating aspects of the gameplay- e.g. camera angles or layout of game screens; storyboards are absolutely necessary for cutscenes.

The meeting will be a good time also to put a timeline by starting bacwards from the next deadline that is on 10/24/08, on which we'll present the first demo of our game.

See you for updates.