   mathius20
  Recently I have been working on an rpg, and everything is going fairly smoothly except I keep on feeling like theres alot better way I can do something as im writing it. I want to design everything better, make it more organized, more self-sufficient. Like if each part of the engine(sound, graphics, etc) was a module that is loaded and unloaded, and it took care of its own memory. My question is are there any tutorials on engine design? I think it would help me if I saw more examples of how people design their engines. I just don't want to hack this together, and then have alot of problems when I want to implement something. Thans.   
  Here's what I found in GameDev's tutorial section, under 'General Programming', hope it helps!Elements of Programming style -- The C++ style GuideHow to best arrange C++ source and header files And more important the Enginuity series:Article #1Article #2Article #3Article #4Article #5;  Game engine design, or even program design in general is probably something you will want to learn-by-experience with. Keep going with your engine, if you find ways to improve it and you can easily modify it, do so, otherwise carry on and remember it for next time. I must have started about...4 game-engines by now, and each one of them has an improving design, but I completely understand every choice in their design. Well thats what id do anyway xDHope that helps   ;  Thanks for the links, that looks really nice. Its just, I hate programming something that I know could be alot better, and make other things easier in the future. And because of that, I guess it ends up making me complacent:( Thanks for the advice though, and I understand the logic behind making mistakes, but I keep feeling like it would be better(and even easier) to bypass a few of those stages and start at a little higher level and design and modify the engine instead of starting at something thats not even an engine and working up.   ;Quote:Original post by Mathius20Thanks for the links, that looks really nice. Its just, I hate programming something that I know could be alot better, and make other things easier in the future. And because of that, I guess it ends up making me complacent:( Thanks for the advice though, and I understand the logic behind making mistakes, but I keep feeling like it would be better(and even easier) to bypass a few of those stages and start at a little higher level and design and modify the engine instead of starting at something thats not even an engine and working up.I ment to just look through them (particularly Enginuity) and see how they are layed out, and optimize your code accordingly. Just skip to the later articles in the seriesand give it a glance over. Guess I should be more specific.   