Can't create a new project when "Plugin Debugging Enabled" is ON

[rogeriodec_games]

Reproduction Steps

1) Put some plugin script inside C:\Users\%username%\AppData\Local\Roblox\Plugins (with any error that will force Studio to stop the script)
2) In Studio Settings, turn on Plugin Debugging Enabled option

3. Close Studio and open it
4. Create a new project
   

Expected Behavior

The new project should be opened normally

Actual Behavior

The plugin script inside C:\Users%username%\AppData\Local\Roblox\Plugins is being auto-executed after creating the new project.
Due to the script error, it will stop on the error line:

And, due to another bug I already related…

Plugin debugger can't be stopped

Reproduction Steps 1) Create any plugin 2) Enable plugin debugger: 3) Set a breakpoint at any line 4) Run the plugin Expected Behavior When the debugger stops at the breakpoint line, it should be able to be stopped, as a normal script debugging. Actual Behavior When the debugger stops at the breakpoint line, the stop button is disabled. [image] Edit Sometimes, I can’t even close Studio, so I have to abort it via Windows Task Manager And, even closing and reopening Studio, the …

… I can’t go on with the new project.

Workaround

I have to disable the Plugin Debugging option on Studio settings.
But even disabling it, when opening a new project, Studio still creates an error and also opens some other script window:

Issue Area: Studio
Issue Type: Other
Impact: High
Frequency: Constantly

[IcyTides]

Hi rogeriodec_games,
We are investigating the issue that you have linked to. In the meantime, it looks like the error output you are getting is due to an existing user plugin in your local plugins folder executing, then hitting an error. The solution I would suggest to remove this local plugin from the local plugins folder so it doesn’t run automatically. You can find the local plugins folder by adding a Script in any place, right-clicking the script in the explorer, and choosing “Save As Local Plugin…” . The folder that pops up should be where the plugin with the error is running from.
Please respond to this thread with any updates or additional questions.

[rogeriodec_games]

@IcyTides

it looks like the error output you are getting is due to an existing user plugin in your local plugins folder executing, then hitting an error

That’s what I’ve described.

@IcyTides

You can find the local plugins folder by adding a Script in any place, right-clicking the script in the explorer, and choosing “Save As Local Plugin…” . The folder that pops up should be where the plugin with the error is running from.

I know that, therefore I mentioned the original path in the op.

@IcyTides

The solution I would suggest to remove this local plugin from the local plugins folder so it doesn’t run automatically

This is not the solution, this is a workaround.
And, AFAIK, the plugin scripts inside C:\Users\%username%\AppData\Local\Roblox\Plugins shouldn’t be auto executed.

[rogeriodec_games]

As explained here:

Studio autorunning a plugin within the local plugins folder

The button gets created by the script when it runs. There will never be a button to press in the first place unless the plugin has already run. If you want lighter weight plugin loading you can put most of your plugin code in ModuleScripts which only get required once you’ve actually pressed the button that the small bootstrapper script creates (this is the pattern which most of the builtin plugins in Studio use).

… the plugins must be auto-executed because they need to create its buttons first. So I need to split my plugin to avoid the error described in this topic.