Skip to content
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

Open
NoOneNeedsThat opened this issue Dec 4, 2024 · 4 comments
Open

BladeBurner - estimated succes chance doesnt rise #1826

NoOneNeedsThat opened this issue Dec 4, 2024 · 4 comments

Comments

@NoOneNeedsThat
Copy link

be in BN 10.2
have all Blackops in BladeBurner finished
(BladeBurner Rank 11.5mill)
grafik

have all augments installed (conventional or grafting)
have attributes in high values
grafik

have no sleeves doing BladeBurner tasks

doing field analyses dont give clear estimated success chances, even after running several 100 times
grafik

even lowering level doesnt give a clear est. success chance
grafik

maybe an issue because of bad attribute ratio????? (eg. str vs cha ???)

@NoOneNeedsThat
Copy link
Author

i think i found out what the problem is:
grafik

is that intended????

@catloversg
Copy link
Contributor

Check my comment at #1575 (comment).

In the next version, we don't have this problem.

@NoOneNeedsThat
Copy link
Author

NoOneNeedsThat commented Dec 5, 2024

thx for clarification.
in fact, the comments in #1575 only apply partially to my situation, as i did tracking and other contracts regularily.

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]
i was pretty sure to get a proper estimate this way

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)
is the current BladeBurner city relevant for the tracking contracts or will the tracking contract improve the est pop in all cities?

as a fun fact, #1575 seem to have the issues in the same bitnode as me (BN10.2)

@catloversg
Copy link
Contributor

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.

is the current BladeBurner city relevant for the tracking contracts or will the tracking contract improve the est pop in all cities?

Current city.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants