Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.5 (ch. 27) Cellular Automata Orphans Are Not Culled #187

Open
KyleHagad opened this issue Mar 21, 2022 · 1 comment
Open

4.5 (ch. 27) Cellular Automata Orphans Are Not Culled #187

KyleHagad opened this issue Mar 21, 2022 · 1 comment

Comments

@KyleHagad
Copy link

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

@mFragaBA
Copy link

mFragaBA commented Jan 1, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants