[Feature Request] Native trophy/achievement support
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading RetroArch's handling of RETRO_ENVIRONMENT_SET_MESSAGE_EXT, achievement notifications, and Quick Menu core options; the issue does not name specific files or tests. The work spans API and UI changes, notification images and sounds, per-entry icons, and optional RetroAchievements suppression. Done means native achievement support addresses these three requests while respecting user settings.
Written by the indexing model from the issue text.
Description
More modern systems such as the PS Vita, PS3 and Xbox 360 are being ported to cores, and have their own native trophy/achievement features that are different from RA's own RetroAchievements. Implementing these native features has been in discussion already for the Vita3K core, but have run into some limits given current RA architecture.
This request is to address those limits through RA architecture improvements, leveraging RetroAchievements however possible. Specifically:
-
Display of a trophy-specific notification (background box, badge icon, image of trophy "grade" such as gold and silver, and text), and play of sounds such as
unlock.oggfrom sound assets if original sounds are not possible. Since a core cannot currently access RetroAchievements, the only way it shows a notification is viaRETRO_ENVIRONMENT_SET_MESSAGE_EXT, which takes text only. So this could be an extension of that call (or a new one) that lets a core pass an image (e.g. RGBA pixels or a PNG) with a notification and mark it as an achievement. RetroArch would use its achievement widget and play its unlock sound, with the user's own settings for both. This could be used by any core with native trophies/achievements, such as those mentioned above. -
Display of icons for Trophy/Achievement entries listed inside the core's Quick Menu. These icons would need images in core options, or a separate way for a core to give RetroArch a list to show.
-
Optional suppression of actual RetroAchievements for these systems, as they have their own native trophy/achievement systems renderiing them unnecessary.
@WizzardSK please provide any further information to support this request, thanks!
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libretro/RetroArch#20108 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schrodinger/pymol-open-source#532 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
facebookexperimental/hermit#347 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
CTSRD-CHERI/cheribsd#2769 ·
Maintainers usually reply within 2 days
-
good first issue not started
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
CU-Robotics/firmware#257 ·
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100