This is an old revision of the document!
Table of Contents
Design Document
Story
There will not be a story. It's a sports game.
Intro
Probably something akin to the opening scenes for the sports game on tv.
Menu System
I'm not sure about this one. The game consists of both a website and a client engine.
Currently the idea is that team management and character management is handled through the web. Also, on the web will be the ability to schedule a game (challenge) with another team. There will be a launch function on the web to launch the user into a random game.
The only interface that I can think of for the client engine is that it will have an options menu and some kind of chat. Also, there will be stats on the players character.
Controls
This has yet to be determined.
PC
Xbox 360
PS3
Wii
Sounds
Describe the background music and event sounds that will need to be created. Also, discuss any voice acting that needs to take place.
Camera View
There will be two camera views. One is of the player with a first person view and the other is of the spectators which will be a free roam view.
Engine
The irrlicht engine will be used. Other api's such as Hawk for their networking capabilities, XNA for the 360, Nocturnal for the PS3, and the dev site for the Wii. Also, the Havok engine will be used to augment the irrlicht engine or replace it entirely.
Character Growth
Statistics
Rules
Cite the rules.
Roles
Identify which roles the player will be. Will he be a single athlete amongst AI or will he be coaching the team?
Character Animations
How will this be done? Will you use motion capture or a highly skilled animator?
Server
Describe what the server will store and process.
Client
Describe what the client needs to display the game. Will there be in game chat?
Packets
What data needs to be transmitted between the client and server. Try to keep this as small as possible.
External Game Elements
Most of these elements will have their own design documents.
- Web Sites
- Forums
- Updates
- Tech Support
- Distribution