Jonathan Snyder

if anything this adds extra steps. If you look here: https://github.com/HaxeFlixel/flixel-addons/blob/dev/flixel/addons/nape/FlxNapeSprite.hx#L289 FlxNapeSprite removes the body from space if it is part of space to begin with.

Good question. I would prefer that. Shall I implement it?

@JoeCreates yes you are correct. it looks like it adds or removes it from the space depending on if physicsEnabled is true, which makes sense

Well it does (for the new body) depending on if physicsEnabled is set to true. however if the old body is already set, and a part of space, then we...

I do think that this class should be looked at again. I don't like the fact that setPosition focuses on the top-left and the body is center anchored. It seems...

@JoeCreates I meant the reference is lost from the FlxNapeSprite. wether we remove it from space or not, it will still be floating around not being used (unless there is...

I don't see a reason for FlxNapeSprite to have more than one body accountable. I would probably want it destroyed since it's really only used by the helper functions for...