Rework on the FlxNestedSprite

[Cheemsandfriends]

While I was using FlxNestedSprite for a project, I noticed that it was very... uncomfortable
for example, you would need to use a relative variable, which you would use in case you added a child, making it very difficult to do stuff like sprite.setPosition() or even sprite.x! but instead sprite.relativeX. same goes with acceleration, scale, etc.

This should fix the inconvenience.

[Geokureli]

I'm also very confused on how the updateMotion() call was removed and seemingly not put anywhere else.

still confused about this

[Cheemsandfriends]

Can you type out examples of how things were done in the old code vs the new way?

Basically, when using FlxNestedSprite, if you added to a parent, the x value would be overriden by the parent position. same goes for alpha, angle, velocity, etc, etc...

With this, what it does is basically if the instance's a child, it would be concating the parent's "relativeMatrix" which would concat the grandparent's matrix and so forth until the beginning of its family tree lmao.

so in the old code, you would need to set relativeX to set the child's position, in the new one, you can do it directly with x. same goes for angle, every type of velocity and so on.

same goes with the color transform, so you can tint the sprite via color, put it inside a parent, and then it would be the tint + the parent's tint with relativeColorTransform.

[itulau]

I've tested your changes and my sprite just went flying off the screen: