I have found in my years, ok months of game story writing that some writers will type up short little stories to support thier games. I on the other hand go a little further. I tend to type up an average of 100-200 pages of story to help others see what I see in the game creation. In case you are wondering what the heck the point of this question is, I just want to know which you think is better. A) Writing a few pages long story and then typing up the rest of the design, or B) Typing a long, novel-like story which is very discriptive and very easy to follow. Hence eliminating many other parts of the design document?

I''m with you. I''m in the middle of writing a game at the moment and i go into as as much detail without getting ridiculous.

The rest of the team seems to always object to that approach while you''re doing it; when you''re done they''re thanking you.

The Design Document should have lots of non-story related things, regarding programing, gameplay, graphics, levels, weapons, AI, etc. But anyways, if you do write a large story, dont force the player to read it by putting important information in it. I love to read everything in a game, and still am quite horrified when a full page of small-written text pops out.

So, let the player read the story only if he chooses to.

hi, I''m a screenwriter (I can call myself that because I sold my first one this year and just finished filming the low-budget feature in London) and as a sideline I''m writing games and applications for mobile devices...I can write a 120 page screenplay...piece of cake...because it''s just you in a darkened room with a bowl of cereal and your imagination...but gaming I gotta work alongside designers, programmers...it''s a fricking minefield...and what I''m finding increasingly difficult is how a game script should look on paper and work? Especially if you want to send the game off in different directions but with one ultimate outcome.

Any help out there please write me ASAP.

regards

Steve Kendall