Jump to content
  • Advertisement
Sign in to follow this  
S&H Music

Process

This topic is 2435 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

Seeing as though I pay this forum money, I guess you could say I would like a 'good', non one line answer that actually has interest from the replier
to show someone who wants to go somewhere, get there with it.

Thanks in advance.

Tim

Share this post


Link to post
Share on other sites
Advertisement

1. Write an overview of the story in prose
I stopped at this point. It is definitely a bad "process". Story is never first, games are build of mechanics and rules. Also, in all these 8 points there was not even one instance of word "fun", which is supposed to be a critical focus point of any game. Also, it is rather artificial, there are no points like "the programmer said he have an idea how to implement a cool, flaying castle, so the story should incorporate one" or "the artist is very good at making trees, so the story should have many forest locations".

Anyway, you could get better respones if you write more about the game (what genre it is? what is the theme? how many people involved?) These all affect the design process heavily.

Share this post


Link to post
Share on other sites

Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

Seeing as though I pay this forum money, I guess you could say I would like a 'good', non one line answer that actually has interest from the replier
to show someone who wants to go somewhere, get there with it.

Thanks in advance.

Tim

This certainly is a process... for storyboarding and fleshing out the storyline. It's not very relevant to game design though; since you missed game mechanics, levels, items, interactions, flow etc.

Share this post


Link to post
Share on other sites
Ok, so this 'process' was my test, because the feedback that you get from this place is actually telling me to follow this process
from previous posts of mine asking for help, even after posting a full 'script in process'.

So in short, that is why there is NO views of the character/the world etc because that is already floating around the traps here in previous posts. It was just a question.

If I were you guys, the one who know the answers, missing the forums posts of replies to someones ideas, you should actaully read all of whats before you
before you pass quick judgements. Isn't that what forums are for? Help? Or is it a quick 'scope this'.

If your info is so bright on process, what do you do for a living? Give me an insight of whats your true skill. Then maybe I will stop judgement on the quick pass you just made.

Share this post


Link to post
Share on other sites

[quote name='Tim Law' timestamp='1324328726' post='4895465']
Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

Seeing as though I pay this forum money, I guess you could say I would like a 'good', non one line answer that actually has interest from the replier
to show someone who wants to go somewhere, get there with it.

Thanks in advance.

Tim

This certainly is a process... for storyboarding and fleshing out the storyline. It's not very relevant to game design though; since you missed game mechanics, levels, items, interactions, flow etc.
[/quote]

Thanks for that mate, this is a reply appreciated. Simple and to the point :)

Share this post


Link to post
Share on other sites

Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

You haven't mentioned the controls, about the UI, about the AI. You also need at least a preliminary competitive analysis (discuss what existing games it might be compared with, what existing game audience it might interest, how your game differs from and is better than those existing games). And of course what's the platform and who's the audience.

Share this post


Link to post
Share on other sites

[quote name='Tim Law' timestamp='1324328726' post='4895465']
Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

You haven't mentioned the controls, about the UI, about the AI. You also need at least a preliminary competitive analysis (discuss what existing games it might be compared with, what existing game audience it might interest, how your game differs from and is better than those existing games). And of course what's the platform and who's the audience.
[/quote]

Ok, so halfway down the list of THIS forum is a post called 'Dreamscape'...that's me and my storyline pitch.

Now, to make things clear...it has evolved from that, including even dumping the idea of the blade, and certain other things. I have created a 'flow chart', I have introduced more characters
and have developed a theme for visuals revolving around it etc. So in short I am developing that Game Design feel, only without the 'artist' side so far.

But I am not going to post it. This forum and site has problems with adding attachments via my end, so I gave up trying to add a file, which is why I have kindly asked if there is interest
in a story with 'more' vision, to email.

Unless of course, someone can tell me why your site doesnt like attachment files of the word document type? It is a zipped folder, and is 26KB and goes fine through email
but attaching it here...well thats another ball game.
'

Share this post


Link to post
Share on other sites

[quote name='Tom Sloper' timestamp='1324336560' post='4895528']
[quote name='Tim Law' timestamp='1324328726' post='4895465']
Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

You haven't mentioned the controls, about the UI, about the AI. You also need at least a preliminary competitive analysis (discuss what existing games it might be compared with, what existing game audience it might interest, how your game differs from and is better than those existing games). And of course what's the platform and who's the audience.
[/quote]

Ok, so halfway down the list of THIS forum is a post called 'Dreamscape'...that's me and my storyline pitch.

Now, to make things clear...it has evolved from that, including even dumping the idea of the blade, and certain other things. I have created a 'flow chart', I have introduced more characters
and have developed a theme for visuals revolving around it etc. So in short I am developing that Game Design feel, only without the 'artist' side so far.

But I am not going to post it. This forum and site has problems with adding attachments via my end, so I gave up trying to add a file, which is why I have kindly asked if there is interest
in a story with 'more' vision, to email.

Unless of course, someone can tell me why your site doesnt like attachment files of the word document type? It is a zipped folder, and is 26KB and goes fine through email
but attaching it here...well thats another ball game.
'
[/quote]
If you want to break it down, there are a number of documents pertaining to development (some optional, others mandatory):
  • Concept Document
  • Game Design Document (GDD)
  • Technical Design Document (TDD)
  • Story Bible
  • Business PlanSome of these are of course called different things depending on who you ask and where they work and what they are working on, but I fare to say the breakdown is pretty accurate. What you are writing falls more in line with 'story bible' than it does with a GDD or a concept document. Story of course always plays a part, in some games even a vital part, but it can't make a game concept since a story by itself isn't a game! Oh, well, unless you're writing a point 'n' click I guess -- in that case, a story could very well be the entire game -- but even then you have mechanics, even if they are minimal!

    A concept document usually focuses more on what makes the game unique and what aspects make it fun and interesting for players to, well, play! Whereas a GDD focuses more on the details of the design -- how many of this, how many of that, how does this game mechanic work, what level does he get that...you get the point. Usually a GDD also contains a brief 'technical' section -- but that's mostly just fluff so anyone can breeze over it and see what tools are being used in development.

    TDD is irrelevant to a designer, mostly, while a business plan only goes if it's a commercial venture. A story bible is an 'extension' of the GDD -- in large RPG:s and similar type of games that usually contain complex storytelling, it serves as a place to store all the tidbits about lore and various miscallenous background info.


    Hope that clears it up a bit (if you needed it cleared up? Can't tell, but here ya go anyways!) :)

Share this post


Link to post
Share on other sites

[quote name='Tim Law' timestamp='1324340733' post='4895546']
[quote name='Tom Sloper' timestamp='1324336560' post='4895528']
[quote name='Tim Law' timestamp='1324328726' post='4895465']
Hi,

Is this a good Game Design or concept process:

1. Write an overview of the story in prose
2. Write a history and quick background of the world
3. Create a flow chart with descriptions
4. Create sub-quests
5. Create character descriptions and bio's etc
6. Write interactions with non player characters
7. Write a storyboard script
8. Collaborate

Is this the correct process of how and where to go with a concept?

You haven't mentioned the controls, about the UI, about the AI. You also need at least a preliminary competitive analysis (discuss what existing games it might be compared with, what existing game audience it might interest, how your game differs from and is better than those existing games). And of course what's the platform and who's the audience.
[/quote]

Ok, so halfway down the list of THIS forum is a post called 'Dreamscape'...that's me and my storyline pitch.

Now, to make things clear...it has evolved from that, including even dumping the idea of the blade, and certain other things. I have created a 'flow chart', I have introduced more characters
and have developed a theme for visuals revolving around it etc. So in short I am developing that Game Design feel, only without the 'artist' side so far.

But I am not going to post it. This forum and site has problems with adding attachments via my end, so I gave up trying to add a file, which is why I have kindly asked if there is interest
in a story with 'more' vision, to email.

Unless of course, someone can tell me why your site doesnt like attachment files of the word document type? It is a zipped folder, and is 26KB and goes fine through email
but attaching it here...well thats another ball game.
'
[/quote]
If you want to break it down, there are a number of documents pertaining to development (some optional, others mandatory):
  • Concept Document
  • Game Design Document (GDD)
  • Technical Design Document (TDD)
  • Story Bible
  • Business PlanSome of these are of course called different things depending on who you ask and where they work and what they are working on, but I fare to say the breakdown is pretty accurate. What you are writing falls more in line with 'story bible' than it does with a GDD or a concept document. Story of course always plays a part, in some games even a vital part, but it can't make a game concept since a story by itself isn't a game! Oh, well, unless you're writing a point 'n' click I guess -- in that case, a story could very well be the entire game -- but even then you have mechanics, even if they are minimal!

    A concept document usually focuses more on what makes the game unique and what aspects make it fun and interesting for players to, well, play! Whereas a GDD focuses more on the details of the design -- how many of this, how many of that, how does this game mechanic work, what level does he get that...you get the point. Usually a GDD also contains a brief 'technical' section -- but that's mostly just fluff so anyone can breeze over it and see what tools are being used in development.

    TDD is irrelevant to a designer, mostly, while a business plan only goes if it's a commercial venture. A story bible is an 'extension' of the GDD -- in large RPG:s and similar type of games that usually contain complex storytelling, it serves as a place to store all the tidbits about lore and various miscallenous background info.


    Hope that clears it up a bit (if you needed it cleared up? Can't tell, but here ya go anyways!) :)
    [/quote]

    Again, thanks heaps. I haven't received much 'breakdowns in clarity' of direction in the scope that you have put it in, but that is exactly what
    I have been needing. A direct clear path on 'explanations of what, where and if to go there and how to get there'. Most of all, possibility with a vision of approach.

    It really is a great help mate, cheers :)

Share this post


Link to post
Share on other sites

Seeing as though I pay this forum money, I guess you could say I would like a 'good', non one line answer that actually has interest from the replier
to show someone who wants to go somewhere, get there with it.


Please be aware that no-one here - not even the moderators - is paid to answer your questions. Your GDNet+ subscription includes many things, but some kind of preferential treatment from other users or moderators is not among them, and GDNet+ users are expected to follow standard netiquette just like everyone else.

If you find you are not getting good answers, please consider the possibility that you may not be asking the right questions.


Is this a good Game Design or concept process:
[snip]
[/quote]



As has already been said, this process is very much about story and includes almost nothing about game design. If there is any confusion about what I mean by Game Design, please read the FAQ. (apologies in advance for the formatting, the forum software has thwarted every attempt to fix it). In fact, even if you aren't confused, read it anyway, because it may actually answer more of your questions.

As for my previous comment about 'not asking the right questions' - what are your actual goals here? Because ultimately, knowledge of the general process followed in professional games studios (and that process may vary considerably from one studio to another) may or may not be of any actual use to you.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!