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

Display the required bank and CpS to reach the next reward level for Cookie Chains in stats #29

Closed
killergege opened this issue Oct 9, 2014 · 4 comments · Fixed by #601
Assignees
Milestone

Comments

@killergege
Copy link

Could you add to the Cookie Chain stats the required bank and CpS to the next reward level ?
Today, it displays the cookies required for the current chain, but it would be interesting to have information about when you'll get the next level.

This information is available on the Golden Cookie table "Rewards for Cookie Chain" on the Wiki.

Thanks to your awesome addon, this is now the only "outside" information I search when playing Cookie Clicker !

@Aktanusa Aktanusa self-assigned this Oct 10, 2014
@Aktanusa
Copy link
Collaborator

I guess I would need to do that for both wraith and regular golden cookies, huh

@killergege
Copy link
Author

Oh yes, probably.
To reduce the number of lines in the "Chain" part, maybe you could display the golden / wrath values on the same line for "Chain reward" informations.

@Aktanusa
Copy link
Collaborator

That's a good idea. I'll take a look.

@DanielNoord DanielNoord changed the title Cookie Chain : display the required bank and CpS to reach the next reward level Display the required bank and CpS to reach the next reward level for Cookie Chains in stats Nov 26, 2020
@DanielNoord
Copy link
Collaborator

Moving this to later version as it turns out it is pretty difficult to compute this

@DanielNoord DanielNoord added this to the 2.041.4 milestone Feb 21, 2021
@DanielNoord DanielNoord self-assigned this Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants