-
Notifications
You must be signed in to change notification settings - Fork 56
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
Avaible keys optimization #5
Comments
Key proliferation shouldn't be much of a problem anymore since you can't On Thu, Jan 16, 2014 at 3:01 AM, glupilogin [email protected]:
|
Thanks for the reply. |
I see that if you routinely collect keys from other players, lopsided harvests are likely. |
Correct. |
This seems like a difficult problem in general. If you have almost enough keys for maxfield, you pick a maxfield plan that only loses a few fields because of the missing links. If you only have a few keys, you could do a brute force search. I haven't been able to think of a good method for the in-between cases. |
Hi,
great work with the code there! I had my 1st experience with py but managed to run it (thanks for the detailed how to).
Here is a question: would it be possible to optimize CF/Links configuration for the given keys parameter? Often some portals won't drop as many keys as we like, while others do it everytime. Eventually I end up waiting burnout cylces to collect 1-2 missing keys and having a load of others.
So, if I could omit the maxed out CF configuration for the sake of making the best out of the keys I have that would be awesome.
Regards!
The text was updated successfully, but these errors were encountered: