You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All tiles are considered "reachable" by the Dijkstra Map.
This results in orphan areas not being culled, and the possibility that completing a map might be impossible due to the exit stairs spawning in an orphan area.
Tested and verified with the "Run this chapter's example with web assembly, in your browser" link in section 4.5 of the tutorial
The text was updated successfully, but these errors were encountered:
I was able to "fix" the behavior by adding a call to self.map.populate_blocked(); before the culling step. This marks the wall tiles as blocked. The DijkstraMap is working as expected but since the blocked vector from Map was not updated the get_available_exits function which is used by the DijkstraMap was returning walls as available tiles
All tiles are considered "reachable" by the Dijkstra Map.
This results in orphan areas not being culled, and the possibility that completing a map might be impossible due to the exit stairs spawning in an orphan area.
Tested and verified with the "Run this chapter's example with web assembly, in your browser" link in section 4.5 of the tutorial
The text was updated successfully, but these errors were encountered: