dukdukgoos

Agree with what Aussiedroid wrote re: WMP and MPC-HC. I was able to decline K-Lite with the 13.21 final installer. However, it forced me to install the Windows Desktop Runtime 3.x, which is redundant as I already had a later version installed (8 or 9). After trying to complete the install without installing the Desktop Runtime unsuccessfully a couple of times I gave up, let it install, then uninstalled it after the LB install finished. Everything seems to work fine without it since I had the later version of Desktop Runtime installed. Please update the installer next time to check if Desktop Runtime is already installed (including later versions) before forcing the 3.x version to install. On the positive side I like the media pack feature, great idea!

Can someone please summarize what the plan going forward is VLC/Media Player/K-Lite Codec pack, etc.? I always completely uninstall Media Player (not just disable) and I don't want K-Lite Codec Pack anywhere near my PC, so Launchbox deciding to require it is a pretty big deal to me. Please allow any changes to the installer to be selected/disabled by the user, so we don't have Launchbox making unwanted changes to our PCs.

Yes, sorry for cluttering your plugin thread. I'll file a bug report.

Here's an example: after doing a full set import on .274 with all the default filtering options I get 3490 games imported (much higher than previous sets that were 2800 or so). If I then use filters to select all "gambling" games (which should have all been removed by the import filters) I get 522 games.

What I'm seeing is 13.18 loads, but the interface is broken (no buttons, text missing, etc.). 13.19 doesn't even show up in the menu. I'm surprised this isn't a more popular plugin. The default MAME full set importer never seems to work cleanly for me. I always have to clean up a bunch of extra stuff that doesn't get filtered properly.

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