Replies: 4 comments 1 reply
-
I never use those sort fields, and I'm not really sure why anyone would, so I'm not sure adding more options is worth the effort. The one thing I would sometimes like to do is to see the locked/unlocked achievements in their original order (without grouping the unlocked first), as the display order often provides insight as to the order of achievements so I can figure out whereabouts in the game something I missed occurs. I see this being more important once tags are implemented, as the user would likely want to filter on specific tags (i.e. missables). |
Beta Was this translation helpful? Give feedback.
-
Also, related: #764 (ability to hide unlocked achievements [hardcore/softcore individually]) |
Beta Was this translation helpful? Give feedback.
-
Something else to consider: Both the standalone overlay and RetroArch list unearned achievements before earned achievements. The website displays earned first. |
Beta Was this translation helpful? Give feedback.
-
Bumping this to say I'd highly value better sort options, yet even the current sorting options being changed to client-side JS would be a huge improvement both for users (quicker) and the site itself (reduced server load with all the page reloads from sorting). My personal use case, and I do this regularly, is to check the "Won by" sort to see what the hardest few achievements are (as they've been earned by the fewest people) to gauge whether I'd be able to Master the set. |
Beta Was this translation helpful? Give feedback.
-
I have some idea for changing the way how achievements are sorted. Before I go into introducing such changes, I want to consult my proposition with you, so maybe there will be some more ideas on how to make it better.
Right now on game page, user can select one of the four pre-defined sorting rules for the achievement list below. By clicking a link, sorting gets applied in ascending manner. If user wants to get descending order, then they need to click the link again.
There are some disadvantages of the way, how it's actually working:
– every time user changes way of sorting, whole page gets reloaded,
– if user wants to change ordering, they need to click the link twice (so page gets reloaded twice as well)
– search engine bots visits those links as well, and they perceive those addressess to be different, but the content of the page is exactly the same (only order of items changes),
My proposition to improve this element, is to change links with parametrized URLs to selects. After changing the option, instead of changing URL, Javascript should reorder achievements list (we don't have anything else to do, as all achievements are loaded already on the page). Also, it should take less space, letting us to provide even more functionality. In my proposition, I added a display setting, wchich lets an user to hide unlocked or locked achievements and see the other ones.
Here is a small visualization, what I have on my mind:
BEFORE
AFTER
(it's not ideal in terms of spacing and alignment, but I was using a new design app I'm not used to, and it even crashed during work, so I just made a screenshot of my actual work. It's just for preview)
Alternatively, we could join sorting and ordering selects into one, and just list all possible options with ordering included.
Let me know, if you support this idea, or if you have some additional ideas on how to make it better.
Beta Was this translation helpful? Give feedback.
All reactions