Joe Williamson

I have responded to it and you just keep ignoring me. It makes no difference. In my actual game _I'm not even using flixel's nape stuff_. It doesn't matter where...

Here is a diagram to illustrate clearly. There are TWO `step()`s after which the ball is on the ground. There are THREE `step()`s after which ONGOING is called.  Flixel...

Why do we have a setBody rather than just having a body property with a setter?

@thegoodideaco That doesnt remove the old body. It determines whether the current body is in the space or not. Note that it gets called after setting the body in setBody....

Im not sure if it should automatically remove the body from space or not...

@thegoodideaco The point in the original post is that the original body isn't lost, because the space still has a reference to it, hence the possibility of a memory leak....

Seeing as FlxCamera has improved a lot with zooming, it seems to me that FlxZoomCamera might not be worth keeping at all. Does it do anything more than a lerp...

@MSGhero Sure, although breaking changes have to happen some time. :) I prefer tweens to the lerping anyway due to the extra control and have personally never had any use...

Did your optimisations make it in? Looks like you are still iterating on maps in places. I would typically create a separate array of iteration (potentially making a new class...

Oh... you removed the map? To be clear I didn't mean to suggest to replace maps with arrays, but rather to use both. Use array (or perhaps list) for iteration...