They did though? As i’ve said the entire point of this update is to make sure developers can opt-out from default Team Create (which is what people didn’t want) even after the update is out of beta. The only thing that people could complain about is the fact that the switch is hidden by a setting, and i’m also against it as I said in my post, so I don’t see your point here.
1 Like
Yes but they spent alll of this time making this update, even though this is not a priority, priorities were waht the community asked not what Roblox wants, obviously depends on the case but still, they should listen more to us
Okay I get your point. You mean they could’ve spent the time of this update on a more requested update. I get that, in fact I agree. But remember Roblox has teams of people working on different updates at the same time. Unfortunately it is not in our power to change their work style and asking them won’t do much. After all Roblox is a company that needs to grow, obviously this update was targeted to big game studios (= the studios that bring the biggest amount of money to Roblox) rather than devs creating games by themselves. The only thing we can do is hope Roblox develops requested updates as soon as possible.
Yes but they are not listening to the community, a lot of people here said that big developers on Roblox don’t even use team crate, so what’s the point?
Team create is already so buggy and broken, I do trust anything to function correctly while using it. This update is only going to break studio so much more, I know it. It’s crazy how is probably going to happen even though the majority of people don’t want it.
1 Like
Nice update, but does that option allows for those who are in the beta program or is it available for everyone?
Ah, yes.
Roblox just being Roblox.
1 Like
This is what happens when there is no alternative to begin with, there is no incentive in stealing customers from somewhere else, therefore a company has no interest in keeping daring changes to a limit.
Are you blind, or did you just blatantly ignore the other jarring half of the issue where simply creating a new place via the “New” Tab (with all the templates) will create a new, archived, place in your inventory?
I do care about the (technically not completely forced) forced team create issue and the vague implication that all developers may be forced to use it in the future. (I’m opted out of the beta because I never use team create)
But what I REALLY have a gripe about is what I just pointed out earlier.
simply creating a new place via the “New” Tab will create a new, archived, place in your inventory
If I actually wanted to create a new place/game that will be in my inventory, I’d press alt+P, also known as PUBLISH.
100% of the time nowadays when I click that “Classic Baseplate” button, I don’t want another game in my inventory, I just want a .rbxl (local) file, if it even gets to the point where I even want to keep the file in the first place.
I publish to a testing experience to then make use of data stores, either via studio or playing.
1 Like
This is not to mention the bigger part of the problem, the segregation of developers and Roblox becoming bigger and bigger, it’s even a stereotype that Roblox doesn’t listen to developers now (whether or not they do), that’s the problem, couldn’t that lead to more changes ignorant of what the developers it’s being made for actually want?
1 Like
I mean, absolutely, truly, a brilliant change that is necessary to the success of the platform.
Now for the 0 out of 200 places I have created I don’t have to turn on team create manually! Truly saving me so much time by having it on by default.
This is sarcasm.
I don’t use team create. It’s slow, it’s inefficient, and it gets in the way of solo developer activities. It just truly goes to show how out of touch roblox is with its developer community, and how it refuses to listen to actual feedback by the people who literally are the reason their platform makes any money.
I assume they did no stakeholder analysis for this change? The primary stakeholder being the developers on the platform who are staunchly against this change?
For teams of developers, maybe there are 1-20 places in TOTAL which need team create. But for each developer there is HUNDEREDS of solo places which under no circumstances need team create, or even need access to the internet. Why would you want a feature that is only needed maybe 1%-5% of the time by DEFAULT? It’s a nonsensical decision with no backed up reasons to why its being implemented.
As a developer, when I use studio, I want to be able to quickly and efficiently build, design, and test code. Team create and Collaboration significantly slow this down to the point that it makes development painful.
Imagine this:
For most development outside of roblox, people can easily design, build, and test code on their local machine and do that quickly and efficiently, since they do not NEED to be connected to a network or data center. Imagine if all development updates and small changes required every single time for a push to be made to git, wait for that push to be made, and then to test, even for the smallest pieces of code that do not need under any circumstances need to be connected to the internet. It would be ridiculous. So why does roblox think this is okay to do? It’s not.
Developers have been begging for offline studio for years. So what do you go and do? You spit into their faces and say, no, actually, what you want is PERMANENTLY online studio (which they don’t need).
I’ll say it again, there is a limit to how much developers will tolerate with how much BS roblox throws at them all the time. What happened to caring about the community? Asking developers what they thought BEFORE making any changes? Explaining the reasons of a change and backing it up with data?
Maybe someone at the company is experiencing sunk-cost fallacy and think because they have worked on a feature for so long it must be good and must go ahead. That’s not the case. Not every feature will be good, not every feature will be worth continuing even after substantial time and investment. Sometimes its better to just call off the whole thing and stop digging yourself into a deeper and deeper hole you can’t get out of.
This is not a good feature. This is not welcomed.
10 Likes
Sunk cost fallacy is exactly what I would believe is the reason all the forced crap updates got pushed on us over the past many years.
5 Likes
Yes, if you enable Team Create, Studio does save it in your archive. I’ve tested it just to make sure. If you switch Team Create off, it’s not going to save it on your profile, and you can simply proceed to save it as a local file if you prefer that. And even if you enable Team Create and still don’t want it to be archived, is pressing Ctrl+S that big of a deal? They mentioned it will go away from your archive if you edit any setting of the game or if you save or publish it. I don’t want to be aggressive to you as maybe you just didn’t understand exactly how it works (they didn’t explain it really well), but I don’t get where all the frustration from people is coming. Remember that creating a place with Team Create on basically forces Roblox to save it on your profile if you want other devs to join since it’s online. It seems Roblox received our feedback and acted accordingly.
Either way I do agree with you that forcing Team Create is not a good decision. I think the automatic save of a game wouldn’t even be a problem if Roblox at least considered adding a Delete Place button.
Please stop forcing the creation of cloud places!
You’ve been trying for the past 4 years to force new places to be automatically created in the cloud. But no one wants this! NO ONE!
People don’t wan’t this! Stop, forcing, this! We don’t want this.
Cloud isn’t always better. This is a good example of that.
In this case cloud sucks and it performs worse in every single way.
At least give us an easy choice and stop trying to force us!
Why do you need to force us to use cloud places. If we don’t wan’t to then stop forcing us!
This makes creating temporary places nearly impossible. I don’t want team create by default so stop forcing it!
It’s fine if this is a choice. But there should always be an easy way to disable this.
6 Likes
We can only hope this gets revised next week so that the beta feature has better functionality.
I would suggest an “Open Local Copy” button here:
Then the issue will be mostly fixed. How hard can that be?
4 Likes
I think everyone has described much of the flaws with this update, however, I’m still really interested in why - and how - this change was passed or developed.
Is it “1984”? Roblox has clearly seen that there is always going to be a bypass no matter what happens or what changes occur.
Is it really easier to access? No - more unnecessary clutter. People can manage their own disk space, and it’s actually less load for Roblox, so this is a negative aspect.
Does it help out people who use Team Create often? Well, not really - as they too either use a group (which is beneficial for things like animations and maybe sounds) or don’t constantly use Team Create - which, once again, many developers use it only rarely.
Once again, don’t forget developers who want to work offline, on the go, or require file sharing to work in a team workspace.
What made you think this was a good idea? Just interested. 
6 Likes
What is the point of this update, I mean not to be rude, but I don’t think anyone cares about this. I mean if we wanted to work with our team just enable it manually I mean we did not need this to be announced or added
3 Likes
This is currently a Beta feature that can be disabled in Studio.
1 Like
I meant to say revised. I’ll edit my post.