Designer and Conceptualist

Started by
16 comments, last by Paul Cunningham 23 years, 2 months ago
Ok, we''re hear to discuss design but how about conceiving game idea''s, this has to be an extremely important issue too. As fun as it is conceiving fantastic new idea''s for games it''s also crucial to get it right - forthought. Who would want to work in this industry if there were no decent concepts for games being brought to light and all we saw was a battle between companies to design the same old games better and better and produce more effecient code and stunning graphics. So why isn''t the field of Game Concepting taken more seriously in this industry. Why don''t we have a specialised field for this area? I''ve also heard a lot of talk about team conceiving or having everyone in the "team" putting their bit into the game. This has to be the worst thing in the world one could do. Conceiving a game in most cases require a vision, it just seems ridiculas to say that a large number of people hold the same vision becuase this isn''t true and we all know that. You want to know why all the old games were so good - it''s becuase of the Concept and the concept was brought together by one person. Its always one person becuase that''s how it has to be if you want to be innovative. Sometimes that one person is a creative type or logical or even a little crazy or what not but when it comes to conceiving a game it has to be done by one person. A designer doesnt need to know everything about code, they just have to have an appreciation for its limitations and how those limitations affect features they may wish to include in their design. - Drew
Advertisement
Paul,
Interesting point. What about the concept of many people inputing their little bit, but one person making the final decision? One person cannot know everything, but having one person get input from many sources before making a decision is logical. It''s sort of like in Star Trek where the captain gets many opinions from the crew before making a final decision.

Maybe I''m totally missing the point though.



http://www15.brinkster.com/nazrix/main.html

"All you touch and all you see is all your life will ever be --Pink Floyd
Need help? Well, go FAQ yourself.
Need help? Well, go FAQ yourself. "Just don't look at the hole." -- Unspoken_Magi
Fair enough for those who like to work in this fashion Nazrix but these sort of setups can create vunerablity for the person conceiving the game. If you want to concieve a game you will know it - you know what i''m saying otherwise you''re just making a salad with the best bits available. What i''m more talking about is the whole picture. I''m a little worried at this point in time to say that this is a purely creative effort as its easy to argue that some games don''t require any creativness to make and i don''t want to get side tracked down that avenue.

Screw it, ok lets say for a moment that the game concepts has to come from creativity and game concepts a based on innovation. So what do we have now, well if you take the scenario of having a lead game conciever with random input from the team then what do you have. Well i guess this is where we can actually says that there is or could be some sort of technique involved in this process because the conciever could be responsible for putting these idea''s together in a way that they see fit or is proper. Although it''s not quite the same a being motivated by your creative spirit via a amazing idea, thought or concept.

A designer doesnt need to know everything about code, they just have to have an appreciation for its limitations and how those limitations affect features they may wish to include in their design. - Drew
I can see your point about if the game being a more "creative" or original concept, then perhaps one person being the game designer is a good thing. If the game is just another Quake clone then having only one person is not so crucial because the ideas have already been laid out by other game developers.

So, if a person is trying to design a more innovative game I can see why having only one game designer can be useful. Thanks. Now I don''t feel like such a control freak for wanting to my current project all by myself



http://www15.brinkster.com/nazrix/main.html

"All you touch and all you see is all your life will ever be --Pink Floyd
Need help? Well, go FAQ yourself.
Need help? Well, go FAQ yourself. "Just don't look at the hole." -- Unspoken_Magi
I sort of agree with Paul on this one, having one person with a clear vision of the game is a definatly a good thing, that person (the conceptualist.. bit of a mouthful of a name isnt it?) would have a good understanding of the entire game, what it is supposed to "look" like, play like, etc...

There is however no reason why this person cant take other people''s ideas and either mold them to fit in his vision, or reject them out-right, I dont think taking someone''s suggestion as is and "adding it in" is a good approach, after all that person only has a small idea of the vision of the conceptualist, and no matter how well the conceptualist communicates his vision to the rest of the team, they are never going to have exactly the same vision it may come close, but still be off to some degree.

In the context of any game with a story, having one person with an idea of how the story fits into the world in which it happens makes the story far more believable from the players perspective.

The problem I think now-a-days is that games (especially RPG''s) and the teams producing them are becoming so large (rather than the 2 guys in the bask of a shed outfits that existed many years ago) that the conceptualist is having to try and communicate his ideas to so many people, and with everyone having a different view of that vision, that the vision is getting blured between the conceptualist and the player. Also with the small teams the conceptualist had more than one role, e.g. aritist or programmer, so where were he could have more control over how his vision was protrayed. Most of the games I consider great (all written for the old Spectrum btw.) were written by one, maybe two guys. (e.g. Lords of Chaos.. vision and game by Jullian Golloup... Dizzy.. Concept and Game by the Codemasters [when they were literally the Dar(l?)ing brothers]). The larger the team, the less "control" the conceptualist has over his vision. Ok so, yes he (or she lets not be sexist here) COULD stand over the modlers shoulder until he got that Droid EXACTLY right, but the modeler would soon become resentful...

I think, Paul dont know if u agree, that for the conceptualist to be effective in getting his vision across he MUST be involved with the development, and I mean activally produing something involved, rather than sitting back and commenting on whats produced involved. After all no-one knows his idea better than himself.

Just a point Nazrix, Kirk, or Picard, is trying to solve a problem, rather than creating a piece of sculpture (which is kind of like designing the concept of a game)..


I hope all that makes some kind of sence (its not easy posting when ppl keep bringing you work to do)
NightWraith
I see what you are saying, yes. The conceptualist would be about on the same level as the director of a movie perhaps?



http://www15.brinkster.com/nazrix/main.html

"All you touch and all you see is all your life will ever be --Pink Floyd
Need help? Well, go FAQ yourself.


Edited by - Nazrix on January 29, 2001 11:01:41 AM
Need help? Well, go FAQ yourself. "Just don't look at the hole." -- Unspoken_Magi
Probably more Script/Screen Writer and Director, after all a directors job is in a way to interperate someone else''s vision.

A conceptualist should know all the tiny ins and outs of the world, whats possible whats not.. etc.
NightWraith
Ugly truth time guys: The conceptualist idea is extraordinarily unlikely because game concepts themselves are a dime a dozen. I wish this was not true, as I''d love nothing more than to be a paid conceptualist.

You''ve got to put ego aside to see this. Otherwise you will not get this point.

Everyone has ideas. Everyone. Period. Even your granny and the neighbor kid down the block has ideas. Conceptualization is extraodinarily easy because it doesn''t face the rigor of proof. It is implementation that is the actual proof of a concept.

The world values results. Conceptualists / theorists project possible roadmaps, but they don''t take the hard journey themselves. This is why they are largely (and maybe rightly) undervalued. This gets worse the less value the end result has. Look outside game design to something like philosophy, or writing in the movie biz. Philosophers and writers are treated like crap, and paid / rewarded accordingly. Now game design, having a lot less value than, say, theoretical medicine or business planning doesn''t stand much of a chance.

As you move to designer, you get closer to actual results. But even most designers (AFAIK) aren''t kept throught the whole project unless they''re doing something else. Dedicated designers are so rare that we can probably name them all.

The more you actually produce results, the more you''re valued. The ugly thing about this is that some of the most vibrant and wildly creative minds are the dreamers, and some of the most boring and pedestrian minds are the actual doers.

In my experience so far, anyway.

--------------------
Just waiting for the mothership...
--------------------Just waiting for the mothership...
quote:Original post by Paul Cunningham

I''ve also heard a lot of talk about team conceiving or having everyone in the "team" putting their bit into the game. This has to be the worst thing in the world one could do. Conceiving a game in most cases require a vision, it just seems ridiculas to say that a large number of people hold the same vision becuase this isn''t true and we all know that. You want to know why all the old games were so good - it''s becuase of the Concept and the concept was brought together by one person. Its always one person becuase that''s how it has to be if you want to be innovative. Sometimes that one person is a creative type or logical or even a little crazy or what not but when it comes to conceiving a game it has to be done by one person.



I want to tackle this one directly: I think Valve''s CABAL design philosophy disproved this philosophy, that "many cooks spoil the broth." Half-Life was inarguably was inarguably a well executed, creative and innovative take on the FPS genre. Whether anyone personally liked the game or not, you''ve got to give them this credit. Yet is was a product were everyone in the company purportedly contributed ideas.

I think it''s an ugly example of elitism to value one mind over many others. If your measure of value for a concept is sales, then the company secretary might have a better mind for concepts then the chief designers. This is because the cost to dream is cheap. (Execution and communication, however, are different matters)

I don''t think, btw, that the old games were better because they had a concept guru: They were better because the lack of distraction caused them to focus on essentials. They had to do less with more, and this inspires creativity.

Today, our games exist in a world of financial, graphical and audio excess. If this changed somehow, you''d see a lot more creativity.


--------------------
Just waiting for the mothership...
--------------------Just waiting for the mothership...
I think the future for game designers is very bright actually due to the fact that the role of Game Designers is becoming more and more mechanical/technical by the hour. This allows people the ability to measure their value more easily compared to the creative roles.

Being a Game Designer is not neccessarily a creative task at all and this is whats worries me. All jobs that pay well are one that (if you were good enough) could be done by a programmed robot almost. But Game Designers are like Doctors, they''ve got to use there rationale to overcome certain obstactles - this is the reason the future of the Game Designer has a bright and prospectus future because it''s provides the right environment for interlect to proper. The mechanical or knowledge base that game designers are starting to work off (systems,structures,models and the like) gives Game Designers foundations like a doctors education. The problem with conceptualist is that they can get hung up on an idea and sometimes never let go - this is a big problem for starters in the commercial world.

The way i''m visualising the conceptualist is like a writer/director rolled into one. Although the game designer is also a director in many ways. But this comparision is really the wrong thing to do becuase we are not talking about the movie industry we are talking about computer games here. I don''t think a conceptualist may never work, if you can work out some sort of code of ethics for professional conduct for a conceptualist then you''re off to a good start in providing acknologment for their value and application.

quote:by Wavinator
I want to tackle this one directly: I think Valve''s CABAL design philosophy disproved this philosophy, that "many cooks spoil the broth." Half-Life was inarguably was inarguably a well executed, creative and innovative take on the FPS genre. Whether anyone personally liked the game or not, you''ve got to give them this credit. Yet is was a product were everyone in the company purportedly contributed ideas.

I agree and i did think of this while writing the original post. But what i need to see is whether or not they''ll keep up the good work with later titles. As i understand the history of the guys at valve was that they all came together in a rather planned fashion like a jailbreak one could say. These sorts of events can lead to suprising results. So as i just said, i for one will be watching how things turn out for them with game concepts down the line as things calm down over there. Was there one guy who had this concept and drove it home with everyone just listening and doing their bit becuase it sounded so damn good, who really knows.


A designer doesnt need to know everything about code, they just have to have an appreciation for its limitations and how those limitations affect features they may wish to include in their design. - Drew

This topic is closed to new replies.

Advertisement