Navigation / navmesh issues

Hi @luboslenco,

As I understand haxerecast binds to recastnavigation/recast.js, but only a few features are used currently.

Would be nice to be able to have the following also:
- NavAgents to be able to avoid each other based on setting on/off (crowds in recastnavigation?)
- Be able to add static and dynamic/moving collision boxes to a collision layer which is avoided by the NavAgents (temp obstacles in recastnavigation? perhaps temp obstacles are only static?)

With these two features navigation would become very usable.

Kind Regards,
Martin

Start by tracing haxerecast's current bindings to recastnavigation/recast.js and identify how navigation agents are represented. Compare the requested agent avoidance and static or dynamic obstacle behavior with the corresponding crowd and temporary-obstacle APIs. Done would require defined behavior and tests for both features, but the issue does not name specific files or tests.

Written by the indexing model from the issue text.