- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 74
 
Description
I’ve been using NonSteamLaunchers on my Steam Deck for GOG Galaxy. A few weeks ago, everything worked fine: games installed through GOG Galaxy (e.g. LEGO Star Wars) were detected by the NSL scanner and automatically added to my Steam library.
Now, since mid-September 2025, I noticed that newly installed GOG games are not detected by the scanner anymore, even though they install and run perfectly inside GOG Galaxy.
Examples:
LEGO Star Wars → detected correctly.
BioShock 2 Remastered and The Smurfs (installed recently) → run fine in GOG Galaxy, but the NSL scanner does not add them to the Steam library.
Additional info:
Install location: SD card (D:).
GOG Galaxy runs smoothly with GE-Proton 10-17.
The issue is not game-specific: all new installs are skipped by the scanner.
Two weeks ago I completely removed all launchers and the NSL plugin, cleaned up everything, and then reinstalled them from scratch. The problem still persists.
This makes me think it is not a leftover config problem, but rather a recent bug related to how the scanner reads GOG manifests.
Expected behavior:
Newly installed GOG games should be detected by NSL’s scanner and automatically added to Steam, just like before.
Workarounds tried:
Full clean reinstall of NSL + GOG → issue remains
Re-scanning in NSL → still skipped
Conclusion:
Looks like the scanner currently fails to read new GOG installs, even though Galaxy itself recognizes them. Likely caused by a recent change in GOG manifests or NSL parsing logic.