Schedule
Scroll to the right for moreeeeeeeeeeeeeeeeee
| Week | Art | Animation | Game | Graphics | GUI | Input | Network | Physics | Sound |
| 2 | Create list of all maps, characters, weapons etc. that need to be created. Research. | Take list of characters/objects and create list of animations necessary for each (death scenes, etc.) and begin sketch. | Research DirectX. Basic Game Loop. | Creation of basic framework, system that allows for extensions. | Keep general idea in mind. Research. | Basic State input. IE Exit Program. | Research Winsock. Implement client/server echo functionality. | Begin implementing classes and fitting it into the regular framework. | |
| 3 | Character and Map sketches. Begin creating characters in Maya. | Continue above. | Program / Project structure and module implementations have been decided upon. | Extensibility for engine? Scene Graph? Particles? Are objects classes? etc. | Continue above. | Wait for other modules to mature a bit before further analysis. | Server-client basic interactions. Server-side send / receive nearly fully implemented | Discuss physics implementations. | Finish sound classes. Desire to have sound module implemented. Placeholder sounds in place. |
| 4 | Continue above. | Continue above. | Start module connection. Ideally, multiple clients fly around in 3-d world. | Basic textures and shaders. A working map. | Begin refining GUI. | Movement system analysis in DirectInput. | Multiple client connection logic. Asynchronous clients. | Coincide implementing above with other modules. Begin coding jumping, basic collision detection. | Replace placeholder sounds. |
| 5 | Finish artwork content. Implement into working aspects of game. | Take 3D models and implement movement. | Refine game loop. Content creation / implementation begins. | Work on animation integration so that engine fits in with design philosophy. | Discuss implementations for all necessary user systems. HUD discussion. | Player movement. | Game state updates. Decide upon what information packets will carry and how to parse it. | Collision Detection (I). Jumping. | Continue above. Associate existing sounds with objects finished thus far. |
| 6 | Continue implementing artwork as objects are finalized / created. | Continue model animations and implement model movements into game. | Content creation. Gameplay mechanics. Implementing out of game flow. | Animations. | Revise above. Implement basic GUI. | Status screens. Menu interaction, etc. | Client-Server / Server-Client interactions fully implemented. Packets well defined. | Continue collision detection. | 3D sounds. |
| 7 | Resolve any design / implementation flaws. | Resolve desing / implementation flaws. | Revise content if needed. Add more as we see fit. | Apply animated characters in collision detection. Bounding boxes implemented. | Functioning GUI implemented. Crosshair, health bar, ammo meter. | All player input actions well defined, implemented. | Solid client/server interface. Client disconnection working. | Collision detection testing. | 3d sounds. |
| 8 | Alpha testing. Phase I. | Alpha testing. Phase I. | Solidify game constructs. | Lighting and other effects. | GUI fully implemented: menus, hud, etc. | Alpha Testing. Phase I. | Alpha Testing. Phase I. | Alpha testing. Phase I. | Alpha testing. Phase I. |
| 9 | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. | Alpha Testing. Phase II. |
| 10 | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. | Operational Beta. |
