I recently tried switching from oxidized_navigation to vleue_navigator. However, I noticed that the navmesh doesn't update, and #54 didn't fix the issue. So, I switched back to oxidized_navigation in this commit.

@mockersf asked me on Discord if he could try running the project before the commit. Since I’ve fixed quite a few bugs since then, I decided to create a separate branch with this commit reverted and rebased onto the latest master: #330. Hopefully, this will help determine whether it's a bug or an API misuse on my part.

Below are the steps to reproduce. It requires a bit of setup when you try it for the first time :)

1. cargo run if you running it for the first time. Next time run cargo run -- play --world-name "New world" family "New family" instead and jump directly to step 16. You may also want to run with RUST_LOG=project_harmonia_base=debug to tracing.
2. Click on "Play":
   
3. First we need to create a world. Just click on "Create":
   
4. Confirm creation, just leave the default name:
   
5. Now we need to create a city first. Not very intuitive, but select cities tab first:
   
6. Press "Create":
   
7. Confirm creation, just leave the default name:
   
8. Now switch back to the families tab:
   
9. Click on "Create new":
   
10. It's a stub for character creation screen 😅 Just click on "Confirm":
    
11. Confirm the family name:
    
12. Now click on "Place & save":
    
13. Press Esc and click on "Save". It's very important, if you exit the game the world won't be saved!
    
14. (Optional) You probably want to see navigation paths and navmesh. Let's enable them. Press Esc and click on "Settings":
    
15. (Optional) Navigate to developer tab:
    
16. (Optinal) Tick the needed checkboxes and press "Ok":
    
17. Now in order to place walls you need to enter build mode:
    
18. Select walls:
    
19. Click anywhere to start placing a wall:
    
20. Click anywhere again to confirm placing. You can already see that the navmesh is not updated. Let's try to move a character, back to the family mode:
    
21. Click somewhere behind the wall and select "Walk here".
    
22. You can see how the character goes through the wall:
    

Since I have networking and serialization, I use the blueprint pattern, which is basically "required components at home". For walls you can see that an empty collider is inserted here. And collision is updated here on the wall change.
Let me know any questions :)

After writing this I started to doubt that it's the best way to debug the issue 😆 Maybe it's simpler to just create a simple example with a changing mesh.