Script Injection plugin outputs are contextualized as Studio, not user Plugin

At the beggining of each of my playtesting sessions, I use the output window to view what is going on at launch to determine any bugs that might occur with the launch of a server or client; in this particular game, I have disabled certain plugins from recieving injection privs.
Now whenever I launch a play session I am greeted by the following outputs;


All of these prints are from User Plugins, but they’re being given the context of Studio.
Is there any way to convert these to using the User Plugin context, or is this feature not yet available?

1 Like

Thanks for the suggestion! We’ll look into it :slight_smile:

2 Likes

Please check again. The stack trace showing cloud_171922549 as the root indicates that these are coming from [SEMI-BROKEN] Character Creator - Roblox not a local plugin. It should not be possible for a local plugin to generate this error message.

1 Like

I’m uncertain of the difference between the local plugin / user plugin definitions here.
The error is still here as;


My issue is that they are tagged as Studio output, as opposed to User plugin output.
(My understanding of User Plugin being user-generated plugins.)

Oh. I see. This isn’t about local plugins but about the tagging of the error by its origin (Studio vs User Plugin) - there are two kinds of user plugins - local and cloud. I thought you meant that the error shouldn’t show up at all - which is true of local plugins, not cloud plugins. Local plugins are those RBXM / RBXMX files that you work on just on this machine’s drive vs cloud plugins which you install on all machines with your Roblox account. The button for opening the local plugins folder is next to the plugin management button in the plugins tab.

Let me look into this. Bear in mind that we don’t release new binaries of Studio for a few weeks due to the holiday season.

2 Likes

Appreciate it, hope the team is doing well!