Better Pathing

Hello, loves! If we draw suite paths in the right order, it should give us the layout we want with no extra work. If this works, it’s a lovely idea. Herein we eschew pompous prolixity. The new PassageCollection object, which I am inclined to rename to Passages, is now in place. It ensures that once a passage between two rooms has been formed, that passage is preserved even if we’re nominally computing new passages. We did that because when stepping the build for the developer, we want to see the passages as we go, and the passage-computing code would make new decisions about where things should go. Arguably, we coulda shoulda changed the passage-making in some fundamental way so as to specify somehow just exactly what it should do. That seemed daunting, and once we created the Passages object (see what a nice name that is, gonna change it right now … done) as I was saying, once we created the Passages object, it was very simple to have it keep track of which room pairs already have…