New Feature: Way to reorder hashes

[suspect15]

Currently, developers cannot reorder the hashes on the Hash Management page. Hashes are listed in alphabetical order, but often times the most commonly used hash is buried somewhere in the middle. I think it would make sense to have a way for devs to manually reorder the hash listing to put the most likely to be used hashes at the top.

[ryoxdx]

Seems to me that's alphabetical order. But yeah a manual override would help.

[SoakedTofu]

It might be better if all the base hashes were automatically listed first, followed by the patches.
Super Mario Sunshine is one game that has a lot of hashes.

[redwizard42]

This is more trying to solve the problem when there are a lot of base set hashes. Those ought to be ordered in a way that makes sense. Happens more when different translations are supported, etc.

[Chew]

Yes, ideally hashes are flagged and stored with more relevant info being surfaced (like if it's a base hash, a translation/qol patch, subset patch, etc.) This would make it more organized by default, but then fine turning sorting from there would be useful still.

[wescopeland]

I think us implementing this feature might be an admission that our software can't figure out what matters to the user. It also passes work onto every developer/maintainer of every set - forever.

My perception is the problem is that every hash on the page looks the same. Things are being rendered as peers even though they're not peers. The back-end itself already knows this, but we're not yet leveraging it on the page.

[Jamiras]

I'm not sure if this is what you're alluding to, but I'd recommend something where the most commonly used hashes (#814) are shown first.

We might still want some way to sort the hashes so players can check for specific support, but that leans more into a full table (#717).

[Jamiras]

Also #3753

[suspect15]

An idea that I just had is similar to what Chew suggested above. Perhaps hashes could be designated certain types and sorted by type on the player facing Supported Game Files page. On a hash's management page, it might be helpful if a dev could mark it as an "Official release," Translation," "QoL," or "Other" hash. Hashes could then be grouped on the Supported Game Files page probably starting with Official Releases on top, probably translation next, then QoL and Other below as they are rarely and not especially useful in most cases.