I don’t have that plugin so it’s not that. I’m sure what @ForbiddenJ said about it being a cloud problem is correct. Just need to get the attention of staff
For me, it only happens sometimes with different plugins when starting studio. It sounds like the plugin loader is loading the plugins twice…
An easy reproduce is my plugin rip… Property Text V2, it happens every time I see it so far.
Even though this happens, all the plugins see to work fine. Although this isn’t critical, it would be nice if I wasn’t getting spammed with this message on start up…
Yea, I’m quite disappointed if it will effect my game. Now I’m not sure to continue my project in that game that it’s giving the output in, or to make a new game and transfer the gamepass purchases…
The errors won’t affect your game whatsoever. Nor do they cause plugins to break/etc.
The only problem with the bug is the spamming of the output on startup.
I think I’ve found how to reproduce it:
- Grab some random plugins.
- From Roblox Studio, turn on Team Create on a group game.
- Close Roblox Studio.
- From the game’s webpage, click on the three-dots, and then click “Edit”.
- You get the error.
Here’s a picture of what’s happening to me. It looks like my plugin’s scripts are being run twice.
I think a fix that plugin authors can do for now is to put a BoolValue named “AlreadyRun” inside each of their scripts, and then set one to true as soon as a script runs. If it is already true, then don’t run.
1 Like
I’ve noticed this issue too. Although in my case it’s to do with the act of updating a plugin instead of getting them by opening Studio. I’ve gone ahead and even made a little video demonstrating this problem with a dummy plugin, with as simple-as-can-be coding.
Video Example
Coding Example
local ToolBar = plugin:CreateToolbar("Empty Test")
local Button = ToolBar:CreateButton("Button","WIP","rbxassetid://2195531164")
print("This is a test!")
plugin.Unloading:Connect(function() print("Unloaded!") end)
I believe this started happening around the same update that allowed for plugins to be independently refreshed instead of needing to refresh the entire list. I’m not certain of the exact version.
This also prevents the plugin function plugin.Unloading from firing, too. Turning off and on the plugin after updating them seems to fix the immediate issue, though will occur again if they need another update.
1 Like
This is still happening, will there be any fix for this soon. As a user who creates and uses plugins a lot, this makes it incredibly hard to work with them. It has been happening for way too long and it’s halting plugin development.
This behavior does not affect plugins saved locally. Consider downloading them with InsertService and then saving them as local plugin models.
Step 1
Step 2
Step 3
This still doesn’t fix the issue at hand, I would like to quickly publish and recieve updates on plugins online without the errors popping up. Also saving as a local plugin forces it to be saved as ‘.lua’, the only workaround is to save to file, change the directory of the model, then save script as a local plugin so that the update can be registered. This isn’t ideal and is a lengthy workaround. Thanks for helping anyway. 
Can we please get some sort of response from staff? Starting to really become a pain in studio 
I just started getting this error today.
Has there been any update, or progress, on the analysis of this issue?
Edit:
Oddly enough, the messages stopped appearing after about two hours. I was messing with transferring and replacing places around and wonder if I just got myself into some weird state as a result. All seems normal to me at the moment.
I have filed a ticket for this internally, but it will not be fixed until 2020 due to the code freeze. In the meantime, you can make sure you are opening the place from Studio to avoid this.
I would also suggest using Studio instead of the website in general: as far as developer-facing content goes, the website is legacy and not actively maintained. If there is anything that prevents you from using Studio to do the same thing, you should make a feature request, as website developer-facing content is not guaranteed to continue existing in the future.
1 Like
This should be fixed as of yesterday. Apologies for the inconvenience.
1 Like
I’m getting this again for file-installed plugins (with ID ‘cloud_0_…’), and now all of my local plugins are broken.
Is the “Plugins” folder in AppData supposed to be deprecated? I still get this issue as well as this one, and it feels like Roblox doesn’t really want to support offline plugins anymore. The second issue I linked has not been fixed for almost a full year, but I have a lot of older plugins that I still have installed as files within the Plugins folder.
We do still support local plugins. This is a bug introduced by a flag flip yesterday, the flag flip has been reverted.
@DataBrain
So I cannot find a trivial repro on my end (I can still build and run a basic local plugin).
Could you please post an example of a local plugin that was not running (generating errors/exceptions) for me to play with?
I’m not sure which ones were breaking together like this, since the flag flip fixed the issue for me, but here’s a smaller one that was breaking:
AnalyzePartDensity.lua (16.7 KB)
You may have to have two local plugins running at once, since this issue seems to conflate the IDs of two separate plugins; IIRC the error was showing up multiple times with the same ID ‘cloud_0_vip’ or something akin to that (this is the plugin that the error was referencing the ID of multiple times: Core.lua (170.6 KB) )
It could also be the fact that I use the same plugin toolbar (“Databrain’s Plugins”) for multiple different plugins.
I think we figured out what the disconnect was. @EchoReaper suggested it’s because you are opening the place directly from the web (like clicking “edit” on website to edit place), as opposed to opening studio to start page then selecting a place to edit.
When I did the “open from website” version I was able to reproduce problem. (At least ‘a’ problem, not 100% sure it’s yours.
Anyway, punchline:
- @EchoReaper is the best.
- We should test launching from website more (when testing I always just open studio and open a place from start page).
- I have a fix which I hope to get live soon.
3 Likes
Getting this again when opening any place through Roblox Studio. All of my local (id 0) plugins are broken.