Mazette

Popped in expecting JS code procedurally generating and solving the mazes on the fly, but it looks like the page just pulls animated GIFs of pre-generated maze solutions?

There are only two GIFs in the `/mazes/L40` directory, so now I'm lost as to how the query parameters in the `img src` determine which maze solution is used.

If you enjoyed that, you'll probably also enjoy the "Maze Generation" section of Mike Bostock's Visualizing Algorithms talk: https://bost.ocks.org/mike/algorithms/#maze-generation

It actually passes the exit because it's not making the "turn" to it. So it tries a bunch of other paths first before the time comes to try the turn towards the exit.

I'm not sure how kosher this is as it's my own project, but this reminds me of a project I did for college back then:

https://arianv.com/post/cs-180-pathfinding/

It's a python/jupyter project though that's just rendered into html. It's over-engineered and over-explained :D

I just saw the line ignoring the exit and continue to search for it, that was... Unexpected!

Is it just me or are there only two different mazes?