DestinyItemManager / DIM

Destiny Item Manager
https://destinyitemmanager.com
MIT License
2.07k stars 642 forks source link

LO: Set maximum desired tier for each stat #10132

Open jerrycarlson opened 10 months ago

jerrycarlson commented 10 months ago

Proposed change

The LO interface prior to the recent revision (which is awesome, by the way) allowed the user the option to specify a floor and a ceiling to each stat, eg., minimum of 3 resilience and maximum of 7 resilience. The recent revision removed these endpoint settings.

Although it would be great to have both endpoint settings back, if I had to choose only one I would request that the team re-implement a way to specify a maximum value for each stat.

Sadly, I'm no UX guru and so do not have any ready recommendation for how this might look/work in light of the recent revision.

How does this fit into your workflow?

Stats that are above what the user considers an acceptable ceiling end up polluting the LO output and increase the amount of work and eye strain necessary to identify an appropriate loadout stat distribution in the LO output (I regularly spend multiple consecutive hours staring at LO outputs when processing new batches of armor and so am rather sensitive to how fatiguing the display can be). Being able to filter out stat extremes makes the analysis much easier and more efficient.

For example, if I would never consider a warlock loadout with resilience > 4, being able to filter that out ahead of time makes the analysis so much easier than having to visually track which stat distributions are out of bounds for my purposes. The stat numbers/symbols in the LO output simply aren't visually distinct enough to make for relatively painless eyeballing.

jerrycarlson commented 10 months ago

A thought for UX implementation, for setting the max value anyway: let the user double-click the stat tier value to toggle the cap on and off. For example, double-clicking "5" in the Intellect stat tier bar would toggle on 5 as the maximum intellect allowed for loadouts to show up in the LO output matrix. Then, double-clicking the 5 again would remove it as a cap. Maybe even change the double-clicked value's box from orange to red or yellow to indicate that it's been set as a cap for that stat.

This way, no additional screen real estate is needed for the min/max setting. Just a thought!

bhollis commented 10 months ago

Thanks, this has been discussed quite a bit and we do have some ideas for how we could reintroduce that setting. That said, the original maximum stat limit was something of a misfeature that would rule out better builds if they happened to go over the maximum. In general we recommend setting the stat order you want, and unchecking the ones you don't want to have maximized, and the top sets will generally be the ones you want to use.

bhollis commented 8 months ago

This was added back in, but only for desktop - you can now shift-click to set a maximum. I'll leave this open because I still want to improve the UX and make it workable on mobile.

jerrycarlson commented 8 months ago

I saw. Thanks!