-
Notifications
You must be signed in to change notification settings - Fork 167
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
Bulk buy / mitigate early game lag #183
Comments
you can let frozen cookie buy 10 or 100 buildings each time, when you click the corresponding button above the buildings list |
Your suggestion does seem to help. lots of 10: in 1min, I get to 1.5 quadrillion cps But as my testing shows, that my (poor guesstimates) is improving cp/s, really need something that reduces the time it takes to make a purchase, because waiting 200ms to make a purchase is worse than just buying anything sufficiently efficient. My assessment is: assisted lots of 100: basically an abuse of race condition, e.g: you buy the 1-4 prisms before it issues the purchase of 100 temples, highly temperamental to input timing. Unless I'm misinterpreting how the code works (I should probably go dig and experiment) I Hope to achieve both the most efficient build order (or at least a very good approximation), and keep the automation (I don't need to switch between buy lots, and don't need to assist it) This could be done by: baking the first ~1000 purchases. (though I don't like this solution). |
I've noticed that the algorithm determining the next purchase takes far too long for the time frame in which you earn cookies, and while the autobuy is still trying to figure out what the most efficient next purchase is, in the tens-of-cookies range, I'm earned 100k worth of cookies.
Maybe have the game just outright buy all efficient purchases it can afford after the calculation. (I assume it's currently only buying one at a time?)
The text was updated successfully, but these errors were encountered: