cocos2d for iPhone

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

1. 

   macgeo
   Member

   Quick question: What's best way to "reset" a player (as in, after death) if he's a node that contains other items? Currently I do this...

   Inside mainscene.h:
   

   {
   //create a member variable for the player. He is a subclass of CCNode.
   Player *m_player;
   }

   Inside mainscene.m:
   

   //initialize player and add to scene
   m_player = [Player node];
   [self addChild:m_player];

   Within the method to kill the player:
   

   //likely doing this wrong...
   [self removeChild:m_player];

   Then I bring him back in the same way I created the first version of him, [Player node] and addChild. Something about this isn't right because I believe the new player is inheriting some of the old one's values. Is this a pointer issue, or something else I'm screwing up?

   Considering making my player a singleton, which may help, but would rather be "tidy" and just have the single gamestate singleton. Lemme know what you think.

   Posted 1 year ago #
2. 

   Dragyn
   Member

   [self removeChild:] only removed the sprite from the layer - it doesn't destroy it. So when you're re-initializing the player when you bring him back, you're probably just linking to the same Player object again.

   If this is the way you want to handle your player, i'd recommend creating a method "resetPlayer" or something like that, and it would be called before you call addChild:. In this method, you would reset all values pertaining to the Player to their baseline values.

   To keep it "tidy", you should build the methods for resetting the player inside the Player class. This will keep the OO structure more intact than using a Singleton.

   (Although, for a single-player-only scenario, the Player object itself could be instantiated inside the gamestate singleton you already have. This would allow persistence of Player data outside of your current Layer/Scene. This will work fine as long as you will only have ONE "Player" object in the whole game.)

   Posted 1 year ago #
3. 

   macgeo
   Member

   Thought that might be the case. Actually turns out that I had some other things gone wrong around it- starting and stopping game loop poorly, and within the Player class I never set an initial value for "BOOL playerdead = NO." Anyhow, I got it to work.

   Until I start optimizing the code in a few weeks and need to rewrite it all :)

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.