I survived PBB!  I can probably jot down some thoughts about that but it's late and so I will instead report on my accomplishment for today -- I had the day to rest and recuperate and just chill at home after being out camping and everything and I ended up spending most of my time on...ALTTPR research.  It took a lot of work and I'm not 100% sure my code and all is bug-free (hopefully good enough...) but I believe I now know how to route through Skull Woods in pretty much all situations, woohoo!

Skull Woods is a really weird dungeon to route because it's split into different sections.  The key logic is not as complicated as PoD but there's an extra complication in that you can get softlocked if you drop into the "dropdown" hole and don't find a requisite small key to escape.  You can mitigate or even prevent that risk by doing the other checks in the front + middle of Skull Woods, but of course all of the different routes will have different timings and average timings, so it's really hard to know what is actually best in any given situation.

Some things from the analysis were intuitively true -- if you're planning to walk out of Skull Woods, you want to do the front last.  But other questions weren't as obvious to answer, for example if you're planning on doing a S+Q out of Skull Woods and clearing the entire thing, is it still better to do it back to front since the boss at the end is required?  Or should you try to potentially minimize backtracking by doing it front to back -- but risking a required backtrack for the big chest if there's an item there (happens 12.5% of the time).  Front to back actually ends up being better here, though of course skipping the front entirely is also a viable option since SW is in general just not a very efficient dungeon in terms of raw number of items.

Unlike the PoD analysis I did a while back, the conclusions from this one substantially change how I route SW in some cases (though not all), which is great!  It's going to be tricky to remember exactly how to route it since there are so many different options and cases, but hopefully I can get a handle around it intuitively and then start leveraging those routes in my runs...