A good game stucture
Im just starting to make another game, but how does the structure of a GOOD (well programed) game looks like?
I will expand this topic later if needed!
----------------------------
^_^
If you mean the code structure you can always take a look at the Quake I/II/III sources...
Better code that is free will be hard to find i guess...
Happy coding!
// Jonas Ericsson
Better code that is free will be hard to find i guess...
Happy coding!
// Jonas Ericsson
while the algorithms used in the quake games might be good, the code itself is very far from being well-structured and easy to study.
I was wondering the exact same thing about general program structure. The only thing I have to study from right now is the "SimpEngine" in the back of the OpenGL Game Programming book... Seems very heavy on derived classes, virtual functions, that sort of thing. Anybody familiar with that code? Is it OK to study from, and base projects off of (as far as program structure we''ve been talking about)?
Wow, thanks for the ogre link, that looks great too! Also, my buddy passed this along to me, haven''t checked it out yet, but looks cool...
"Elements of a Game Engine"
"Elements of a Game Engine"
Try this book. Its not specific to games, but rather a general list of rules of thumb to remember while you program. I have found it to be a interesting read. (Its short too, so good for bathroom reading)
Enough Rope To Shoot Youself in the Foot:
Rules for C and C++ Programming
By: Allen I. Holub
Enough Rope To Shoot Youself in the Foot:
Rules for C and C++ Programming
By: Allen I. Holub
quote:Original post by Themonkster
what book?
Um, which post are you reading??
Enough Rope To Shoot Youself in the Foot:
Rules for C and C++ Programming
By: Allen I. Holub
It''s right there.
pan narrans | My Website | Study + Hard Work + Loud Profanity = Good Code
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement