I’d like to add on as my own response to this, even though this question wasn’t directed to me, I too prefer working on games with Team Create off.
My main issue with team-create, is that it requires constant internet access. Me and many other developers I know do not have 100% stable internet access, and as long as the place (without team create) has been opened initially with internet, our development will not be completely stopped and disrupted by it. We can still code, develop and play test, etc if our wifi does go down.
Another problem with team-create is how slow it feels compared to working without team-create. Scripts save and apply instantly, there’s no need for waiting/syncing or anything like that. It’s a much more enjoyable experience. And I can comfortably work if my Wi-Fi ever goes down if I am in the middle of developing.
This is coming from the perspective mainly as a developer without a team. In cases where I do have a team or someone else to work with, I do tend to use team-create as the syncing is great to have. However, for solo projects and games, team create disabled is an ideal experience
Great inplementation!
Though as dekkonot stated, it would be great if that could be done without team-create being turnt on.
This can be a great tool, not only to development teams but for solo use, so i really don’t see the point of having it be team-create exclusive.
This feature is amazing, but also, yeah I totally agree with this.
I don’t use team create often, I’m also the type of person who works with local files and model files only.
I save models, scripts and frameworks as individual files and if I were to work together I might only share the model, place or framework that is relevant for the job since I don’t want to give people access to my ENTIRE place.
Being able to save comments in local files and models is a must imo.
Overzealous text filtering is a pain point we’re super aware of, and we designed the feature with that in mind. We intend to continuously refine our approach to text filtering in order to minimize potential impacts on usability.
If creators run into issues with text filter, we really want to hear about it Making sure the user experience is good on this front is one of our top priorities.
Because risk of leaks, aka, if a team member decides to simply download the file, they’ll just do it without any activity logs or even an option to disable downloading copies of team create experiences.
To protect under 18 year old creators from other people- Wait… you have a strong point here, I can type out anything on a TextLabel without censorship… I can basically talk without censorship through text labels… so text filtering in studio does nothing.
Been excited about this for a while and am so exicited to see it release! Here’s to this being the first of many improvements to TeamCreate and collborative editing tooling on Roblox in the year(s) to come!
Yeah I’m not sure what the point of it is, they can’t be so worried about it since the FilterService doesn’t even work with studio plus I could be wrong I’m not sure if the previous text system had a filter.
Regardless the amount of steps to get someone into studio is way more challenging than trying to direct them off-site to another communication platform if you really wanted to get information out of them.
I respect the intentions with filtering it, it’s always good to keep user safety in mind, but what’s even the point in having ROBLOX’s awful filters on it if it can just be completely defeated with… TextLabels?
Any ROBLOX engineers reading this: DO. NOT. FILTER. TEXTLABELS. That is not the correct move here at all.
I just don’t get why you would put a subpar text filter on these new comments when bypassing it is literally as easy as making a TextLabel. The filter will not do anything but make comments incredibly frustrating to use since any common slang, numbers, long text, or vaguely suspicious words will get nuked. This decision becomes especially pointless when you consider that TextLabels, Scripts, decals, and even physical parts (or plugins such as 3DText!) can be used to completely defeat it. Again, DO NOT PUT FILTERS ON SCRIPTS OR TEXTLABELS. That won’t do anything but make people angry and hinder development.
Honestly, the correct answer here - in my opinion - is to not filter comments at all and just have a built-in reporting feature (preferably one that is actively monitored). Most bad actors are not gonna be using studio to break the rules, they’re going to be using off-platform communication tools where ROBLOX moderation can’t do anything.
And if your too lazy to use a text label then you can rename a object in workspace and name it to anything you want or say anything you want. The name does cut off after a while but there wouldn’t be censorship.
Or you can use a string value and say anything in the value, so many ways to talk in studio without filter lol
You do realize that there are about a million other ways to get inappropriate content on studio, right? putting a filter on studio comments is like putting an eletrified fence gate in space.
Next update be like: You must have ID verification before renaming objects, using gui instances, no string object, and of course no attributes because those can also be named anything and have a string value.
I made this as a plugin 4 years ago but I can’t even hate cause I never fully finished it.
Making sure the user experience is good on this front is one of our top priorities.