[Disabled, See Update] New Experiences Have Team Create Enabled

What? This update will be judged because:

  • It negatively affects developers by changing their workflow
  • It negatively affects roblox, they will suddenly have to store every place you make unless you disable the switch baked in to the settings which, again, new devs or some people in general won’t know about

and third

  • there is zero communicated reason for making this change.

this update demonstrates the segregation between developers and Roblox’s decision making process, don’t get me wrong they’ve listened to feedback and are doing a great job (thanks roblox engineers and all), but cases like this could still be avoided by just asking for input, can’t you see just about every single person that replied to this does not want this? Look at the poll posted in the second reply too…
They didn’t explain the reason for this update, not thinking behind it either, and it doesn’t just negatively affect us it also negatively affects them, so why?

Most people here are happy for what they have, but it’s still their right to criticize this update because their workflows are being changed for seemingly no reason (which goes back to my last point, these things should be communicated better), the world isn’t all rainbows and it isn’t mean or wrong to do so…

Edit, what I think: This update would be great if Roblox servers didn’t go down so often or were just more stable, I’m all for this update, if that could be fixed.
I left some points out because others already brought them up.

5 Likes

These long responses are what forums exist for and why you can make them.
It doesn’t solve the problem it explains why it is a problem, that’s the point.

Roblox studio simplifies game development, that’s why most of us learnt it, so why make it more complicated when it shouldn’t and doesn’t have to be?

Don’t forget the same developers that make Roblox games are also the same developers that power Roblox’s existence and make them a multi-billion dollar corporation, we aren’t backseat drivers of the corporation but we are those developers, their profit is from developers, well, developing, what will they do if people don’t want to develop anymore? They should have some say in decisions to avoid that happening.

Also, all this isn’t directed at the engineers they do great, this is directed at the lack of communication.
If I changed your daily routine for seemingly no reason at all how would you react? Do you see why this is a problem yet…?

9 Likes

It would work but it wouldn’t happen.
I wouldn’t do it myself.

This won’t happen for 2 reasons:

  1. Roblox is on the NY Exchange because they need more money and stock is a sure fire way of doing so. They gotta make big numbers go bigger to attract investors. They don’t care about the money devs make outside of PR cus most times they gotta give that money away too lol.
  2. There is way too many devs on the platform to coordinate this. The market is already very cut throat and relinquishing your spot will only cause someone else to take it without guarantee that you’ll take it back.

A poison pill like this will not help and more than likely would get drowned out by everyone yelling about how bad the update is.

5 Likes

I concur. Either this or they’re imposing some sort of new, “live moderation” feature in secrecy.

3 Likes

Uh i just reread the post.
This is a very reasonable update. It’s a beta and it’s not like it’s FORCED to anyone.
They listened to our previous feedback and stopped forcing controversial updates and even gave people who wanted to use it a way to switch it on and off.
we went mob mentality mode

just read the article. its very clear

Yes, it’s probably gonna be forced, and now it’s the fifth time I say this:

That’s why we don’t like this update, okay there’s a switch, but if they keep pushing Team Create, will we have a switch anymore?

2 Likes

no its not going to be forced, and even if so they give a studio setting option to switch it on and off.

Thanks to the people who made this update, please keep the toggle on/off a thing in the studio settings.
Also maybe make sure that everyone knows its not a forced beta.

How do you know it’s not a forced beta? I want to see documentation, if you don’t have it then I can’t believe you, and as already said we are scared that Team Create night become not togglable and will be forced

2 Likes

How do you know it is? It’s easy to turn the tables on all the compliants here.

What do you mean by that? It doesn’t make sense to me

you don’t need documentation because they LEGIT SAY ITS A BETA.
they also show a way to allow it to be toggled even for beta.
SO IF IT IS eventually forced they give you a way that requires 1 button click to change.

You don’t get my point… I said that it’s not THIS update that’s not gonna be togglable, we are scared that maybe future updates they may make it un togglable, did you get what I mean now?

man you guys seriously need to introduce a polls for updates section somewhere
team create should be an option, maybe enabled by default but at least an option always visible. not locked behind a setting.

I don’t understand. I frequently have friends ask me to make scratch code for them or to make small projects to put into their game, and recently my friend asked me to update their code. Because saving to RBXL is now unbound and the cloud is forced, I’m swamped with over one hundred places that I have to run through.

image

It took me an ungodly amount scraping through my places to find out what place was what. This was already bad enough, but being forced to use an inconsistent workflow that outright drops me from the servers if I’m in for too long (or sometimes if I’m gone for 15 minutes, is there a timer?), I’m not even allowed to have what SHOULD be a local file open anymore without first making a new place - so not only am I hogging up space on Roblox servers, but I’m also hogging up space on my own computer! Oh, but we also have local auto-recovery files, why not put that on the cloud as well?

Why are you guys forcing this down our throats? There is absolutely no reason to. People reckon it’s to prevent “unsafe content,” but most content already is stored on Roblox servers, which are moderated heavily; it can’t just be that reason. If the developers that you intend to cater to via these updates can’t even understand why you are making these decisions, you’re not catering to them.

We are not babies that force you to play a guessing game because they can’t speak. A large sum of us are coherent and mature people that have a voice that should be heard. The fact that this is not understood is deeply insulting. There are far too many bug reports and features, that have been unaddressed for literal YEARS, but instead of addressing those, you shove these bloat features that nobody, not even their mothers, nor their grandmothers, heck, not even their twice-removed cousins had asked for, right down our throats.

Now if you guys intend to revert this issue, look at what you did, not only did you guys waste the developers’ time with temporarily giving us an unnecessary workflow hurdle, but you also are wasting your own time AND money to revert this change, plus, you’re also absolutely shattering the rapport you’ve built with your developers after all these years. This all could have been avoided if there was more clear communication between those who lead development and the community of which the development concerns.

I’m not trying to subscribe to a slippery slope fallacy, but giving us unwanted features or modifications that negatively affect the pride and joy will inevitably cause damage to both the player and developer ecosystem that you’ve tried so hard to nurture for all this time. This is exactly what happened to Overwatch. No communication, one patch that absolutely nobody wanted, and then abandonment to work on a new game. And then… the game essentially died wrt players that had stuck by for a long time. Doesn’t that sound familiar, maybe with… what’s going on right now (outside of abandonment)?

9 Likes

It has been a worrying and frustrating 10 days with the majority of comments obviously in condemnation of pushing this feature and we still haven’t gotten a single staff reply or update about the decisions of this feature - whether it’s still pushing ahead, alternatives are being considered, or what. Knowing Roblox’s track record, the lack of reply translates to our feedback not having any weight at all and that this will ship. The beta is just to make sure it doesn’t break, not to take in our feedback, questions and concerns.

I don’t get why staff are so selective in what they respond to. Could we please get some signal from someone who isn’t out to do damage control and will instead just let us know what is going on? Talk with us, the ones who help drive the platform and use this tool on a frequent, maybe daily, basis.

Please.

The contents of developer replies should’ve highlighted that there is a real need to review this update and that it may be more damaging to developers and the platform than anticipated. There are several considerations that just seemed skipped, like how much cloud storage this is wasting.

Offline features benefit everyone. Those with weak internet connections, those who prototype incredibly often, the platform in not needing to devote more expenses to storage knowing how much of it is just going to waste (just because you can afford it, doesn’t mean you should do it), and so much more.

Please just say something. And no damage control. Just let us in on the why and if we can have an alternative or just not go through with this. Team Create is already there and developers should be able to clearly choose if they want it or not. No more “default is the cloud” experience, this was already pretty souring with Ctrl + S defaulting to Save to Roblox[1].

[1] I don’t use that key anymore, I manually click on Save to File now - even if I were to be able to override the keybind, muscle memory has already set in and erased a widely accepted keybind from my mind for Roblox purposes.

10 Likes

Please do not have in enabled by default. Team create can cause problems with importing animations.

Team crate should be OFF by default. This will honestly just be annoying.

2 Likes