[Feature Request] Make rarity and points optional/customisable with the achievement widget
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
For quite a while I have been using an older version of retroarch, I recently upgraded to just before 1.20.00 as it was a requirement to keep unlocking hardcore achievements, I had originally upgraded to 1.20.00 but really did not like that rarity and points were added to the pop-up with no way of disabling them (CHEEVOS: Add rarity and points to achievement unlock widget)
Not sure if it's my OCD or what, but would it be possible to make these additions togglable in the achievement settings? There's already lots of options in there, so I was a little confused that these were just added with no way of changing back to how the widget looked beforehand.
I'm actually dreading the possibility of this not being changed by next year where I will probably have to update again, this will affect my enjoyment of achievement hunting quite a bit. A few other people piped up about not liking the change when I initially went around asking if anyone knew how to change it back, so I hope this gets considered, it would be nice to have it back how it was, without those and also the ability to 'just' add the points, 'just' add the rarity, or add both to make it like it is in current versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the achievement unlock widget and the achievement settings in the RetroArch source, then trace how rarity and points are added to the popup. Done means settings can independently disable or enable rarity and points, including showing either one or both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100