Bug - Won't Fix Black Cat batting used items away not detected

Ah... if the official goal is to not make it easier, I suppose I can accept that and not work on simplifying things. Speaking as someone who screwed up a BC HC ascension by one fight, by finishing up the NS in the relay browser instead of through the client, personally I think it's painful enough already, but then again, I'm not one of the guiding two. :D
 
Also: can the BC and OAF actually bat away/sell quest items (which is after all what the bounty items are)?
 
Surely aborting on encountering adding machines isn't really making life easier. Maybe that could still be introduced.
 
I can verify that the BC bats away bounty items... In the rare case the bounty is actually happening at the Giant's Castle and I notice, in each bounty I've had to kill an extra Raver or two because of failed bounty drops.

And as the aborting on encounter patch hasn't been approved by anyone yet in the past month, I'm guessing it's unlikely to happen... Suppose I'll stop work on this overall then. After all, I should hopefully be done with this and never experience it again after another month... or so... *mutters*
 
Okay, what's likely to be the final version (and the one I'll use) of the Black Cat Combat patch is included here. I'll leave the old version, because someone may prefer that, where it always aborts combat if it thinks you might want it and you have BC or OAF combat on HC or RAM without TCW equipped.

Anyways, what this version does is that if you have a problemFamiliar (new private boolean function that checks if you have a Black Cat or OAF without Tiny Costume Wardrobe) equipped, and you come against the hulking construct, abort automation.
If you come to a rampaging adding machine, auto-attack it to death, unless you've set your choiceadventure to show in browser, in which case it'll abort. This means that you can still farm out the scrolls automatically, and then abort automation whenever you actually want to by changing the choice.
Another change is that if an expected bounty item doesn't drop, but you have a problemFamiliar, don't stop automation... life sucks, and it's your fault for bounty hunting with a lousy familiar, but that's just the way it goes.

Anyways, I don't think this really qualifies as making the BC ascension easier... in fact, it means that KoLmafia won't try to make the scrolls itself, even if you set it as a condition... but it does mean that people won't end up thinking KoLmafia will put the scrolls together for them, and end up 300 turns down with no scrolls left wondering what happened. :)
 

Attachments

That actually does seem a nice compromise. It doesn't recognize batting of items, it just aborts on the main source of potential problem rather than assume mafia will work. It seems like a good idea.
 
Back
Top