• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
microlizard

A question about how to organize in code, a small game project

5 posts in this topic

I have been practicing with C/C++ as well as SDL 1.2. I can follow most tutorials, without too much problem. I'm ready to move onto a small 2D game project, but I am not sure how to organize the structure of the source code. The 2D game project would be a top down game like the original Zelda or Gauntlet. Does anyone here have experience with this? Any suggestions or example code could be helpful to me.

 

I'm working with Windows 7 64bit, mingw (32bit) with SDL. I am using Grafx2 and Gimp for simple test graphics. I'm not focusing on asset development whatsoever at this time, just code.

 

So to recap, I don't have an outline or structure for my source code because I just got to where I am and I have never done this before.

 

Any help would be great and small easy to read examples would be even better.

0

Share this post


Link to post
Share on other sites

I forgot to mention as a side note. I am looking into doing the 2D rendering with opengl. The lazyfoo.net opengl tutorials are excellent help, but limited to just explaining the graphics, obviously. Either way, I'm interested in both regular SDL and opengl 2D rendering techniques and how other components of the game would fit together.

0

Share this post


Link to post
Share on other sites

This may help you:  http://en.wikipedia.org/wiki/SOLID_(object-oriented_design)

 

What you are asking for is overly general; So I'm giving you a very general answer and that is that in most code bases its good to keep in mind that as long as classes have one responsibility, they are closed for modification but open for extension by design, and you follow all the OOP rules, you should be good.  If you need to learn these rules first, then I suggest you invest in a book called "Clean Code".  Most of the code samples are in java but the things it teaches will make you a better programmer in any language for any project, even if you disagree with some of the things the author :(Commonly simply known as "uncle bob") says.

1

Share this post


Link to post
Share on other sites

I'm looking over the links now. Thank you.

 

L. Spiro, that's a great article. The Game/Engine structure is the next one I'll look at.

0

Share this post


Link to post
Share on other sites

There is one high level design pattern I really can recommend, and that is the Model-View-Controller. A short summary:

  • The Model can be seen as the physical model. It will manage objects in the game, and how they interact with each other, and attributes.
  • The View knows about the presentation to the player. This is where the OpenGL goes. The View understand the model, and knows how to present the various states.
  • The Controller takes care of all input (mouse, keyboard, timers, ...), and tells the Model and View to act accordingly.

There are more advanced version of the MVC pattern, but this is a good start. For every class and file you have, make sure you clearly document to what part it belongs.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0