Step 1: Learn the basics of a language (I'm currently learning python - seems relatively easy after a few hours ^_^)
Step 2: Then I guess I should learn DX, because based on what you people have been telling me, DX is a better solution to game prog. DX is the most common game programming language right?
Step 3: Mess around with some source code, like Quake or Torque.
Step 4: Plan my game more in detail (sadly, I already did that, thinking that was step one :D! How dumb of me)
Step 5: Learn more code like C++ or OpenGL (should I stay away for OGL? Seems like a bad place for a beginner) based on what my game seems to require.
Step 6: Maybe with a few people, start my first attempt. Learn from my failure (if it will <-- most likely)
Step 7: Keep practicing, producing, and of course...practicing
Step 8: Within a few years (if I'm lucky, months) I can start realistically think about posting on Help Wanted.

Anything missed out here?

BTW:

One thing I would like to point out is that as you progress and learn more, many of these questions that you ask now will naturally become clearer to you.

I'm realizing what you mean. Before I read some C++ and Python books, I never really understood what a compiler was, or what an interpreter was. (Interpreter reads what you type and translates it to a form the computer can understand, while the compiler compiles or builds an executable file of what you programmed - Right?)

To answer any doubts about my previous programming/GD experience:
I know more about mesh, tiling, mixing 2D w/ 3D and skyboxes than I know about iostream or /include stuff :D
I've been through the GD Beginners Places, but I find (advance apologies if I'm being too blunt or rude) people in forums like this more helpful than an online article/webpage.
[Edit] I've had my share (2-4 years) of simple WYSIWYG programming (is it really considered programming?) I found that quite boring - its very limiting. 2-D (sometimes 3D) game engines like The Game Maker (by Mark Overmars) are really only worth for 2d games like tetris or scrolling shooters (no offense)

Anyways, thanks for all your help, people. Python, DX, mess around, practice.

Hey, Big Bright Idea from the Big Noob. :)
If I were to actually start a good team with a good game in mind, I suppose I could stick with, perhaps, audio/sound or graphics art, and leave the programming stuff to more experienced people. Right?

I suppose there is a certain amount of fun and respect in mastering different programming languages.

Quote:
Anything missed out here?

Not to be too critical, but it seems like you're missing quite a bit still.
Steps 4-7 are likely to be repeated a dozen+ times and even a few years is quite optimistic.

And directX is not a game programming language. It simply displays graphics, plays sounds... you'll still need to create the entirety of the game and almost all of the infrastructure of the game yourself.

Yup, I suppose practicing and (learning from)failing will probably be my most important and time consuming steps. But for the DX: I believe I make a game engine and map editor through DX, and then proceed with the actual building of the game (i.e. adding audio, video, objects, plot etc.) in the game engine/map editor. Right?

Hmm, advice taken. But to use existing engines/editors, you still need to learn programming right? Which language? I suppose it varies from engine to engine?

Quote:Original post by DJ N3X
If I were to actually start a good team with a good game in mind, I suppose I could stick with, perhaps, audio/sound or graphics art, and leave the programming stuff to more experienced people. Right?

for the love of God, don't go into that mindset. People who can actually help you accomplish something won't jump on your project - good as it may be - unless you can actually show them a working test version. You need to convince them that you are capable.