Hello!

I'm new to this forum, but not entirely new to Game Development. I'm studying Media Arts and Programming at university, with focus on Game Development and I have been involved in small indie Projects before, however not as Game Designer yet. I have read a few Books about the subject, but there are many questions still left open for me.

For example, I am looking for a book or resource that tells me everything about Game Loops, how to write Game Design Documents correctly and how to describe Game Mechanics.

Also I want to know, what kind of Maths do I need to know as Game Designer? I wish to be schooled in Balancing as well, because I think this is important if I ever want to work in that field.

Last but not least: How does someone coming from university find a job as Game Designer? 90% of the Job requests I read about are for experienced Designers only ... which makes me a little sad, because: How am I supposed to become experienced, if noone ever allows me on their team? :C

Thank you for your answers in advance!

Are you sure you want to become a games designer, or a games developer?

These are my understandings of the role - bear in mind i am not a professional games developer or designer but i am a professional software developer and some of the skill sets overlap so these are purely my observations, feel free to correct any inacuraccies...

A games developer needs to be able to work on complicated programming tasks with little supervision, needs to pay tight attention to deadlines and needs to be highly motivated and deeply knowledgeable with regards to his craft. They must also have the desire to continually develop their skill set.

A games designer on the other hand is the person who started out as a games developer. He has been promoted up through a games studio and generally is in some position of team leadership. As most games are generally designed by more than one person, it is not a role of a lone ideas man who says 'i have this great idea for a game, everyone jump to it!' far from it.

So, back to the question - which one of these roles are you aiming to fill?

Wow, first of all, thank you for the fast response! I am aiming to fill the second role, if I can that is. Up until now I have been doing different parts of Game Development. On our current project at Uni I work as Level Designer / Programmer, but I've been 2D artist before as well. So .. I know a bit about the Development of Games in general, however I kind of wish to also know how to plan said development ahead, and how to bring ideas to paper.

But thank you! I didn't know that you couldn't become a Game Designer as entry level job, and that you usually start as Developer before this - although it makes perfect sense that you can't design a game without being able to actually create one.

Hi, I don't visit this forum very much. I am a Technical Games Designer, and I worked at Riot Games for quite a few years before recently founding my own indie studio (Skyborne Games).

however not as Game Designer yet

How am I supposed to become experienced, if noone ever allows me on their team? :C however not as Game Designer yet

You become a Game Designer by first believing that you are one. Don't let anyone, including yourself tell you otherwise. To become a good games designer, you need experience making various types of games. If you're in a Game development programme in University, that's the best place to form small teams to tackle fun game projects. Even if you don't have some of the technical / artistic skills to contribute to a collaborative digital project, you can always start being a games designer by making board / card games.

If you want to be a games designer, there is very little reason not to be making games right now, that's how you beat the catch 22 of becoming a games designer professionally.

For example, I am looking for a book or resource that tells me everything about Game Loops, how to write Game Design Documents correctly and how to describe Game Mechanics.

There are some pretty good talks on GDCVault, I highly recommend the Hearthstone design talk, and the George Fan's PvZ talk.

That aside, it's extremely EXTREMELY important that you balance this out with real experience, the real experience is probably more important than reading the books. (Real experience of playing and analyzing both your own and other people's experiences, AND making game experiences and analyzing other players' perspectives)

The best design books out there teaches you frameworks for understanding / analyzing great games, but that alone doesn't mean you can make great games. Why? Game development evolves rapidly. Game design must evolve with it, to solve new problems that a static book won't be able to keep up.

Also I want to know, what kind of Maths do I need to know as Game Designer?

As a Technical Games / Systems designer, I can tell you that the more math and engineering you know, the more tools you have at your disposal to solve design problems.

Having a solid understanding of probability is a MUST for systems design.

Having a solid base in Calculus 3D / Physics has helped a ton when designing AI and physics based games.

The amount you know in math (& any other discipline really) will limit how you as a Games Design approach and solve various problems.

I hope you have a ton of fun on your journey as a Games Designer!

I like issfire's advice. Making tabletop games is a great training ground for being a video game designer. You can learn a lot about game mechanics, balancing, and documentation without the distraction of getting it implemented on the computer--this is especially true if you are not already a pretty handy programmer. This is where I start all of my game design students.

However, to really do it right you need to actually know something about tabletop games... if your board game experience pretty much starts and ends with childhood games like Monopoly, then you'll be like someone who is trying to make a video game having only ever played Pac-Man. There's a tabletop game renaissance going on right now, and a lot of amazing games to be played (I'm happy to post a list of my current favorites, if any cares to know). If you will forgive a bit of self-promotion, I just had a book published on this subject, Tabletop Game Design for Video Game Designers. It focuses much more on designing game mechanics than on programming... and it has a pretty good chapter on probability.

I wouldn't worry too much about game design documents. They're important, sure, but I think they're a distraction when you're just starting out learning about game design. They become useful when you start collaborating with others making a game. Incidentally, I think using a wiki as a GDD works much better than a more traditional GDD along the lines of what are typically included in game development books.

There are so many ways to the field. The road can be so curved and variated that i can only recommend you to read on the internet or in books or watch videos to get your answer. But im afraid the answer isnt going to be one and a simple one............wich i guess can be both reassuring and frightening to hear