When you insert a tool through models you get the follow message:
Honestly, even tho I’ve seen this message a million times, I’m still confused wether to click yes or no to make it spawn in starterpack.
I suggest removing the “(otherwise drop into 3d view)” since it confuses the question and if you dont put it into starterpack you’ll see where it ended up directly anyways.
This be the silliest of all my suggestions but it would be a nice change 
Yes! I have never understood this prompt 
This seems like a reasonable suggestion, we’ll do it!
Why do we even have it to begin with? Seems like a legacy feature to allow unanchored tools to be parented directly to StarterPack without falling through the Workspace in Build mode. In Edit mode, I’ve always just clicked “no”.
I had no idea what “into the 3d view” meant for like 5 years. “Workspace” would have worked
Agree with @EchoReaper
For new developers who don’t understand how tools work, there is no indication that they should be placed in the starter pack.
We don’t have any indication that lights/particles/etc need to be parented to BaseParts, that Frames/Buttons should be placed inside ScreenGuis, nor that LocalScripts should only be placed in select locations – I don’t see what makes tools a special case. I think it’d be great to have a way of showing what should be parented where in general, but not one specific to tools while numerous similar cases don’t receive similar treatment.
When I started studio way back when, I interpreted it like this:
Click yes: Put it in the StarterPack. Simple enough.
Click no: Don’t insert the tool at all.
I got confused when No inserted it anyway.
I thought the “(otherwise drop into the 3d view)” meant that, and this is kind of funky but, it MIGHT go into the 3D view if the tool had some weird property that a noob to studio like me wouldn’t understand, otherwise it’d go into the StarterPack.
Which is the argument that they should, not that the tools shouldn’t.
But if additional prompts were to be added, do they need to appear more than once?
Maybe it should be a preference that the user can choose when they perform the action for the first time, and then it can be changed with a setting later if they choose.
Yes, a save preference tick box would be great, I can easily move it after if I need it esle where.
The short term argument is that the tools shouldn’t – the prompt makes a negligible difference in a problem whose scope is far beyond just tools.
The long term argument is that if there’s an issue with new developers not knowing where to put specific instances, maybe we should have a generic way of communicating that to them (not prompts – those are just annoying) instead of just for a select amount.
This is a great idea, I never really understood the second part of the clause for ages.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.