• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.

Archived

This topic is now archived and is closed to further replies.

ugenn

Design Document Question

2 posts in this topic

What exactly should go into a design doc and how detailed should the writing be? Everytime when I write up the technical description of a game, a lot of the stuff map directly to program code. So I get the feeling that what I''m doing is overkill since I''m better off spending the time writing it directly as code anyway. I would appreciate some suggestions, esp from someone with the relevant experience in this area.
0

Share this post


Link to post
Share on other sites
Write out what the program is suppose to do, now how it does it. If the documents are for your own use, make them as detailed as you want. When you''re writting documents, you''ll think of things you might not of thought of right away. These things might affect the way your program works or is structured.

I''d make them almost as detailed as a flow chart. When you have docs like that, the coding will just be "filling in the blanks".

For instance: I recently wrote a quick program but I didn''t have very good documentation, just some notes. Later I wanted to add the ability to save out its data elements to a file. My program was using a lot of pointers and I didn''t have anyway to mark an element as unique, only by it''s memory address. Of course I couldn''t save that to disk so I had to change the structure of my program to include a unique ID on each element. I also had to add code to setup this ID when an element was created (which could be done in several different ways, for each of the 7 types of data I''m using)

E:cb woof!
0

Share this post


Link to post
Share on other sites
The easy answer for this is EVERYTHING!!! And it true with some modifications. I would say everything execpt code, it's all about what the game offers, what the player can do, what scenes, backgrounds, music will be there. Make it as detailed as you wish, but a good thing is to describe everything, if thing can be moved, describe it.

Splitting it up in diffrent sections is a good thing.
* The basic idea
* The story of it all, background story
* What is it the player should do to win
* The design, interface etc
* NPCs and dialogs

I might have fogotten something, but most of it should be there.

Edited by - Mr K on 2/18/00 4:37:46 AM
0

Share this post


Link to post
Share on other sites