-
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
Boo Clues should use ProvideResistance functions #1103
Comments
ProvideResistance first needs an option to simulate the familiar instead of changing to it, the maximizer can only calculate familiar weight for resistance with the current familiar so simulating it comes with cost of -1 or 2 max resistance accuracy otherwise familiar will get changed and changed back every turn for most of the run |
Good point. I'm ok with extra familiar changes to get a more accurate result. Open to alternate viewpoints. Classic performance vs accuracy trade off. |
don't think you would like it, when I tried autoscend ran turns twice as slow (before http2). If accuracy is important ProvideResistance could manually add familiar weight at 1/20? or equivalent value of resistances and maximize several times with min and max arguments for the next familiar weight values that increase resistances |
Boo clues prep should use ProvideResistance both to speculate if we will survive and then to do the actual buffing. Currently this is all done within the level 9 quest ash file and is difficult to maintain. Better to have all that in a single function, which happily already exists - ProvideResitance
The text was updated successfully, but these errors were encountered: