We don’t really need studio holding our hand and preventing us from doing things like inserting a ParticleEmitter into a Folder unless it’s going to somehow cause a game-crashing bug. It’s very cumbersome to have to put it into a part and then move it into something else. It’s additional functionality that actually makes the studio experience worse. Please remove it.
I like Corecii’s solution of showing a warning message instead of an error.
The people who have been using Studio for years might not need it, but those who are new or young might (as silly as that sounds for this specific example).
If the Studio team wants to keep this experience for new users then a good ‘compromise’ would be to show a warning and parent the object instead of an error.
Or heck, an option in advanced studio settings that lets us insert anything into anything, like we used to be able to
The warning messages don’t really make sense, like the errors don’t make sense. Particles being stored in a folder isn’t gonna break anything lol
Then in 2 years, we are going to be complaining about the warning and asking to get rid of that.
This is not a Studio issue, it’s by design. ParticleEmitter requires a Part as its parent in order to function properly.
Parts require to be a descendant of Workspace to function properly, but we’re not restricted from placing them in, say, ServerStorage. What if someone wants to store ParticleEmitters in ServerStorage as a template for cloning?
You can always drag it into whatever you want. Or use the command line. It makes total sense for the inserter to throw errors when an object is attempting to be placed in a spot where it won’t function properly.
Alternatively, perhaps there could be a Studio setting that would override this?
My apologies for the two-year old necrobump, but this still seems to be an issue, especially with Studio’s right click to select feature, which makes inserting parts nearly impossible if you right click on a part, as you were able to back in 2015.
I think a solution to this problem would be to have an option to open up the context / advanced options menu to all objects you can insert.
You can already have all deprecated objects show up, why not have objects be able to be inserted into anything?
We need to evaluate all the ways to insert objects (there are currently 10) and then streamline the ones that need it. I will bring this up in our meetings and evaluate if this is a project we can get slated onto the roadmap.