Is there a reason why the default PathWorld returned by Game::World.path() is const?

We can create our own worlds using Game::World.New() and then set our own areas, but then we can't update the PathWorld in it to use the custom areas.

I would like to be able to call Game::World.path().set(...) to set the path mesh for an area.

Any world on this one Esenthel? Possible, not possible?

no, Game::World manager should handle the pathworld from Game::World only.
If you want custom PathWorld, you need to use custom PathWorld variable.

Even in the case where using Game::WORLD_MANUAL and fully building and controling your own world? In that case we should be able to control the world's default PathWorld as well, no? You would just need to remove the const from it right? Seems silly that we have a perfectly good empty PathWorld in Game::World that we can't use, which would be saved and loaded for us automatically.

yes, in case of custom worlds pathworld should be customizable

temporarily you can use this function to remove const modifier on object:
T1(TYPE) inline TYPE& ConstCast(C TYPE &x) {return (TYPE&)x;}

Thanks. I'll try out your code.

Isn't it just a matter of removing the C from the World.path() method, or is there other internal stuff you need to look at?