dukdukgoos

Doesn't seem to work with the latest versions of LB (tested 13.18 and 13.19)

Thanks for explaining the reasoning. Security is of course important, and I understand now why Launchbox is doing it the way they are. However, GOG and Playnite have been using the "log in, store a local cookie" methods for years and I've yet to hear of anyone's account being hijacked because of it. I guess most people already have Steam Mobile Authenticator and so getting the API key isn't an additional hurdle. Personally I hate those app-based 2fa methods that can lock you out unexpectedly or tie to a particular device. Perhaps Launchbox could offer both methods? Recommend the API method for greater security but have a fallback method for those that don't want or can't use the Steam mobile authenticator app.

It's ridiculous the hoops we have to jump through for Launchbox Steam integration: Custom profile id, API key, Steam mobile authentication app... it's too much! Launchbox should switch to whatever Playnite, GOG, etc are using for Steam integration. Requiring the Mobile auth app is a bridge too far for me...

Me too. Web login works, Launchbox no go

End of support means no more security patches, which means Windows users have to keep an potentially insecure piece of software installed to continue to use Launchbox. I understand that the dependency issues may be difficult, but I hope you'll take this seriously and do it as fast as possible, as having unpatched software on a Windows machine is not a good idea.

As of 12/13/2022 the .NET Core lib that LaunchBox requires has reached End of Life and will no longer get security updates from Microsoft. When will Launchbox be updated to support .NET 6? https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core