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

On the Inventory tab, add an option for "at the maximum rarity that can be achieved only by combining existing equipment" #57

Closed
cppisking opened this issue Jun 4, 2015 · 7 comments

Comments

@cppisking
Copy link
Owner

Basically, some items are really hard to get. If you have only 1 of the items then "current rarity maximum level" is useful, and if you plan to eventually get 3 of the item, or you have 3 already then "maximum rarity and maximum level" is useful., But if you only have 2, you may still want to know what it's going to look like after you upgrade it as much as possible using your existing materials.

@Endracion
Copy link

Not sure how complex this is to code, but I would really enjoy such a feature - it helps in deciding if I'm going to spend materials to level something up or if it's actually worse than what I already have.

Right now I flip between max stats and current stats and try to figure it out that way, but if it could automatically tell me what the max is given how many times I can currently combine it, it would be amazing.

@cppisking
Copy link
Owner Author

I already have this working in my local build, but it doesn't work for
computing the score, only viewing stats. Still better than nothing. Should
be in the next release
On Thu, Jun 4, 2015 at 7:40 PM Endracion notifications@github.com wrote:

Not sure how complex this is to code, but I would really enjoy such a
feature - it helps in deciding if I'm going to spend materials to level
something up or if it's actually worse than what I already have.

Right now I flip between max stats and current stats and try to figure it
out that way, but if it could automatically tell me what the max is given
how many times I can currently combine it, it would be amazing.


Reply to this email directly or view it on GitHub
#57 (comment)
.

@Endracion
Copy link

Score is just the cherry on top, stats are the most important, so it's awesome if it's working already!

When are you planning on pushing the next build? In time for the awesome new patch?

@cppisking
Copy link
Owner Author

Maybe, I've been kind of slacking. Certainly before next Friday though,
because then I'm leaving the country for 5 minutes and won't be able to put
out further updates until I'm back :-/
On Thu, Jun 4, 2015 at 9:49 PM Endracion notifications@github.com wrote:

Score is just the cherry on top, stats are the most important, so it's
awesome if it's working already!

When are you planning on pushing the next build? In time for the awesome
new patch?


Reply to this email directly or view it on GitHub
#57 (comment)
.

@cppisking
Copy link
Owner Author

Err, 5 weeks. Lol. Not sure where minutes came from
On Thu, Jun 4, 2015 at 9:51 PM cpp king cppisking@gmail.com wrote:

Maybe, I've been kind of slacking. Certainly before next Friday though,
because then I'm leaving the country for 5 minutes and won't be able to put
out further updates until I'm back :-/
On Thu, Jun 4, 2015 at 9:49 PM Endracion notifications@github.com wrote:

Score is just the cherry on top, stats are the most important, so it's
awesome if it's working already!

When are you planning on pushing the next build? In time for the awesome
new patch?


Reply to this email directly or view it on GitHub
#57 (comment)
.

@karryt
Copy link

karryt commented Jun 5, 2015

Haha, was thinking 5 minutes...so stepping in to Canada or Mexico to grab a soda or something? Hopefully you'll be able to keep up with the FFRK events though!

@cppisking
Copy link
Owner Author

This is done, should be in the next release later this week

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

3 participants