To confirm: is this the script that was previously at http://almighty-saplings-ash.googlecode.com?
Thanks very much for adopting it, Bale!
Same script. New home. Two updates for compatibility with changes to KoL and KoLmafia.
Delete the old and install the new. In that order.
Yep, thanks. Just wanted to verify that I was replacing the correct existing script. Thanks again!
I'm running into a bug when attempting to banish hot in the Estate.
- Right-click on the Estate box in the Totals section at the top of the parsed log.
- Select Banish element > Hot.
- Mafia pops up a warning that "Cold has not been banished yet, banishing Hot now will make this impossible, do you wish to continue?" (Which I don't think is true.)
- Mafia prints this in the gCLI:
Code: Dreadsylvanian Woods Encounter: The Tallest Tree in the Forest  Dreadsylvanian Woods Encounter: The Tallest Tree in the Forest Encounter: The Tallest Tree in the Forest Encounter: The Tallest Tree in the Forest Offset 2 out of bounds (clan_raidlogs.ash, line 2349)
- I'm left at The Tallest Tree in the Forest NC.
Looks like there may be a mistaken route from the Estate menu option to the Forest that's confusing things.
Thanks again for adopting this, Bale!
I don't think that is what happened.
If I understand, you started an adventure in the Dreadsylvanian Woods. Then instead of exiting that adventure cleanly you entered the raidlog (Perhaps you clicked the back arrow on your browser) and selected the Estate box. Unfortunatley you were still in the non-combat adventure for the Tallest Tree so the program aborted. And thank goodness it did abort rather than choosing a choice option.
While you could have gotten a better error message, it would have been a lot of work for every adventure to recognize that you were never in it to begin with and report accordingly.
Just for the record, there is no such thing as a route from the estate menu option to the forest.
Thanks so much for taking over maintenance, Bale. I love this script.
Just as an FYI, whatever bit of the script removes banished elements from the element list at the top of each zone seems to have broken at some unknown point in the past. Monster shift still works as expected, but the "Elements:" list never changes. Not really a big deal, but thought I'd report it.
Most of this script is a mystery to me so if someone can identify and fix that problem I would be grateful.
0. Don't be in a choice adventure.
I just replicated this by opening a brand-new Dreadsylvania instance, doing absolutely nothing in that instance, loading the raid log, and then following the steps I listed before. Attached is a debug log, which hopefully will help, or will at least demonstrate that I wasn't stuck in a choice before using the raid log manager. (I visited main.php to make sure I wasn't.)
Again, the warning that "Cold has not been banished yet, banishing Hot now will make this impossible, do you wish to continue?" is incorrect, I think. I'm not sure whether the two issues are related in some way.