cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   xStoryTeller
   Member

   First of all, thanks for taking some interest in this topic ! I just have a few questions. First let me set the mood for this project, its a school project where we have to make a game. We started this project last year, and started freshly with C-Objective and the code got quite messy so we are going to do a full re-write of the code and could use some help on doing it in the best way. Its a platformer / puzzle game, where you have to draw lines and he walks on lines previously created.

   1. Last time, for collision, we used a lot of CGpoints and CGrects. We were thinking of using Box2 or Chipmunk. Which one would fit us best ? The main problem was that we had to make a lot of rectangles / points and we could only work with squares for the collision.

   2. Our line drawing worked like this : Start touch make a new array, move event add the current point to this array, stop touch close the array and put this into another array, which our draw function would cycle trough. ( Array with points -> Array for a line -> Array which holds all lines ). Is this the best way? It seems a bit inefficient, just wondering what kind of other idea's you guys might have.

   3. We would like to have some kind of level loader so that if we add a level, the gravity system, basic collisions, player functions... stuff like that would be included and we would just need to place some lines / objects and it would work, well that is the idea anyway, we have some ideas for this but what is the best / easy way for this ?

   Anyway, thank you for any advice you could give n.n

   Posted 2 years ago #
2. 

   Mitch Lindgren
   Member

   2. You could consider using a queue or several queues instead of arrays; this would likely be more efficient for your purposes.

   3. I don't believe he's released it yet, but riq was working on something like this: http://blog.sapusmedia.com/

   Posted 2 years ago #
3. 

   xStoryTeller
   Member

   Hey lindgrenM,

   Thanks for the post, but I dont think you got what I ment with question 3, I guess it wasnt that clear. I ment how to do this code wise, so that we dont have to have the gravity code in every file for a level, but just in one. Would it be best to just put this kind of code in a file and include that in all the other levels ?

   Kind regards,

   xStoryTeller

   Posted 2 years ago #
4. 

   chrisco
   Member

   As a really simplified OOP example, you could have one class called Game that holds the basic logic (such as gravity, etc - realistically, this would be broken into many classes). Your Game object would hold a LevelLoader object that it would initialize at the start of the game.

   The LevelLoader object would hold all of the logic needed to read your level files, and would provide methods that the Game object can call to get the information it needs about each level. For example, it might have a -collisionMap method that returns the currently loaded levels collision details. There's no need for LevelLoader to know anything about how this information is used by the Game object - it just needs to provide it.

   Hope that makes a little sense :)

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.