Excuse me, can you help me please?
by Anonymous · in General Discussion · 01/31/2002 (5:45 pm) · 3 replies
#2
Good start on this, but you're going to need much more detail.
Remember, a design document is something that should be able to be given to someone with a decent amount of knowledge in one or more areas of game design and have him be able to walk away from reading it saying "yeah, I understand how you want this to be"
All I can say is... the original design document written for the project im working on (not by me though) was over 20 pages... and it still was incredibly vague.
You seem to lay out the "parts" you're going to need very well, but the gameplay and story and special features like game saving and how you're going to find voice actors... well, those don't seem to be in there.
Writing a design document will kick your ass.
It's no walk in the park essay... it's a guide to make sure you know what you want fromt he project, and a way others can look at something and understand what you want from the project.
Planning ahead will save you so much time in the long run you'll be thanking everyone who asked you to give large amounts of detail for the design doc. Right now... this design document is clearly coming from someone who isn't entirely sure what all the "departments" will need in order to carry out the game to a "t".
I will be posting a tutorial/resource aimed at providing ways to get that design document finished and other tips regarding team formation as well as technical skills needed for you (the project coordinator)
01/31/2002 (8:38 pm)
Wow, deja vu all over again!Good start on this, but you're going to need much more detail.
Remember, a design document is something that should be able to be given to someone with a decent amount of knowledge in one or more areas of game design and have him be able to walk away from reading it saying "yeah, I understand how you want this to be"
All I can say is... the original design document written for the project im working on (not by me though) was over 20 pages... and it still was incredibly vague.
You seem to lay out the "parts" you're going to need very well, but the gameplay and story and special features like game saving and how you're going to find voice actors... well, those don't seem to be in there.
Writing a design document will kick your ass.
It's no walk in the park essay... it's a guide to make sure you know what you want fromt he project, and a way others can look at something and understand what you want from the project.
Planning ahead will save you so much time in the long run you'll be thanking everyone who asked you to give large amounts of detail for the design doc. Right now... this design document is clearly coming from someone who isn't entirely sure what all the "departments" will need in order to carry out the game to a "t".
I will be posting a tutorial/resource aimed at providing ways to get that design document finished and other tips regarding team formation as well as technical skills needed for you (the project coordinator)
#3
I wouldn't be too worried about someone stealing your idea. If they're to the point that they read these forums, they probably already have an idea that they consider better (Their own)...
One thing I would like to see is an HTML version of this, so that it's easier to read in installments.
My NZ$0.02 GST exclusive ;)
02/02/2002 (2:25 am)
A very long read... Needs the warning "Remember to blink" put at the top...I wouldn't be too worried about someone stealing your idea. If they're to the point that they read these forums, they probably already have an idea that they consider better (Their own)...
One thing I would like to see is an HTML version of this, so that it's easier to read in installments.
My NZ$0.02 GST exclusive ;)
Torque Owner Jeff Tunnell
Jeff Tunnell GG