UpdateManager refactoring

[llafuente]

Some problems raise again from the order of things are executed.

First: Rename IUpdateEntity -> PlatformerEntity

Now we have two events: PlatformerUpdate & LatePlatformerUpdate
Moving Character in PlatformerUpdate is not always viable, ex: while pushing boxes, because Character is always using the last-frame contact (not a real problem) but when you chain MovingPlaforms movement there is...

Study an solve the case for 4-5 boxes.

Some magic must be done to handle those cases...
Alternative: is that MovingPlatform do not use Translate directly, something like Move, to notify passengers and they can react to that fact.
Alternative: Character broadcast a message to child that it has been moved. children react then...

The problem will be greater when pulling, so review after that...

[Thundros]

PLEASE fix this!!!!!!!!!!!!!!!!!

[Thundros]

@llafuente : hello?......

[llafuente]

hi @Thundros, this library is obsolete I don't have time to fix it myself.

Long time ago I move most of the library to: ECM2 and it's my recomendation.
This library handle all the physics by itself, while good on paper (old-school) it's bad for these kind of simulations or continuos collisions.