Thank you for adding a studio settings option to enable the feature in studio, although I prefer it to have an effect across the board rather than just CTRL+N. The feature looks pretty useful especially in group environments when spreading assets into different places quickly but for individual projects it will get in the way and having to turn team-create off by hand is plainly annoying.
3 Likes
Please, have it be able to be disabled permanently as I hate the new system and others seem to agree with that. Offline creation should be a focus and not “forever online” as what I see Roblox trying to strive for.
If you’re forever online; you can lose a lot of progress just from Roblox having a hiccup 
On top of that, I do a lot of working on projects that I just create and then discard afterwards without having to archive it since it doesn’t delete it. Also, what if you just want to make a place with the goal of it being a .rbxl? It will be stuck in your archives and you’ll have to just see it every time you look in there.
Archiving should be used for things you want to use later or for another date, not for deleting items. That’s why it’s called an archive section.
And don’t forget about the File > New with Team Create off setting. It should also apply to the templates page as well with the setting being New files with Team Create off instead of requiring to use File > New for people who don’t use the new baseplate template. I sometimes use the terrain template or classic baseplate template. I personally like the classic baseplate for quickly removing it to make a quick map for my games.
TL;DR
- I don’t like the new system
- Always online leads to loss of progress when servers go down
File > New with Team Create offshould beNew files with Team Create offinstead to include the template page
8 Likes
I feel that I should also have included in my reply where Roblox should be heading instead. If the aim is truly to grow in the industry and become a professional tool, Roblox needs to start attempting to:
- Integrate with existing workflows for game development, including loading local files into studio before uploading them for preview
- Integrate with existing toolsets like git for source management, to allow developers to implement proper CI/CD pipelines (no, I don’t count hacking your way with Rojo)
- Bring back offline studio, so that development is not dependant on Roblox’s server availability
8 Likes
Got this update and honestly, it’s so stupid, it’s laughable.
Why can I no longer double click to create a new place? The fact that this is creating a new place for me while I know full well that now I’ll have place duplicates across my profile and groups filled with usually NDA work. I also never publish to groups unless I know that something is completely foul-proof on my side and the rest of the team can take from it too.
This is giant step backwards for Roblox and honestly, I hope that this gets reconsidered.
8 Likes
I hate this
i liked being able to just open a baseplate to test something not have to wait for it to “load” the team create and having to publish everything to roblox is just a waste of time and why force team create the old system was perfectly fine this update is just a waste of time and recourses and the fact the had to disable and fix it right after it was released really says something.
5 Likes
I am not a fan of this update, for one reason (and the reason I have it disabled):
I don’t want new places to automatically upload to Roblox. I open new local places all the time to test stuff; I don’t want to have thousands of places cluttering my place inventory. I am aware that you can use Ctrl+N (new) to create a local place, but I want local places to be the default.
A solution I would be fine with is: in the new Create section, it should have an option or a checkbox to “create local,” and this preference should save across Studio instances.
3 Likes
Came across this post wondering why a few plugins weren’t working, it’s because all my new instances are with Team Create on. 
I, and MANY OTHERS are not fans of this idea, it’s breaking a lot of fundamentals we’re in need to continue our workflow. I also as a more solo developer do not need to constantly be disconnected from my instances because of ping-related issues (when I’m having good enough bandwidth)
6 Likes
Abysmal “feature”.
Inconvenient, team create scripts are annoying to work with, plus sometimes you dont wanna publish a new place every goddamn time you create a testing place for one thing. Do not force this upon developers.
Not only the above, studio is in a barely functional state right now between interface bugs and stupid things like this. Still doesn’t have offline code execution, or usage of studio whatsoever for that matter.
I dont wanna publish a new place every time I need to test something, I do not understand how as a company you dont understand why forcing people to waste server space is a bad idea.
6 Likes
Where is the “remove feature from studio altogether and under no circumstance re-enable it” option? Might be worth another patch.
2 Likes
Literally the best reply here, could not agree more.
1 Like
This change is pretty bad in my opinion.
I like screwing around at times by opening a new baseplate and then when I am done I prefer closing it without leaving any traces of me being there, which also means that team create is useless for me at that moment sense I am just doing all this alone.
With this update I will have hundreds of places just because I wanted to try something for a minute (because I am used to just clicking “Baseplate” and making a new place without saving it later).
Can this feature be optional to people? I hardly use Team Create and would hope so.
7 Likes
I couldn’t agree more with this statement. This “feature” is more of a hassle than a perk. I’d rather create games in a local file before even considering putting it on my profile or group(s) unless I have a specific reason to do so.
Cloud saving is good on paper, but always has issues in one way or another.
5 Likes
On a fast internet connection (520mbps down, 470mbps up), it takes 4 seconds to open a baseplate. With team create on, this is now about 11 seconds including the mouseclick for the create new button. On more normal internet connections this is likely even longer.
Team create is nothing but a hassle for developers who are not working in a team (the huge majority). Every single detail about it is a downside. Cut it out please.
10 Likes
Also just wanted to throw it out there, script autosaving works worse inside teamcreate. I’ve lost so much work from getting randomly disconnected from a teamcreate for no reason whatsoever and losing hours of work, where the script auto-recovery did nothing to save my scripts.
stop pushing unfinished features
7 Likes
Bruh, my router already doesn’t let me use normal Team Create (i have to vpn through my vps whenever I want to join a Team Create session).
The current way of ROBLOX Studio seemed just fine to me.
I’m not a big fan of the always connected ideology, I don’t like the idea of having all new projects being automatically saved to roblox.
1 Like
For that issue try use a DNS Jumper or change your DNS manually to switch to a different DNS server. Sometimes I’ve had this fix some issues with other applications.
1 Like
Prime example of why this is terrible today.
I was working on a place, wanted to quickly test the scaling of something, so I clicked new to create a new baseplate, with the intention of using test to spawn a character and check the scaling of a chair.
The new window opened, rather than as a baseplate as “LordHenryVonHenry’s place number 1600”
The previous window however got stuck with “Adding current script versions to script version history before closing place RoomBuilding” So for some reason opening that new baseplate made it want to close the existing place, as the existing place was not team create, it seems to have got infinitely stuck on that error, followed by “Loading game (attempt 1)”.
I cannot close that popup, nor can I save, nor can I exit.
If not for local autosaves I would have lost a bunch of work (and I still lost a bunch of work related to my plugins).
All this is presumably caused by it presuming the existing place is a team create place, when it isn’t.
Why…
Just why…
So many developers shy away from team create, for a variety of legitimate reasons, from not having a good internet connection, to the fact if your work gets stolen, and you have team create enabled, you get a copy pasted response saying: “oh check who you gave team create access to”.
Or maybe just the fact they don’t like not having control over when stuff is saved, or they find committing scripts whenever they make changes a pain.
Maybe they’ve just experienced one of the many bugs with team create in the past and want to avoid the hassle.
Switch the default setting on the “file new creates team create enabled”
and don’t you dare remove that setting in the future.
3 Likes
I’m largely a solo developer and I rebuke all this troublesome always online, teamCreate with no team, making it easier to hack, steal, attack, lose data etc Get rid of FE just to do something dumb like this…But Roblox is gonna Roblox and screw up our progress by moving forwards the backwards way instead of doing what is right and just! I have never had a good experience with teamcreate. I want mine always off and away from the clouds…
5 Likes
This so-called “improvement” is a slap in the face to any self-respecting developer.
I love making prototypes, and templates are a very important part of doing that quickly. What I don’t love is having said prototypes be automatically uploaded to Roblox as soon as I make them, creating a new place associated with my account that I have no way to delete, only archive (which in its current state, is equal to “hiding it inside of a disgusting closet that hasn’t been cleaned in the past decade”).
Your “solution” is not good enough. It’s hidden behind a context menu (notice how it’s not available in studio’s start menu?) and only works with baseplates, essentially permanently and irreversibly making all template places accessible only by creating a new one in the platform.
Not only that, but it’s implied it’s temporary…
Your wording implies that once team create is “improved”, this feature will be removed and local files will be impossible to create again. How could anyone unironically think this is a good idea?
This is borderline an insult to any developer that uses rojo or other local solutions or simply anyone that has a less-than-ideal internet connection. Not everything needs to be online and represented in the Roblox platform. This feels like a direct attack against the workflow of many developers, some of them developing your platform’s biggest and most influential experiences.
Development should never be reliant on the cloud. Your aggressive efforts to hide local files behind dark patterns and arbitrary restrictions does nothing but hurt your reputation in the most professional development circle in your platform, makes your creation tools look more like children toys to any outsider and most importantly, puts an unnecessary security risk of having development copies accidentally leak online.
It’s time for this ““vision”” nonsense created by Roblox’s Product Team to stop. Roblox wants to provide more cloud functionality and simplified tooling with their platform, and that’s ok, but that doesn’t mean the proven ways of doing things should be removed in favor of them. This has been shown time and time again to be an issue with Roblox.
“Doing things “automatically” or “via the cloud” is simpler for <13 developers and beginners, so we won’t bother implementing the industry-standard way of doing things, and if it already exists, we’ll straight up hide it behind a bunch of confusing settings and eventually remove it later.”
Every time Roblox makes a controversial update or change to their development tools, this seems to be the root reasoning. It shows a clear disconnect between the product team’s objectives and the objectives of the developers actually making experiences and content that keep this platform afloat and evolving. It applies to everything, from lighting probes not being added because “they can’t be represented as a real-world object” to local files being butchered and turned into second-class citizens in place of cloud saves, which have inherently different qualities and drawbacks and can’t replace each other.
It’s time for Roblox to treat Roblox Studio and Roblox’s engine as a development tool, not as a toy or an attraction for players.
Roblox, following your “vision” and removing (or ignoring) concepts and functionality present in any other engine is delusional and actively puts arbitrary limits in your platform’s capabilities. Please wake up, pull your head up from the sand and read the room. We welcome your efforts to make studio more attractive to first-time developers, but please, not at the expense of everyone else.
Stop replacing traditional local files with always-online cloud saving, stop replacing flexibility and configuration with a single automatic choice, one-size-fits-all simply doesn’t apply for development.
Even the strongest default can’t cover everyone, which is why customization and choice is so important, especially in a tool for developing experiences and games.
15 Likes