D8H

The case is too specific to be integrated in the top-down behavior as it would be almost impossible to control. It can be done using variables for acceleration and force...

I agree that having a different behavior at 99% and 100% of the max speed is an issue, but using only one of the 2 formulas make things weirder. We...

If someone is facing this issue, a workaround is to close the project and open its json file with a text editor to copy paste the values. This is a...

What could be an issue when implementing this change request is that Tween is an extension and parameter types are defined in Core where tween concepts shouldn't be known.

This seems very promising. I had a lot of issues with PIXI imports when trying to add types definition for Pixi extensions (pixi-tilemap) and this will probably avoid some not...

> Should we rather work on the core to expose variables to the events based extensions? This would make this trivial to implement as an extension outside of the main...

> I think that's in this case a UX improvement to be done for the editor rather than something that the extension should support itself :) Do you mean the...

I added an action to disable the NavMesh updates. For instance, it allows to drag an obstacle while paths are computed without rebuilding/invalidating the meshes continuously. 

With the automatic invalidation of the NavMesh, this can happen: * events change the obstacle locations * events ask a path * pre-events, the obstacle manager watch the obstacles and...

I opened 4 change requests. For clarity, should I remove from the code the TODO linked to these requests? Do you think one of these requests should be included in...