If you’re facing this problem, you might also notice that no mods or changes are applied to new instances when launched.
The collection of mistakes in Bloxstrap’s operation leads to this issue. This occurs when the accounts you’re launching on enrolled to different client channels. Causing a forced upgrade when you change channels. After an upgrade, configured mods may not apply because the process is skipped if Roblox is already running, which is likely if you’re launching multiple instances.
This problem should be fixed in a future update. For now, you can temporarily solve it by keeping yourself on the production channel. Follow these steps to do so:
- Open Bloxstrap’s installation folder at %localappdata%\Bloxstrap or wherever you installed it
- Edit Settings.json in a text editor (just use Notepad if you don’t have any)
- Make sure that these two settings are set as shown below:
“Channel”: “LIVE”,
“ChannelChangeMode”: 2,
- Save the changes and close the text editor.
After doing this, you shouldn’t have any more problems launching multiple instances.