Rules for writing a Design Document
Inga kommentarer än än så länge
Kommentera
september 17, 2007, 11:50 e m
Sparat under: Open Game Design
Sparat under: Open Game Design
I shall try to pin point the old wisdom of how to. I will edit it, add and remove stuff, patch bugs in the statements. This is just repetation of old information.
- Nothing will, everything shall – Be definite when you describing things, it shall not be a guessing game for someone that reads your document.
- Short but totally describing – Do not write for your sake, write for the developer that shall read it.
- Write in simple and in area language, don’t create new complex words for old things.
- Remove not needed explanations.
- No emotions – a dry language
- Knew the capacity of the development team.
- The time-frame the game shall be produced in.
- Don’t loose the small base idea – it’s the foundation in the game, it is what makes the game worth playing without the fancy glamour.
- The document is not your only end-station of ideas; you shall have all about the game in your head, every tiny non-important important thing.
- Let every idea rest for a while, let them grow in you head. Clean out the weed.
- Kill your darlings – A designer’s favorite quotation
Kommentera
Inga kommentarer än än så länge
Kommentera
Kommentera
Rad och paragraf bryts automatiskt, e-postadress visas aldrig, HTML tillåten:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>