Closed Malibu-Stacey closed 3 years ago
I imagine the list is going to be very large... I have no actual opposition to it if someone else wants to write this though
I can work on this one. I see it as a 2 step process:
Questions
Here's a list of banishable monsters that we probably don't want to banish, grouped by relevant council quests:
❓: I don't know if these are actually affected by banishers
(This list is neither verified nor exhaustive; feel free to correct me)
Many of these monsters are not as important in Softcore since their drops can be pulled. An ideal implementation (not necessarily the prototype) could have an in_hardcore()
check for them. I don't play softcore, though, so I don't know if autoscend actually pulls them.
Thanks for the detailed list! Sorry for delayed response - real life has been busy and probs will continue to be. Agree with your approach of including helpful monsters and not just mandatory. Do you think the following are important enough to add to the list?
Agreed some are less important in softcore. For now I'm going to keep it simple and not consider SC vs HC. Potentially could save a pull if a drop happens to happen.
I plan to include the question mark monsters in the check. No real harm besides a few extra CPU cycles.
@pastelmind mentioned in Discord that he'd forgotten he ice-housed the Pygmy Bowler before ascending and hadn't melted it which then caused autoscend to spend over 50 adventures in the Hidden Bowling Alley trying to complete the quest. We could add a simple check for a bunch of monsters we know are ascension relevant when in a run that the Ice House is allowed and abort if we find one so the user can go free the monster to continue (or play manually if they really want to keep that monster banished for some reason).