Originally posted by Quizzical

A lot of the details that need to be filled in don't become obvious until you have a game working with a lot of features already implemented.  Once you have the game sitting there, it's completely obvious that you have some major components that are completely missing, but you didn't realize it while writing a document.

There are also a lot of things that on paper, look like they should work flawlessly.  But once you implement them, it's obvious that they're completely broken.  It's unlikely that you'll ever detect that while the ideas are just on paper, but they could force enormous redesigns of large swaths of content once you try to implement them.

Quizzical has some great advice there, Mike.

You've got everything written out, so now it's time to start trying out what you've created. GameMaker is a great free tool for testing out ideas. You could even raid your board games for dice and pieces to start testing it out that way. Have other people playtest the various systems in your game. See what they are doing and find out WHY they are doing it. How you may perceive the mechanics being used could be radically different from how others actually use them.

You'll find you have a ton of refining to do at that level. After that, it's getting the various elements to work together in the same enviroment. Test, change, refine.

I want to offer a fast track to this study tho:

Create an IP elsewhere first.

Novel, cartoon, comic book, pen & paper game that appeals and resonates with the core gaming community. Then sell the IP to become a MMO. 

IP MMOs are all over the flippin' place.

Originally posted by mikecackle

Everyone talks about what his or her dream game would be like... I want to take that idea to the level light years beyond those basic thoughts, so I was asking if there would be those to listen and perhaps support, otherwise there is no sense in me to start recording :D

You sound like you'd be unwilling to accept any answer but "yes".

When you're creating for a paycheck, that's an extremely bad habit.

How do you react to editors?

Originally posted by Loktofeit

Originally posted by Quizzical

A lot of the details that need to be filled in don't become obvious until you have a game working with a lot of features already implemented.  Once you have the game sitting there, it's completely obvious that you have some major components that are completely missing, but you didn't realize it while writing a document.

There are also a lot of things that on paper, look like they should work flawlessly.  But once you implement them, it's obvious that they're completely broken.  It's unlikely that you'll ever detect that while the ideas are just on paper, but they could force enormous redesigns of large swaths of content once you try to implement them.

Quizzical has some great advice there, Mike.

You've got everything written out, so now it's time to start trying out what you've created. GameMaker is a great free tool for testing out ideas. You could even raid your board games for dice and pieces to start testing it out that way. Have other people playtest the various systems in your game. See what they are doing and find out WHY they are doing it. How you may perceive the mechanics being used could be radically different from how others actually use them.

You'll find you have a ton of refining to do at that level. After that, it's getting the various elements to work together in the same enviroment. Test, change, refine.

 

Yeah, understood. I have 15 years of data programming experience, in which I always believed in a more procedural base approach of building projects unlike todays more object orientated rail based systems. It leads to a modular approach in development that provides a very stable backbone. Things take a bit longer to develop this way but are so much worth it and mistakes don't happen and you never code yourself into a corner. (things are done, tested and completed, and moved to the next problem) So that has helped tons with the initial design of the game.

And no I have not everthing written out yet :D Its a major task with tons yet to do, but i have hundreds of hours of theory and design completed, as well as lore and other stuff...

No, not at all. It's all about the Benjamins and you just need to be a big name or some big funds.

After that you can do anything you want.

Ooh yay, it's time for Death by Powerpoint!

/popcorn  Ready!  Roll film!

er...wait...no film? Just a cover slide?

Originally posted by mikecackle

Originally posted by Loktofeit

Originally posted by Quizzical

A lot of the details that need to be filled in don't become obvious until you have a game working with a lot of features already implemented.  Once you have the game sitting there, it's completely obvious that you have some major components that are completely missing, but you didn't realize it while writing a document.

There are also a lot of things that on paper, look like they should work flawlessly.  But once you implement them, it's obvious that they're completely broken.  It's unlikely that you'll ever detect that while the ideas are just on paper, but they could force enormous redesigns of large swaths of content once you try to implement them.

Quizzical has some great advice there, Mike.

You've got everything written out, so now it's time to start trying out what you've created. GameMaker is a great free tool for testing out ideas. You could even raid your board games for dice and pieces to start testing it out that way. Have other people playtest the various systems in your game. See what they are doing and find out WHY they are doing it. How you may perceive the mechanics being used could be radically different from how others actually use them.

You'll find you have a ton of refining to do at that level. After that, it's getting the various elements to work together in the same enviroment. Test, change, refine.

 

Yeah, understood. I have 15 years of data programming experience, in which I always believed in a more procedural base approach of building projects unlike todays more object orientated rail based systems. It leads to a modular approach in development that provides a very stable backbone. Things take a bit longer to develop this way but are so much worth it and mistakes don't happen and you never code yourself into a corner. (things are done, tested and completed, and moved to the next problem) So that has helped tons with the initial design of the game.

And no I have not everthing written out yet :D Its a major task with tons yet to do, but i have hundreds of hours of theory and design completed, as well as lore and other stuff...

Wait... 15 years as a data programmer. So you're an adult?

Originally posted by Satcho
Once you have something "tangible", put it up on http://www.kickstarter.com/ -- that'll get you funding.

Yea right. That's just shuffling money around. You still need the big 3: Audience, Publisher, Studio.

Originally posted by TigerAero

Originally posted by Satcho
Once you have something "tangible", put it up on http://www.kickstarter.com/ -- that'll get you funding.

 

Yea right. That's just shuffling money around. You still need the big 3: Audience, Publisher, Studio.

You probably could skip the publisher unless you are looking to do physical box product.

Originally posted by Loktofeit

Originally posted by mikecackle

Originally posted by Loktofeit

Originally posted by Quizzical

A lot of the details that need to be filled in don't become obvious until you have a game working with a lot of features already implemented.  Once you have the game sitting there, it's completely obvious that you have some major components that are completely missing, but you didn't realize it while writing a document.

There are also a lot of things that on paper, look like they should work flawlessly.  But once you implement them, it's obvious that they're completely broken.  It's unlikely that you'll ever detect that while the ideas are just on paper, but they could force enormous redesigns of large swaths of content once you try to implement them.

Quizzical has some great advice there, Mike.

You've got everything written out, so now it's time to start trying out what you've created. GameMaker is a great free tool for testing out ideas. You could even raid your board games for dice and pieces to start testing it out that way. Have other people playtest the various systems in your game. See what they are doing and find out WHY they are doing it. How you may perceive the mechanics being used could be radically different from how others actually use them.

You'll find you have a ton of refining to do at that level. After that, it's getting the various elements to work together in the same enviroment. Test, change, refine.

 

Yeah, understood. I have 15 years of data programming experience, in which I always believed in a more procedural base approach of building projects unlike todays more object orientated rail based systems. It leads to a modular approach in development that provides a very stable backbone. Things take a bit longer to develop this way but are so much worth it and mistakes don't happen and you never code yourself into a corner. (things are done, tested and completed, and moved to the next problem) So that has helped tons with the initial design of the game.

And no I have not everthing written out yet :D Its a major task with tons yet to do, but i have hundreds of hours of theory and design completed, as well as lore and other stuff...

Wait... 15 years as a data programmer. So you're an adult?

 

That's debatable ;D

Originally posted by Loktofeit

Originally posted by mikecackle

Originally posted by Loktofeit

Originally posted by Quizzical

A lot of the details that need to be filled in don't become obvious until you have a game working with a lot of features already implemented.  Once you have the game sitting there, it's completely obvious that you have some major components that are completely missing, but you didn't realize it while writing a document.

There are also a lot of things that on paper, look like they should work flawlessly.  But once you implement them, it's obvious that they're completely broken.  It's unlikely that you'll ever detect that while the ideas are just on paper, but they could force enormous redesigns of large swaths of content once you try to implement them.

Quizzical has some great advice there, Mike.

You've got everything written out, so now it's time to start trying out what you've created. GameMaker is a great free tool for testing out ideas. You could even raid your board games for dice and pieces to start testing it out that way. Have other people playtest the various systems in your game. See what they are doing and find out WHY they are doing it. How you may perceive the mechanics being used could be radically different from how others actually use them.

You'll find you have a ton of refining to do at that level. After that, it's getting the various elements to work together in the same enviroment. Test, change, refine.

 

Yeah, understood. I have 15 years of data programming experience, in which I always believed in a more procedural base approach of building projects unlike todays more object orientated rail based systems. It leads to a modular approach in development that provides a very stable backbone. Things take a bit longer to develop this way but are so much worth it and mistakes don't happen and you never code yourself into a corner. (things are done, tested and completed, and moved to the next problem) So that has helped tons with the initial design of the game.

And no I have not everthing written out yet :D Its a major task with tons yet to do, but i have hundreds of hours of theory and design completed, as well as lore and other stuff...

Wait... 15 years as a data programmer. So you're an adult?

Rofl !

Originally posted by Enigmatus
Concepts and ideas don't mean jack, regardless of how elaborate and detailed they are until they are put into actual practice.

So what are you saying, no one should conceptualize anything because they don't mean jack? Looking at my notes here, not acheiving to be jack guess I can move foward.

Not even a rickroll.

/sigh

Originally posted by mikecackle

Originally posted by Enigmatus
Concepts and ideas don't mean jack, regardless of how elaborate and detailed they are until they are put into actual practice.

So what are you saying, no one should conceptualize anything because they don't mean jack? Looking at my notes here, not acheiving to be jack guess I can move foward.

No I'm saying that unless you put your ideas into practice, the idea is just that - an idea. Useful for setting groundwork, but not much else until the actual pieces are put down.

I dunno, I'm terrible at explaining what I'm trying to say, so maybe something got lost in translation.

Originally posted by Enigmatus

Originally posted by mikecackle

Originally posted by Enigmatus
Concepts and ideas don't mean jack, regardless of how elaborate and detailed they are until they are put into actual practice.

So what are you saying, no one should conceptualize anything because they don't mean jack? Looking at my notes here, not acheiving to be jack guess I can move foward.

No I'm saying that unless you put your ideas into practice, the idea is just that - an idea. Useful for setting groundwork, but not much else until the actual pieces are put down.

I dunno, I'm terrible at explaining what I'm trying to say, so maybe something got lost in translation.

Conceptualization of say PvP warzones would be an issue of difference from paper to action, but a valid reason of why people are there doing it does help its purpose.. Take SWTOR for example..At launch, no one really does warzones, becaues there was little point to it.. so they introduce dailies, to get people there.. they expected people to show up just because the game was star wars, and sith vs republic.... That was fail... Concept can indeed evolve purpose correctly...
They failed from the drawing board in this case, which is why you need theory... I excel at theory and analyzation, but forum posting is cheap, its time to move forward into action :D

Being a gamer is very poor developer qualification...

Your preposition of "real gamer" is just silly, your ideas are no better than others.

Originally posted by mikecackle

I excel at theory and analyzation, but forum posting is cheap, its time to move forward into action :D