jdc said:
Add information and your though maybe we could organize a file width all these information
They are all asked every few weeks. We have found over the years that FAQs, Wikis, and similar don't work, people still ask anyway.
So, burning through your questions quickly:
> what engine to select
Pick one that matches your project. An engine like RPGMaker is probably a bad fit for a shooter game, and UE4 is probably a bad fit for your chess game.
> How to structure a project
Depends on your project.
> Rules to learn in development
It takes a lifetime, learn as you go.
> Industry concepts or guides
It takes a lifetime, learn as you go.
> Game design theory
It takes more than a lifetime. There is no useless knowledge. Game designs cover everything! World religions, world languages, cultures, color theory, medical games, historical games.
> Programming theory
It takes a lifetime, but a four year Computer Science degree covers the basics
> What programming language to select
Depends on your engine.
> When ask for help in your project
Read this.
> How to build a design document
Doesn't really matter. Much like war, planning is essential, but plans themselves are useless. I think of it like a map for a big party: You need to specify the destination, but everybody must take their own route from wherever they were.