• 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
Gravious

OOP with vectors

6 posts in this topic

First post, I'm making my first game, building a framework and making some progress.

 

I've created a class for my entities, and i've created a std::vector of pointers to the instances so that i can loop through them to trigger a member fuction to update their logic

 

entities[i].updateLogic();

 

what i want to do though, is inside that updateLogic() member function, i want to cycle through every other member of the entity vector, but the problem i have, is i can't define the entity vector inside the entity class definition?

 

help!

 

(Thanks)

0

Share this post


Link to post
Share on other sites

Pass the vector by reference to the method, but it is VERY likely that there is some flaw in your design if every instance need to go check every other instance.

 

EDIT: Started writing the answer before nbodynews, didn't see he had replied.

Edited by KnolanCross
0

Share this post


Link to post
Share on other sites
As others have pointed out, you don't want every object to know about every other object.

Consider passing reference to only the objects that need them when you create you game world. For example, if you have a switch that controls a door, then give the switch a reference that it can use to control the door.

If you need the objects for collision detection then create what I like to call a collision space. A collision space contains a collection of collision objects. Each collision object has a position and a shape. If you want to know what objects you are touching you simply ask the collision space to return a list of contacts of objects touching your object, or if you have many objects moving all the time you can have the collision space find any overlaps then alert each individual object of the overlaps that are occurring. The key here is the logic for collision detection is in its own independent module. Then you game logic doesn't have to worry about colliding anything, it just gets a list what objects it touches determines what to do based on that. That has worked well for me in the past.
0

Share this post


Link to post
Share on other sites

Thanks for the input.  

 

The base entity class is further inherited to become the various objects my world interacts with, and i have various bools set to say wether an object is interactive, or active at all, i had thought that it would be ok to make a for() loop and cycle through the entities and only apply the logic based on the individual objects relevance to the currently running instance of the class, but i'm guessing what you're suggesting is i have some kind of external class that governs logic and sweeps through my vector and applies logic externally, instead of the entities being in control of their own logic?

 

I am new at game internal design, this is a design i thought would be ok, but i'm not married to it :)

0

Share this post


Link to post
Share on other sites

... i had thought that it would be ok to make a for() loop and cycle through the entities and only apply the logic based on the individual objects relevance to the currently running instance of the class, but i'm guessing what you're suggesting is i have some kind of external class that governs logic and sweeps through my vector and applies logic externally, instead of the entities being in control of their own logic?

It really depends on your definition of "own logic".

 

A simple example is collision. Some beginners will handle collision by getting each object to iterate through the object list, testing for collision. This heavily couples the object's logic to the list of other objects in the game. For example, you may end up littering your code with tests for objects that are "inactive" or otherwise uninteresting. If you add a new object type - for example a "trigger" object which can be used to activate a cut scene when a character enters a certain area, now you might have several loops you need to inspect to ensure that, for example, you Ogre doesn't choose the trigger as its next meal.

 

Advanced games will totally separate collision from the entities involved, usually via a physics library. An entity can own certain physics bodies, and the appropriate callback mechanism can be used to tie game logic to physics events such as collision. A middle ground for a small project is to have the calling code iterate through the list and notify the objects when a collision occurs.

 

It also depends on the scope of your game. A pong game doesn't warrant this complexity. 

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