Q1. Why do you think there is so much variation in the structure of each design document?
A1. A design document is fundamentally unique to the designer themselves and what game elements they want to showcase. For example, if the game has a weaker plot line but is strong visually, the designer may want to highlight this point; including documentation of the environment (drawings, screen shots, character designs), and perhaps only touching briefly on the plot line. Of course, there could be an opposite to this; perhaps the game has a low budget or is going to be run on a weaker gaming system and thus is unable to run heavy graphics; in this case the designer might want to draw attention to what they have done to make up for this in terms of story, character interactions and gaming experience.
Q2. How much technical information is contained within the design documents? Would a programmer be able to pick up any of these design documents and create the gameplay based on only the information presented within the design document?
A2. The design documents contain an astonishing amount of information; including menu designs, cheat codes, player communications with instructions/interactions, how the game should react to certain inputs (and sometimes if no input occurs at all).
Although a programmer perhaps may be able to create the game described in the design document, the gameplay itself is something altogether different. The gameplay should be something unique, at least in feel, for every game; and no doubt the designers’ intend this. The programmer themselves cannot completely understand what the designer wants in terms of atmosphere and how they want the player to feel/interact with the games elements. For example, perhaps the designer wants the player to feel particularly uneasy on a certain level, using dim lights, sound triggers, extra shadows and maybe even very specific details like rain pattering upon the windows; with the player avatar being made very aware of these things with interactions/drawn vision. These small details are perhaps too specific to be included in a design document, thus the programmer’s creation may feel bare and be a somewhat incomplete experience.
Q3. Discuss a few good points about these example documents, and then identify a few areas which you would improve in your own design document. For example, you may want to reduce some of the long paragraphs of text in some documents and present that same information as a bullet list to make the information more accessible.
Q3. Discuss a few good points about these example documents, and then identify a few areas which you would improve in your own design document. For example, you may want to reduce some of the long paragraphs of text in some documents and present that same information as a bullet list to make the information more accessible.
A3.
I particularly liked Grim Fandango and the style of design document used; the heavy graphics – though not computer generated, but rather sketches were lovely to view and gave me, as a reader, a greater idea of what kind of atmosphere and feel the designer means for the game to have. The plot and interaction descriptions are also amazingly rich in character – almost as if they are a story.
The maps used in Technomancy were also brilliantly realised, and the level of detail used for them allowed me to imagine the gameplay that bit better and how the player would advance through the level/s.
The Claw on the other hand relies heavily on the technical components and contains absolutely no graphics; giving the reader a large dose of practical information on the system specifications and user interaction/instructions.
All of these design documents have things that uniquely give the reader something special to lock on to, though these points can also be their downfall; relying too much on information and specs, and not on story, experience and gameplay (ultimately why a gamer would want to purchase the product) could leave the reader feeling no real passion for the game itself. The opposite can be said for design documents that use heavy graphics and no real information at all could give the wrong impression to a reader; that the designer, although confident in how the game should feel/look, hasn’t thought about basic foundations of how the game will run and what it should include technically.
Within my own design document, I would want to draw inspiration from Grim Fandango, and use graphical pieces to convey the design, but also including enough information, so that the reader can understand the more technical aspects; though I would aim to keep these simple so as not to weigh the reader down with unnecessary information.
No comments:
Post a Comment