Turning on sandboxed mode without RunServerScript or RunClientScript permisson spams output

[052008cooljp (IAmCoolJP)]

Reproduction steps:
Go Open Roblox Studio and click on Workspace. Then change “SandboxedInstanceMode” to expiermental. Proceed to create a regular script or LocalScript and enable sandboxed setting. Then write into the script and you will get a bunch of spammed warnings in the output.

Expected Behavior
Writing in a script that doesn’t have sandboxed enabled when a test isn’t running shouldn’t spam output.

Actual Behavior
It spams a bunch of warning messages saying a permission isn’t enabled when you write into the script.

Last Occurred
5/14/2025

Side Notes

1. This bug only occurs when the script is enabled.
2. This bug also occurs with a LocalScript as well.
3. This bug also occurs when Studio is running in test mode/simulation mode

[WheretIB]

Thank you for the report!

We see the same issue and will be making a fix.

[052008cooljp (IAmCoolJP)]

This bug has just been recently fixed by a recent Roblox Studio update. I will now close this

[052008cooljp (IAmCoolJP)]

@music_man1996 So basically what happens is that in Roblox Studio, when you turn on SandboxedInstanceMode to Experimental and when you turn on Sandboxed on a script. Then you open the Script Editor and start typing into the script without the RunServerScriptpermission (or RunClientScript if it’s a client script) it will start spamming output saying it’s lacking capability of that permission.

Edit: It seems to also occurs when Studio is running in test mode as well