-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autoscend aborting out on Normal Palindome because it's out of pulls for Wet Stew #1487
Comments
I rambled a bunch already about this in the autoscend channel, but I tried to mess around with things like, under
But unfortunately, I haven't been able to figure out how to placate the script to not error out because it's stuck at pref |
...as an aside, I noticed while looking at this that some of the other tasks have a little less "elegant" of (mostly debug comment) handling than Filthworms for when they're unable to be completed and are thus bypassed, primarily due to lacking pulls to tackle them with. Notably:
Mostly just noting this here for documentation's sake since they're not breaking anything; I'll gladly try my hand at fixing some of these myself when I have some more time next week to try to address the specific conditions leading to them being skipped, rather than filing a separate issue for them (...and when I maybe have a better idea on how to solve them). |
Context
Expected/Desired Behavior
If unable to complete a portion of a quest, and with other doable quests remaining, Autoscend should move on to the next quest.
Current Behavior
When autoscend gets to task 50 (L11_palindome) and is in normal/softcore and lacks available pulls for Wet Stew, rather than bypassing task 50 and moving on to other ones like it does with other tasks (i.e. bypassing filthworms when you are afflicted with ELY), it aborts out with a generic error:
Failure Logs
vuvuzela_virtuoso_20240824.txt
The text was updated successfully, but these errors were encountered: