Hi,

After almost two weeks of reading in this wonderful website and other research, I am in the process of making a career plan for game development in my future. The leadership and community here has really helped me.

This body of planning is a rough draft which I wrote over the last few hours this morning and I would like help in guiding me to realistic and effect improvement of my plans.

If anybody actually has the time to read all this, you may be blessed to do so. Please offer your thoughts and feelings on this. I welcome any and all criticism and suggestions.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here is my very basic career flow with future goals until end of 2014 expected to be only very simple accomplishments:

2006 - 2012 : Modding games and simulations, learning about computers in general, and sharpening 2D and 3D art skills: Goals all accomplished.

2012 - 2014: Learning game design, website development, and game development. Learn C# by making my own office suite and game dev tools, learn website language through making my own website, learn probably both C++ and Python for game functionality, and learning other programming to tie these together. First efforts will mostly be open source here.

2014 - Indefinate Future: Develop and Publish Indy Games.

-----------------------------------------------------------------------------------------------------------------------

Here are two more sections: What I want in games and my goals for the next 2 1/2 years.

Game Fundamentals - Minimum Features
---------------------------------
The first thing that I feel should be stated is my goal for my first couple games to include all the fundamental aspects which I like in a game. Though the games might be simple in 2D and 3D content, I want them to have a relatively broad but thin technical foundation for future development of games. The technical branches will be fewer and shorter in my first couple games so as to focus on game structure primarily because the purpose of them is for learning and not end user appeal.
Here is the list of things that I want in my first couple games:

End User Environment
--------------------
First person shooter.
Reload.
Change weapons.
Aim and fire.
Shoot from the hip.
Magnification such as scopes and binaculars.
Crouch, walk, jump, run, or dive.
"Rag doll" wounding or kill
Head pivots with user view.
Pivot at the hip for quick response firing.
Strategy option.
Tactics option.
Ability to switch between strategy and tactical command on the fly.
Global map or regional map.
Tactical map
Dynamic Gameplay Objects

Sky with volumetric clouds.
Water which is dynamic and has depth.
Land with variety of terrain.
Air, land, and water user-operated vehicles.
Basic physics, independent of graphics brand names or API, such as gravity and ballistics
Triggers
AI
Unexpected circumstances, often created by coding randomization

Art Genre
---------
3D environement
Sprites, Decals, and hard edge 3D objects
1st game using textures
2nd game using textures and a few rendered surfaces.
1st game using non-living animations
2nd game using both living and non - living animations
Damage models
Collision detection
Effects

Game
----
Offline only for the first game
Offline and online play for the second game
OpenGL for first game
OpenGL or DirectX user choice beginning with 2nd or 3rd game
Runs well on middle priced laptop or notebook computers, with or without dedicated graphics cards
The first one or two games will be open source and after the bugs are pretty much gone, I will share the source code for the first one or two games to the communities which support me in their design and development.


Long Term Features
------------------
The list is very long here, but I will mention night vision as being one detail example and portability of the game to Xbox or Playstation as an important long term goal.

[color=red]-------------------------------------------------------------------------------------------------------------------------------------------------------------------

2012 - Research, Learning, Foundation Laying Stage - August through December 2012
----

August 2012 - Research Stage
----------------------------
Read and ask questions to gain information to begin C# programming the following month which is September 2012.
Collect learning information needed to make tools in the C# programming language. The first C# project of mine will be of work on an open source game developer office suite beginning in September 2012.
Make a flow chart for development of the office suite, subject to evolution in the future.
Choose an Open Source game engine as the basis for learning the fundamentals of computer game development. This is the game engine which will be the focus of designing my first game beginning in October 2012. After that first game, following games will be developed by me and not merely designed.
Open source game engine will allow tools to be made in C# and implemented games in C++ or Python.
Begin research into website design languages.

September 2012 - Open Source "Office Suite for C#" Development Begins
--------------------------------------------------------------------
Install and configure the previous chosen open source game engine. Begin learning it and planning a flow chart for game design of the first computer game. Make final decision on the theme of my first game to be designed.
Begin programming the office suite for C#, evolution being for indefinate time. Office suite development will track the needs revealed by the open source game engine which is installed this month.

October 2012 - Game Design Begins
---------------------------------
Designing of the first game begins here. Using the open source game engine chosen, the design of my first game will continue until the end of 2012. Office suite development will roughly follow game design needs.

November 2012 - Website Planning and Programming
------------------------------------------------
Planning a flow chart for website development begins here. Programming starts immediately after flow chart is completed. Flow chart may evolve with time. Website will evolve in relation to office suite. Website development deadline and launch is the end of 2012.

December 2012 - Programming is Intensive
----------------------------------------
Some effort will be made for learning but more effort focused on accomplishing the following results:
1) First game design completed by the end of 2012, being certainly very basic.
2) Basic office suite in C# constructed and being used by the end of 2012, even if it is very simple.
3) Website developed and online, only in short and easy structure.

Important Reminder: Goals are for a basic foundation perimeter, not even a whole foundation, to be laid by the end of 2012. Balancing the broader evolution is most important for 2012 rather than amazing details. Remember the fundamentals of the game and don't spend too much time on game details in the early stages.

2013 - Open Source Game Development, Website Homebase Creation, and Open Source Game Developer "Office Suite for C#" Launch
----
Whatever complexity of this game engine and game, it will be published as open source to the community which supported me in their development.


2014 - Private Game Engine and Private Game Development - private and proprietary creation begins here.
----
The goal is to publish a proprietary game by the end of 2014, be it a simple or complex game.
Formulating a game development plan for the next year or two after 2014 must be completed in December 2014 (for a specific game to be created next).

[color=red]-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Summary: My next 2 1/2 years will be spent in learning the basic structure of games, game development fundamentals, and launching the custom made systems which will eventually allow me to become an indy game developer, even if the accomplishments are all only simple. A balanced approach is more important in early stages over a polished, complex game. Creating the system is more important than developing an advanced game in the early stages.


3Ddreamer - "Look! The dreamer is coming!"

I always thought that if one love to make games he/she starts by actually making a game, not by learning stuff that might or might not be useful in future There is nothing about your fun, desire, dreams, tension in that post. If you are looking for a career, drop games, these are not paid well enough to justify it. If it is to be boring at least make it well paid (like accounting).

Generally, basicly all people who actually made games I know, made these because they wanted other people to have fun, and/or to let their creative juices go wild, sometimes to drop their boring office job. I have never heard about anyone starting by setting a goal like portability to Xbox or Playstation (I also have no clue what that would matter to anyone).

If you are able to postpone making a game for 2 years, then probably making games is not what you like the most on this planet (and if making games is not what you desire the most it is a stright way to despair and wasted effort).

I would say that you're overthinking this. Just make games, that should be your only goal. Start by making something that you really want to make, not some dinky tetris clone or your own office suite. You will naturally be forced to learn everything that you really need to know in order to complete the project.


And do you really think that you're going to stick to your schedule? Shit happens, and it's not going to pan out at all in the way that you think/hope it will.


Just do it.

Tool making is something I like to do. This will be a part of my work. Being only a game maker has nothing wrong with it, but I want more.


Though the borders of game maker, game designer, and game developer are often at least a little blurred, there are characteristics which can define them.The distinctions among occupations are important I feel.

A game maker could potentially use all the content, tools, and other things created by others to make a new game. Learning languages, creating 2D or 3D art, and making tools are not absolutely needed for the game maker.

The game designer is a little more, typically working for someone or a company, possibly under a game developer, and leads the artistic effort of the game. Sometimes the game designer makes some tools but always relies heavily on previous existing things. Game designers often use game engines already created by a game developer.

Many game developers create their own tools for their games and game engines. Some developers are all in one, a sort of one person band, as a 100% indy developer, but some have a corporation over them and/or a game designer with a team of artists underneath.


Creating my own tools will be very useful for learning languages, making some game types of features only available through expensive tool programs or even whole suites, and creating tools will cause me to examin deeper the inner workings of games in order to be able to make the most difficult changes and improvements in the game.

There is nothing wrong with only making a game, but I will enjoy creating a game development system.

It is all a matter of what a person wants, I believe.


3Ddreamer

Got dream?

Frankly, I think you're vastly overestimating what one person can reasonably accomplish in the span of a couple of years. I also agree that you're overly detailed in your approach; the way real life works, you're extremely likely to get 3 months into this and get sidelined - either by learning something new and exciting that takes you in an unpredicted direction, or by external factors, or even because you suddenly realize the scope of what you're trying to do.

Projects are hard enough to complete as it is. It's a serious mistake to set yourself so many exacting goals, especially while you're still learning. Pick one thing at a time, and don't pick the next thing until you're done with the first one.

In my career I've taken many detours I never could have foreseen, and all of them I am deeply grateful for. If I had tried to plan my path early on, it would have looked nothing at all like what I actually wound up doing. I think this holds for at least the majority of people I know, if not all of them.


My advice would be to select one project to do over the next year. Make it a goal to get it as complete and polished as possible, no matter what it is. Pick something that will stretch your skills and be a little demanding - that much you're on target with - but aim to complete one thing and do it very well. Otherwise, you will face one of two outcomes: either you will create lots of subpar work and be dissatisfied with all of it, or you'll get buried in something and create nothing of value at all. Focus is vital.

I emphasize completing and polishing a single project because that's far and away the most difficult part of being a good developer, in any field. Anyone can bang out a dozen shoddy prototypes - it takes dedication, patience, and discipline to drive a project to completion, and that set of skills is far more important than just hammering around in code.

Start by making something that you really want to make, not some dinky tetris clone or your own office suite.

Actually, when you're just starting out, a "dinky tetris clone" is probably the best thing to do.

This is piggybacking on what ApochPiQ already said (more or less): One complete project is worth several fancy demos. The ability to "get it done" is essential, and it's unlikely that you'll ever attain that ability by pursuing an overly ambitious set of goals, especially when you lack the basic programming skills.

You learn by making games, so you have to make games, not work on some "dream project" for years.

Start with simple retro knock-offs; You will learn plenty.

Okay, guys

I see the unpredictability. What I want in the long term won't change much, I feel. However I do see that many things could change along the way in the details and timing.

How about making a much more general plan for only the next month? Does anybody see complications with this idea?



3Ddreamer

The pitfall there is twofold.

First, if you only learn to maintain project discipline in one-month increments, you will flounder and burn out hard as soon as you land in an environment that demands a project whose lifetime is measured in years.

Second, a month isn't long enough to do anything interesting, not at this point in your growth.


I stand by my earlier statement: pick a year-long project, and go do it. Put as much love and polish as you can into that project, but limit it to exactly one year. If you don't have enough time in a year to finish your goals, learn the difficult but necessary skill of knowing what to cut back on. If you have extra time, polish it more - there's always room for improvement.

Okay, good, there Apoch - one year sounds reasonable to me. I went from one extreme to another, looking for more help.


What specific time frame for planning would you other people make? Please be specific. There is nothing wrong with agreeing or disagreeing with Apoch. You don't like my extensive original plan and that is fine but I would like to know what specifically you would do? Here is another natural train of thought: How has your planning habits effected your accomplishments? Is there anybody with big plans who failed? Is there anyone with almost no plan who hit the bit time here?

I have another question for everybody: Don't you think that a multi-year school program for gaming design would have an agenda far more extensive and detailed than my original proposal? I suspect that none of you thought of making that comparison instead of comparing my plan to your own standards. Please do not misunderstand here, because I realize that there is a wide variety of planning styles and any one of them might work for a hard working person.

No offense taken and none intended, but I feel that these are all important questions.


3Ddreamer