RobloxStudioModManager should not become default app for .rbxl and .rbxlx files

[hello-42]

After running RobloxStudioModManager to retrieve & replace new Roblox Studio BuiltInPlugins with old, more ideally-behaving versions of some plugins from BuiltInPlugins, RobloxStudioModManager sets itself as the default program for .rbxl and .rbxlx files.

RobloxStudioModManager declaring itself as the default program to open these file types is intrusive behavior, and forces the user to manually change the app back to Roblox Studio in my OS (Win10) in order to seamlessly start Roblox Studio place files from the command line.

This is important to not have to do, because of the fact that this introduces an extra step where the user has to click through the program's prompt box in order to start Roblox Studio. This defeats the purpose of starting Roblox Studio via the command line (specifically the command start place.rbxl) and can break CI workflow.

[MaximumADHD]

I have to overload the default program because I bootstrap Roblox Studio to an independent directory, and update bootstrapping won't go through unless it runs through a launcher that performs these updates. Using this program assumes you're doing so with the intent of substituting Roblox's usual bootstrapper.

I do agree it shouldn't be showing the user prompt when launching files from the command line unless it's explicitly told to do so—I will implement coverage for this. But your use case is not an intended one and you should fetch the files manually if you really want to keep using Roblox's usual bootstrapper.

If you have the version-guid of the build you want to fetch, you can substitute the guid in the following url to download its BuiltInPlugins:

https://setup.rbxcdn.com/version-0123456789abcdef-BuiltInPlugins.zip

Roblox's version history is logged here: https://setup.rbxcdn.com/DeployHistory.txt