Timeline for Game Structure in depth [closed]
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2014 at 20:05 | history | closed |
Anko MrCranky Sean Middleditch CommunityBot |
Needs more focus | |
| Feb 7, 2014 at 10:02 | review | Close votes | |||
| Feb 8, 2014 at 20:05 | |||||
| Feb 7, 2014 at 7:08 | comment | added | Patrick Hughes | Necessity is the mother of invention. | |
| Feb 7, 2014 at 3:36 | answer | added | House | timeline score: 1 | |
| Feb 7, 2014 at 3:35 | comment | added | Lysol | Difficult to answer. But in the few years that I have been programming games, all I can really say is that you pick up techniques as you go. When I made my first game, the code was totally garbage. But as I went along, I developed habits. Some of them I picked up from other people by looking at there code. And over a period of time, you are basically a mixture of a bunch of other programmers in addition to habits that you personally have developed. Short answer: There are about a million ways to program the same thing. So yes, everyone has their own way. There's no right way to do something. | |
| Feb 7, 2014 at 3:07 | history | asked | Trowen Nagbe | CC BY-SA 3.0 |