A fast, easy to use, free, and community supported 2D game engine
I'm extending Sprite to make my Character object. I'm wondering if I should assign each character state to the object as an AtlasSprite property (like character.standing, character.jumping, character.casting, etc) or is it more efficient to switch out the frame of one AtlasSprite?
They are all using the same texture memory so I didn't think it would matter much, but I wanted someone else's opinion that knows more than me.
Am I going about this the wrong way?
What do you mean they're all using the same texture memory ? You have one png file containing all your "character states" graphics ? If so, I don't see how you can use Sprites. If not, then it's not really the same texture memory.
I'm not sure I really understand what you're doing. Anyway, if you're going to draw multiple characters on screen on the same Layer, then you should use AtlasSprites because they're drawn in a much more efficient way than Sprites. If you're going to add subsprites to your character object (like a life bar or a label with his/her name), keep in mind AtlasSprites can't have children and therefore Sprites may be easier to manipulate.
Also, are you gonna use Animations ?
Sorry I was not more clear.
Basically I am creating a new character object to wrap up all my character animations, states (atlas sprite frames), effects,etc. I am using sprite as my parent (extending sprite I guess I should say) because it will alow me to add children. I then add an atlassprite as a Property to the object and make it a child to the sprite which houses all my character states ( from a png as you said).
I do plan on using animations later, but have not made any as of yet and would welcome youR reccomendations on how to organize them in my object. Also, a character can currently be one of 3 classes. All of the classes will have the same types of animations and things, but just use a different sprite atlas image.
Hope this clears it up a little and I thank you very much for taking the time to help!
Ok, I see... If I were you, I wouldn't subclass Sprite to make your character object because you obviously don't need the texture drawing feature. I'd rather subclass the generic CocosNode : @interface Chara : CocosNode.
Then, I'd have an AtlasSpriteManager as a property and child of this node. The ASM would be responsible to draw the character via one or more AtlasSprites. Your Chara class could have all the int, BOOL, float (etc) variables that you like. You could have a particle system for the effects and a couple of Animations (or an array of animations). It really depends on your game but that should be a good start.
Try to think ahead how you will achieve saving and loading your game. It can be much easier to save your data if they're separated from the drawing code. Read my other post here to help you make up your mind.
You must log in to post.
