If RetroAchievements is not showing in Rebit, first check the connected account, reopen the game, and then check whether that exact game release has a supported achievement set. A game launching successfully does not establish that its achievements are available.
If the list already appears and just one achievement fails, skip account setup and investigate that particular challenge. Those are different problems, and repeating the same reconnect routine will not answer both.
This guide uses Rebit's current public integration instructions and RetroAchievements' reporting guidance. It does not claim that a particular game, patch, or challenge has been tested successfully.
Find the stage that failed
| What you can see | Check next | Avoid doing first |
|---|---|---|
| No connected RetroAchievements account in Integrations | Account connection | Replacing your game file |
| Account connected, game runs, but no achievement list | Game release, system and core support | Replaying a long challenge |
| Achievement list appears, but one objective stays locked | Exact requirement and evidence from the attempt | Resetting all achievements |
| An achievement unlock appeared, but your RA profile does not show it | Account identity and whether the unlock reached the service | Deleting your game or save |
Start with the row that matches your screen. Record what you see before changing anything; that gives you a useful before-and-after comparison.
1. Check the account before opening the game
Follow the Rebit RetroAchievements setup guide:
- Open Profile → Settings → Integrations.
- Find RetroAchievements.
- Enter your RetroAchievements username and account password. This field takes the password, not a Web API key.
- Select Connect and check the account shown.
- Reopen the game if it was already running when you connected.
If you recently changed your RetroAchievements password, reconnect in Integrations. Enter credentials only in the account connection interface; do not paste them into a support message or include them in a screenshot.
Write down a simple result: “Account shows connected; reopened the game; list still missing.” That is more useful than “achievements broken,” and prevents the next person helping you from repeating steps you already tried.
2. Separate game recognition from game playback
Rebit's documentation says achievement recognition depends on the actual game file and supported core. Different revisions, translations and patches may not match a set. Also check that you uploaded the game under the correct system.
For example, if an unmodified release has an achievement set, that alone does not prove a translated or patched edition uses it. Treat the patched edition as a separate support question until you have evidence that it is recognized.
Keep this small comparison beside you:
| Your library entry | The achievement set you expect |
|---|---|
| Console/system | Console/system |
| Release, region and revision, if known | Supported release information |
| Patch or translation and version, if used | Whether that modification is supported |
| Core shown by the app, if available | Core support information |
A matching cover or display title is not enough evidence. Renaming a library entry is not a way to change the contents of its game file.
Do not delete your existing entry while diagnosing recognition. Keep your progress intact, and record missing information as “unknown” rather than guessing a revision. If you need to review file preparation, see uploading your own game files. Rebit does not provide copyrighted ROM downloads; bring legally obtained files.
3. If one achievement stays locked, preserve the attempt
Once the correct list appears, read the specific achievement description and any associated guidance. Record the difficulty, game mode, objective and what happened at the moment you expected the unlock.
The official RetroAchievements FAQ directs players to Report an issue on the individual achievement page. Useful evidence includes a screenshot or video, the mode, difficulty and circumstances of the attempt. A missing unlock and an unlock that triggered locally but failed to reach the site need different explanations; describe which you observed.
Do not reset your progress to troubleshoot a single missing award. A manual unlock is a reviewed request, not an automatic recovery feature or a guarantee. Follow the official requirements linked from the FAQ if you need that route.
Already earned it? Check Encore Mode
Rebit offers Encore Mode under Settings → Integrations → RetroAchievements to earn already-unlocked achievements again during play. Turn it off for normal unlock behavior.
If you are replaying an objective you already completed, check its existing status before treating the absence of a new unlock as a failure. Encore is relevant to repeat play; it does not establish support for an unrecognized game.
Send a report that identifies the next step
Use this template for a Rebit integration problem. For a single broken achievement, include its public URL in the report to RetroAchievements instead.
Device and browser/app version:
Game title, system, release/patch version:
Connected account shown: yes/no (no password)
Game reopened after connecting: yes/no
Achievement list visible: yes/no
One achievement or the entire list affected:
Exact message or behavior:
What changed since it last worked:
Screenshot with private information hidden:
You do not need to attach a ROM, BIOS, password or API key. If the game never launches, use Rebit's general troubleshooting guide first: an achievement check cannot resolve a failed game launch.
Before your next long session, connect, reopen and confirm the list you expect. That short check makes achievement-focused browser retro gaming easier to diagnose without sacrificing a save or replaying hours on an assumption.
