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
When I originally developed this library I was able to prove (mathematically) that there was no difference between a maze with thick or thing walls when it came to generating or solving them.
So I came up with the space-saving, dense array notion of making sure all rooms and hallways were on odd cells, and all walls were on even-numbered rows/columns in the array.
This was a fine idea, and I still like it. But if a user wants to hand-draw their own maze (which they should be able to do), they need to know about this quirk.
This needs to be better documented for the users.
Thanks to @kburavskij for bringing this to my attention.
The text was updated successfully, but these errors were encountered:
When I originally developed this library I was able to prove (mathematically) that there was no difference between a maze with thick or thing walls when it came to generating or solving them.
So I came up with the space-saving, dense array notion of making sure all rooms and hallways were on odd cells, and all walls were on even-numbered rows/columns in the array.
This was a fine idea, and I still like it. But if a user wants to hand-draw their own maze (which they should be able to do), they need to know about this quirk.
This needs to be better documented for the users.
Thanks to @kburavskij for bringing this to my attention.
The text was updated successfully, but these errors were encountered: