mechanics is something like gameplay right? what are the other 3? and are there some other words that fit in the same category that game desicgners should know? im a beginning game designer, and want to make a profession out of it.
From what I can tell the post seams to want to know how you handle yourself more then how you design games. Though they are quite closely related. The position of game designer is more then likely the most sought after job in the industry and also requires the most talent. You need to know how to do everything. In general you need at least these skills:
You need to plan everything and keep track of everything. The GDD and TDD will create your game in text. Everything is documented from hours worked each day to the x,y location of the menu buttons on the main menu yet alone the file structure, naming conventions and assigning who does what. This is most likely the hardest part of the job
It's one thing to be able to assign everything and a completely different beast in keeping track of everything. You are in charge of knowing where everything is at any given time when it's coming in and where it is stored once it is in. Also you need to know what build you are on and when the next update will be.
You must be able to explain what you want, why you want it and when you want it. Your team can not read your mind so you must show them what you mean. Videogames tend to be very visual so we draw a lot of pictures and graphical representations in our documents.
Also you must know the lingo of all the divisions (a general summary would be art, modeling, programming, testing) so that you can effectively know what is going on and suggest ways to get around bugs.
When things go wrong, and they always do, your in charge of fixing it. You need backup plans for everything and then backup plans for those backup plans.
Here is another place where knowing all the fields works great. Say the engine you are using only supports 96dpi images for some reason. The programmers will know that there is a draw error along the lines of "file structure not supported" Thats clear to the programmer but if you tell the artist "your file structure is not supported" you will more then likely get something like "well can't you program it to be supported"
But because you are a awesome Lead your know what the error means and you can tell your artist "Your file structure is incorrect, please make sure when you save it out that the specifications match that on the GDD"
Your also in charge of scheduling due dates for assets and builds. This all needs to be documented and planned so that everything moves along smoothly
ah, this helps.
so concept work and mechanics are more the designing skills, and behaviour and structure have to do with the group and how you lead it?
While Justin is absolutely right about the skills needed to be a designer, I'm not sure that's what they're asking for in particular. If you look at it more literally, it seems what they want is documentation that shows concept work (development of concepts, conceptualizing environments, characters, etc), structure (I assume this means structure of the game, perhaps organizational planning of milestones, etc), mechanics (gameplay), and behavior (how different things work in game in relation to one another. For example, writing a flow chart for a choice-based story-driven game).
This is just my take on it. I could be completely wrong. It wouldn't be anywhere near the first time. ;)
The best thing to do if you're unsure is just shoot them off an email and ask for clarification. Ask if they're looking for certain documentation in particular (concept documents, design documents, schedule and budget documents, etc), and what exactly they mean by those terms. Better to ask and have it be an answer you already assumed than to assume and be thrown into the slush pile for irrelevance.
|All times are GMT -8. The time now is 09:46 PM.|
Powered by vBulletin® Version 3.6.9
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.