Quote:Original post by JacksonEMG
Hey guys, I just had some questions on some terminology. Okay, I'm trying to become a game developer, but I'm having a hard time deciding which way to go. I think the definitions are throwing me off.

The way I see it is, that anyone who works on a game, could be a game developer right? This could be anyone doing the graphics work, engine work, or even the artistic/storyline work, right? So then, a game programmer is someone who actually programs the game, such as the game engine? But a game programmer also can use an engine to create a game. A game designer is someone who thinks up the levels, game play, and story, right?

Right.

Quote:Original post by JacksonEMG
Now, I want to develop simple games to build a portfolio, also as a hobby. I have goals eventually to work in the game industry. But I feel like there are so many different lines of work for a game that I need to pick something specific. So to be a game developing hobbyist, what do I need to know? I assume it is a "jack of all trades" kind of hobby?

Right. Another solution would be to team with someone that have a different set of skills.

Quote:Original post by JacksonEMG
I realize that in a programming aspect, knowing libraries is key. So OpenGL or DirectX would be a safe bet? Also, I should know at least one game engine like Ogre or Torque?

You don't have to know a library. But if you want to make a game, you'd better use one as it will save you some time. Of course, you're not required to do so, and you can still use DirectX or OpenGL (which are safe bets). A real game company is likely to use a middleware solution (and one you can't afford) but knowledge don't hurt.

Quote:Original post by JacksonEMG
Also, what math should I know? I've taken up to Algebra II and Discrete Math. I'm guessing I should know Trigonometry and Linear Algebra. Plus if I want to include Physics in the game, I should know some of that too? Also, are there any free websites or podcasts that do a good job of teaching these topics? I'm entering my senior year and I can't take any of these classes until after I graduate. Is the math really needed, or are there models and such out there that I could use in a game? How much does a game engine provide for me?

Your math level shall be as high as it will be required in order to program a game. You don't have to have a PhD (although that may help). You don't have to be able to read the Fermat theorem proof without using a pen and a paper to sort out everything. You just have to have a good knowledge of mathematics, including algebra and trigonometry. If you plan to do a lot of physics, some knowledge won't hurt (again).

Quote:Original post by JacksonEMG
I'm hoping that once I can create a few indie games, that I can have an idea of what to specialize in.

I apologize if I am just throwing endless questions out there. I'm trying to jump into game development on a budget, being a college student.

I appreciate any answers!

You came to the right place. You have tons of questions, we have tons of answers. Game development is a very wide subject, and these forum covers most of it.

HTH,

Quote:Original post by JacksonEMG
The way I see it is, that anyone who works on a game, could be a game developer right? This could be anyone doing the graphics work, engine work, or even the artistic/storyline work, right?

Yep, that's a pretty good definition of a game developer.

Quote:So then, a game programmer is someone who actually programs the game, such as the game engine? But a game programmer also can use an engine to create a game.

Right, a programmer obviously programs. They may be creating new technology or they might be working with existing libraries/engines/etc. Depending on the company in question these people might get a wide range of different additions to the basic 'programmer' title (engine programmer, gameplay programmer, UI programmer, whatever) or may just get a generic title.

Quote:A game designer is someone who thinks up the levels, game play, and story, right?

Here we're starting to get a bit tricky, there isn't really a specific clearly defined definition, and when one person refers to a "game designer" they might mean something entirely different to someone else's definition, and it's probable that they're both correct. Some designers just do the gameplay, others create levels, some do some programming. In general your defintion is acceptable though and you shouldn't go wrong thinking of the role along those lines.

Quote:So to be a game developing hobbyist, what do I need to know? I assume it is a "jack of all trades" kind of hobby?

Lots of people are experienced (to varying levels) in multiple areas of development, but you'll find that the majority have one or two specialties they're good at. Among indie and especially hobbyist developers it isn't all that uncommon to see one person do most or all of the work on a game for themselves, but it's also quite common for people to team up with others or hire people to fill in the areas they aren't good at themselves. In the industry the vast majority of people will work in a specific role.

Quote:I realize that in a programming aspect, knowing libraries is key. So OpenGL or DirectX would be a safe bet? Also, I should know at least one game engine like Ogre or Torque?

Ok, that's not a bad assumption - not all game programmers will neccesarily be working with those APIs much if at all, but familiarity with any of those would be an advantage to you. You should be able to adapt and work with different engines/libraries/middleware as needed, and experience with major APIs such as DirectX or OGL will never go to waste. If you choose to learn OpenGL and/or DirectX what you'll be learning will be more applicable to lower level development such as might be done when developing an engine or tools, where as working with an engine or framework will likely put you in more of a gameplay/physics/ui/etc programmer having a bit more to do with the actual game part. As a hobbyist you get to do a bit of all this stuff and I'd personally recommend working with existing frameworks or engines so that you can concentrate on getting actual games or demos workin. If you're aiming for an eventual job in indutry experience in either can't go wrong, but you'll certainly need the ability to work with existing (sometimes very expensive) solutions.


Hope that helps a bit, I'm sure others will have plenty to add to that and some responses to your other questions as well.

Welcome to the site! [smile]