NonSteamLaunchers in constantly and non-stop (every 10s) scanning and spamming for something... like there's no tomorrow. #514
Comments
|
@D33M0N yeah man use the decky plug in version, you have full control. Install it using the NSLPlugin.desktop |
|
I don't have decky. I am using it on my desktop Manjaro, not on SteamDeck. |
|
@D33M0N ah I see, yeah currently that's the only way so far for the service file...what you can do is open up the NonSteamLaunchers.desktop and simply press Stop NSL Gamescanner,, this will stop it until you want to run it again, kind of like how you wanted. |
|
Thank you very much. Another question. This scanner fails to find any Battle.net stuff. I installed battle.net via NSL to steam and installed there hearthstone and Diablo 3. So at bare minimum it should find those 2 games. (as of just now for me is good enough to just start the added battle.net launcher from steam, is perfectly enough... buuut... if it already scans for games, might as well succeed, no?) like: aaand now I see they exist also here: ah, it's using links. But still some weird double-linkage detected... lrwxrwxrwx - deemon 1 sept 21:18 2855760859 -> /home/deemon/.local/share/Steam/steamapps/compatdata/3952400094 /home/deemon/.local/share/Steam/steamapps/compatdata/Battle.netLauncher -> /home/deemon/.local/share/Steam/steamapps/compatdata/2855760859 -> /home/deemon/.local/share/Steam/steamapps/compatdata/3952400094 |
|
@D33M0N the plug in version has the most up to date battle net game scans. I haven't added them into the desktop version yet, been busy as of late. But will do so soon. Sorry about that! |
|
@D33M0N just fixed now I think? #517 (comment) |
I am really confused how I am even able to "update it". just running it again should be already up to date, as it downloads the fresh script again? anyway... running the .desktop and I get the error: "Decky Loader not detected. Please download and install it from their website first and re-run this script to get the NSL Plugin.". But indeed the scan part now works.
just an idea, but .... maybe auto collections for all the different launchers? |
|
@moraroy for some reason it adds TWO Battle.net launchers... 1: "/home/deemon/.local/share/Steam/steamapps/compatdata/Battle.netLauncher/pfx/drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe" not sure if intentional for some reason or bug, but double entries are not cool usually. |
|
@D33M0N definitely a small bug will try to see why, probably a typo somewhere... just to confirm with you you got both game shortcuts now correct? |
|
@moraroy technically "maybe". All 3 of them launch the Battle.net launcher instead of game itself... But then again I am not sure you can even launch the game without launcher.... ... but no, games do not start. They go to respecive games homepage in launcher though at least... so I can just click "play" in launcher. links seem to be correct. not sure if you can somehow actually force the game to launch from command line... |
|
@D33M0N that's literally the whole point lol, all of what you described is necessary for you to get your "Billboard launcher". That's how battlenet stays up to date with each game when you update the battlenet launcher itself. There is only 2 ways that I know of though, that can allow you to bypass the launcher and play battle net games. I haven't implemented this yet into nonsteamlaunchers yet though |
|
@moraroy oh ok. cool. which of the 2 launchers should be the correct one going forward? so I can remove the wrong "non-steam game" from steam for time being. my games are installed though under the Battle.netLauncher and were detected also there, so I assume/hope the one under NonSteamLaunchers is either some old depracated version or something and can be removed. |
|
@D33M0N just delete both and let nsl give you the fresh one, it would only duplicate if there is a difference in properties, most likely between the desktopversion and the plugin |
Why is this necessary? ONCE EVERY HOUR is enough and even then a bit overkill. Or when I somehow run it manually. (is there a way?)
The text was updated successfully, but these errors were encountered: