Library / SDK
moraroy/NonSteamLaunchers-On-Steam-Deck avatar
moraroy/NonSteamLaunchers-On-Steam-Deck

NonSteamLaunchers puts Battle.net, Epic and GOG inside one Proton prefix on the Steam Deck

Installs the latest UMU/GE-Proton and Non Steam Launchers under 1 Proton prefix folder and adds them to your steam library. Installs... Battle.net, Epic Games, Ubisoft, GOG, EA App, Amazon Games, itch.io , Legacy Games, The Humble Games Collection, IndieGala, Rockstar Games Launcher,PS Plus, Glyph, VKPlay & HoYoPlay, Waydroid and Games on SD Card.

4,441 stars95 forksPythonMIT

At a glance

What is it?
A shell and Python installer that drops third party game launchers into a single compatdata prefix and registers them as Steam non-Steam shortcuts. It handles artwork, collections, play time and save backups, and it cannot fix titles that refuse to run under Proton.
Who is it for?
Adopt NonSteamLaunchers if your library is mostly storefront launchers you already own and you want them on the Deck with artwork, collections and play time rather than a folder of .desktop files you have to open yourself. Skip it if your priority is anti-cheat multiplayer, since the README states those titles fail on Linux game to game, or if you will not run a remote shell on a machine holding your full Steam library.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • moraroy/NonSteamLaunchers-On-Steam-Deck4,441 ★ · +69
Star history
Repository2026-09-232026-11-22
moraroy/NonSteamLaunchers-On-Steam-Deck4.4k4.4k

69 Stars in the last 60 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One compatdata prefix named NonSteamLaunchers holds every launcher

The central design choice is a single Proton prefix. The script installs the latest UMU and GE-Proton builds, then places NonSteamLaunchers under one unique prefix folder in your compatdata path called NonSteamLaunchers, and registers the launchers in your Steam library from there. Nothing about a launcher is reimplemented. Each entry in the library is a non-Steam shortcut pointing at the real vendor client running through Proton.

That arrangement has a practical consequence most Deck users care about: ProtonTricks works out of the box, because the prefix it needs already exists. The install leaves a NonSteamLaunchers shortcut in the library that does nothing on its own, and the documented fix is to right click it, choose Manage, then Hide this Game. If you tick Separate App Id's during install instead, every launcher gets its own prefix and ProtonTricks addresses them individually.

The library mirrors the launcher, additions and deletions in real time

Steam is treated as a view over the launcher rather than a separate catalogue. Games appear automatically as they are installed, and the script attempts to remove them when you uninstall them from the launcher, and collections for games, launchers and web shortcuts are created and removed per launcher. Play time is tracked for non-Steam games, boot videos are pulled per shortcut when they exist, and metadata cards are applied, including Player Count where there is one on Steam.

Two extras sit on top. The music button in the top left of a game page toggles that title's theme music in the client, and it can be swapped with the paste button. RemotePlayWhatever is bundled so two people on the same network can play non-Steam titles together, credited in the README to m4Engi.

Running the installer from the command line with a launcher name

The script is command line ready, so a Decky plugin is optional rather than required. The README pipes the raw script into a shell and passes the launcher name as an argument:

bash
/bin/bash -c 'curl -Ls https://raw.githubusercontent.com/moraroy/NonSteamLaunchers-On-Steam-Deck/main/NonSteamLaunchers.sh | nohup /bin/bash -s -- "Epic Games"'

What you should see afterwards is the launcher in your library and a new folder inside your compatdata path. Distro coverage is broader than SteamOS: the README names Ubuntu LTS, ChimeraOS, Nobara and Arch Linux, and any KDE environment such as openSUSE Tumbleweed on Wayland.

Special .desktop files are written per shortcut as well, so a launcher or game can be started outside Steam entirely.

Ludusavi backups write to /home/deck/NSLGameSaves, and the cadence differs between builds

Ludusavi is preinstalled and configured for save backups, and the output lands in a fixed path:

code
/home/deck/NSLGameSaves

The timing differs by build, and this is the detail a skim misses. The desktop version runs the backup once, at startup, when the main options list appears. The Decky plugin version runs it on every manual scan you trigger. A Decky user who never opens the scan screen gets no backups, which makes an unverified save history look healthy until the day a game is deleted.

The README is direct about the limit: not all games work with this yet, so bear it in mind when deleting or uninstalling games that have not been backed up yet.

Anti-cheat titles fail by game, not by configuration

Local saves, cloud saves and multiplayer work because the vendor launchers still do their job inside Proton. The exception is anti-cheat. The README states plainly that certain anti-cheat games will not work on Linux environments, and that this is decided game to game rather than by any switch in the installer. No amount of prefix tuning changes that.

Two further gaps are worth naming. The community note feature is described as experimental: a note starting with #nsl followed by a space is relayed through an API to other NSL users, and participation starts by opening NonSteamLaunchers and pressing the heart. The feature is marked experimental. And the update path documented is a button: pressing Update Proton GE in either build pulls the newest GE-Proton and UMU and applies a patch that allows Discord game streaming from Game Mode.

pyproject.toml declares a different version from the tag on GitHub

The project metadata carries a number worth checking before you depend on anything version specific. The release history shows v4.2.94 published 2026-10-29, following v4.2.93 and v4.2.92, while pyproject.toml still declares version = "4.2.3" with name = "non-steam-launchers". The packaged version and the shipped release tag disagree, so pinning on the Python metadata alone will mislead you.

The runtime stack is pinned tightly elsewhere. Python must satisfy >=3.11,<3.13, and requirements.txt holds exact versions including python-steamgriddb==1.0.5, vdf==3.4, requests==2.34.2 and python-decouple==3.8. Those four are the direct dependencies declared in pyproject.toml; requirements.txt also pins certifi, charset-normalizer, idna and urllib3. The Docker build mirrors the same constraints on a python:3.11.4-slim-bullseye base and installs with:

bash
python -m pip install -r requirements.txt

NonSteamLaunchers compared with running the Windows launcher under Proton yourself

The difference is not capability. The alternative is manual work: use ProtonTricks or a non-Steam shortcut, point Proton GE at the vendor client yourself, and add each game to Steam one at a time. NonSteamLaunchers does exactly that repeatedly, and adds the parts that are tedious rather than hard: artwork, metadata cards, collections, per-title theme music, play time, save backup scheduling and a microSD layout that relocates the whole prefix and repoints the shortcuts.

The cost is the trust boundary. Installing launchers and games involves a remote shell run from a raw.githubusercontent.com URL on a device that often holds a full Steam library, plus a warning block in the README telling readers that this is the only official repository and that unofficial forks are not affiliated. Logs land at /home/deck/Downloads/NonSteamLaunchers-install.log, or under /home/deck/homebrew/logs/NonSteamLaunchers/ for the Decky build, which is where you look first when a launcher installs but never appears.

Editorial conclusion

Adopt NonSteamLaunchers if your library is mostly storefront launchers you already own and you want them on the Deck with artwork, collections and play time rather than a folder of .desktop files you have to open yourself. Skip it if your priority is anti-cheat multiplayer, since the README states those titles fail on Linux game to game, or if you will not run a remote shell on a machine holding your full Steam library. Verify first that at least one specific title you care about has a working Linux path, because this script covers launcher installation and nothing below it, then confirm a Ludusavi backup actually lands in /home/deck/NSLGameSaves before you uninstall anything.

Frequently asked questions

How do I get NonSteamLaunchers on the Steam Deck?

Run the installer script from the command line with the launcher you want, or use the Decky plugin build once installed. The command line form pipes NonSteamLaunchers.sh from the repository into a shell and passes the launcher name as an argument, for example "Epic Games".

How do I delete NonSteamLaunchers?

The repository ships NonSteamLaunchers.sh, NSLPluginInstaller.sh and NonSteamLaunchers.desktop. The README gives the log locations as /home/deck/Downloads/NonSteamLaunchers-install.log and /home/deck/homebrew/logs/NonSteamLaunchers/ for the Decky Plugin version.

What is a non-Steam launcher?

In this context it is a third party game storefront client such as Battle.net, Epic Games, Ubisoft, GOG, EA App or itch.io. NonSteamLaunchers installs those clients through Proton and registers them in Steam as non-Steam shortcuts.

How do I install NonSteamLaunchers on the Steam Deck?

The README gives a command line ready invocation, so no separate package manager step is needed. It also installs Proton GE and UMU first, and supports microSD layouts that move the entire prefix to the card with the shortcuts repointed at the SD installation.

Official sources

  1. License: MIT
  2. moraroy/NonSteamLaunchers-On-Steam-Deck on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/moraroy-nonsteamlaunchers-on-steam-deck.svg)](https://hysenlabs.com/projects/moraroy-nonsteamlaunchers-on-steam-deck)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/moraroy-nonsteamlaunchers-on-steam-deck.svg)](https://hysenlabs.com/projects/moraroy-nonsteamlaunchers-on-steam-deck)

Was this useful?