-
Notifications
You must be signed in to change notification settings - Fork 27
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
[Suggestion] Rarity tier and roll% display for uniques #342
Comments
|
What I had in mind was just the global percentage, not one for each stat. But if you think they could be useful, then sure. |
There are a few mods that I manually modified whenever I stumbled upon them and thought that a reversed bar would be more intuitive. There are also some inconsistencies within the game when it comes to whether the min or max value is better, e.g. the crusader mods "(51-60)% reduced ignite duration on you" and "(60-51)% reduced effect of shock on you".
Do you have a screenshot of that? And how does PoE Ladder's rating work in general? |
Copied from the explanation given to me:
Essentially:
|
Hey there, had to take a break because I got sick and then my dog had an injury. I'm probably going to pick things up again this weekend or so.
I recently noticed that some rules I created broke at some point, which made me consider two things:
I'm leaning towards the second option but haven't checked how much work it would take to implement. An additional benefit would be that this approach is not limited to English game-clients (unlike custom rules).
After playing with that version of the tooltip for a bit, I feel that individual %-values add a bit of glance-value to uniques (similar to how it does for rare items, so it somewhat streamlines usage between the two categories), especially those whose mod-pools are heavily weighted towards one or two specific mods in terms of being build-enabling. |
Yep, looks fine. |
v1.52.0 is now live. As always, thanks a lot for your inputs. |
I suggest adding some stats to unique pop-up:
The text was updated successfully, but these errors were encountered: