-
Notifications
You must be signed in to change notification settings - Fork 276
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
BladeBurner - estimated succes chance doesnt rise #1826
Comments
Check my comment at #1575 (comment). In the next version, we don't have this problem. |
thx for clarification. i told my script to check for success chance before starting any action (as i dont like failures). i also told my script to do a field analysis like every 5th action (which should keep the pop estimates accurate) or if getActionEstimatedSuccessChance[0] of an action is smaller than getActionEstimatedSuccessChance[1] so, in conclusion to your comments, i either have to switch to a city with est pop or force a tracking on a scheduled basis? (for the mechanics working properly) as a fun fact, #1575 seem to have the issues in the same bitnode as me (BN10.2) |
Both pop and est. pop are usually not 0 (except special cases). Running Tracking is only a workaround when est. pop drops to 0. This situation is rare. If it happens, it's very likely that pop is also 0 or very low. It's best to move to another city.
Current city. |
be in BN 10.2
have all Blackops in BladeBurner finished
(BladeBurner Rank 11.5mill)
have all augments installed (conventional or grafting)
have attributes in high values
have no sleeves doing BladeBurner tasks
doing field analyses dont give clear estimated success chances, even after running several 100 times
even lowering level doesnt give a clear est. success chance
maybe an issue because of bad attribute ratio????? (eg. str vs cha ???)
The text was updated successfully, but these errors were encountered: