next »

[jdc]

How about organize developing steps for people is starting?

See people asking theses questions when i start a couple of years a go…

Any one can suggest but i come up width these:

what engine to select

How to structure a project

Rules to learn in development

Industry concepts or guides

Game design theory

Programming theory

What programming language to select

When ask for help in your project

How to build a design document

Develop in Open source

Add information and your though maybe we could organize a file width all these information

[michaelplzno]

Most of this stuff is too complicated for someone starting out and only useful for really big projects. The best advice for someone's first project is to do something very small, like a game someone would play for 10-30 minutes. Most newcomers can't even do that. Thinking about design docs and open source and so on is just distracting.

[Thaumaturge]

I also think that at least some of these questions might be a bit conditional for inclusion in a general one-size-fits-all document. For example, the selection of language might depend heavily on what the person in question already knows, and the choice of engine might depend on their goals, preferences, and other matters besides.

[brainwipe]

My advice is to find a YouTube tutorial series that is making the kind of games you want to make. Then find the simplest tutorial example of that sort of game and follow it to the letter.

I'm not sure that warrants a document but I wish you luck!

[Demi Dawnfall]

I also like methodology and fear that I also try to find a 'one-size-fits-all-method' but taking what Thaumaturge and michaelplzno noted, maybe the first step is to determine how big your project is and how much time you have to work on something, then determine what steps you can cut out from the ones you've noted?