Thank you, great to hear that Collaborative Editing is working well for your team. Sounds like you have more than one person on your team working on scripts - if there was live editing like Google Docs, wouldn’t that disrupt others on your team if you have partial changes you are still working on?
1 Like
Absolutely! We are adding a warning on publish if you have uncommitted changes that’ll be part of the rollout when we make this on by default.
2 Likes
The concern of disrupting others is extremely valid, especially for teams that have 3 or more people working on the same scripts, and that’s certainly a valid case for many development teams on Roblox.
I think with a commit on close I would at least be happy this didn’t impact me as a solo scripter as the experience wouldn’t change from what it is now, and honestly this would make a huge difference from the current setup for manually needing to commit them. In essence if my changes automatically committed if there were no conflicts to resolve (multiple people have drafts of the same script at the same time) users wouldn’t know the feature was there unless it was helping them.
I think this is the major concern with having the option on be default in it’s current state. It will disrupt current workflows and worse add additional confusion for learning users. I’ve always been impressed with how well Roblox has managed adding deeper and more rich features without baring entry for kids trying to pick up Studio and make a game with little to no knowledge/experience.
I think in my ideal world I’d get to choose if I was going to use Repl like “Multiplayer editing” or Git like revision control and would be prompted when I created a new Team Create which I’d like to turn on (with the ability to change later). Repl has actually shown how successful live editing code can be, and how it is invaluable for peer-to-peer education. Being able to watch my friend code and correct it in live time while also taking over and explaining what I’m doing is exactly what I’d love to see as a potential on Roblox so I could get friends who want to learn to make their first games actually into it, and with Roblox as their platform.
2 Likes
This one extra step can add tons of time and missing it could result in thinking something is broken that has already been fixed.
I’ve encountered this so many times when micro-updating module code when debugging.
If this worked how VSC does live editing, I’d fully support the feature.
2 Likes
I dislike this, bec when the game has 1 scripter, the old system is easier. If you want this feature, pls add feature to snap widgets on 2nd monitor, so the commit widget will not spent so much space on the screen.
2 Likes
I feel that it’s a pro/con situation at that point.
A live editing system would provide users with an intuitive and easy interface that would allow virtually every developer to work in Team Create, however it would definitely require much more communication when it comes to debugging one part of the script.
Meanwhile the commit system of Collaborative Editing is not very simple to someone who has just opened up team create for the first time. A lot of unpublished drafts would accumulate and create confusion as a newer user might not realize that the drafts aren’t published. The positives are that you can safely debug a specific part of a script without worrying about another part being in development.
I wouldn’t say it would disrupt my workflow, but being able to see live updates from fellow scripters would be nice so I could see what exactly they’re working on.
Either way - I’m very happy with how Collaborative Editing is coming up and I definitely am interested in seeing how it evolves and possibly even become better than the proposed live editing concepts. I am extremely glad to see by this thread that feedback is being heard and changes will be made - such as a commit on close option - that will better the platform and its community.
3 Likes
I have to second this, I’m 18 and setting up git was a hassle for me (of course now that it is set up there is no going back, I love it)
I can’t imagine younger devs trying to set that up especially if they are new to development in general
2 Likes
Please no, this update sucks in my opinion. Just makes it 1000 times more harder to manage scripts… 
3 Likes
Please read the post before commenting.
3 Likes
Yes I did, but it’s annoying to turn it off every time I make a new place. I would rather have it like you activate it if you want that “functionality”.
2 Likes
Isn’t the first thing you do when you make a new place * is configure settings like HTTP Enabled. It’s not that hard to tick a box when you’re going through and tweaking a bunch of settings at once.
* unless you’ve ascended to Rojo levels and just have your project.json do it for you lol
3 Likes
Good suggestion on opening Drafts widget for Team Create sessions with Collaborative Editing turned on. We will definitely consider it!
For #3, we recently shipped an update that allows committing multiple scripts as a batch 
Batch Commits for Collaborative Editing are now available!
3 Likes
That’s not the same thing; this still allows you to break code for other people, since other people can receive batched commits without merging their current changes in any one of those scripts. It’s nice to be able to commit multiple at once now for sure, but it seems like there’s always going to be a problem of the code being broken for at least one person until they merge their current changes.
It’s a hard issue to solve under this implementation of collaborative editing; with Git, collaborators can have a fork of outdated, but working code, until they want to merge their changes. This would probably complicate the way TC works, and at that point it might be better to use git with a rbxmx file if you really wanted to collaborate in that way.
2 Likes
In my opinion we need REAL collaborative editing. Like the real deal.
Right now I feel like this collaborative editing just makes the whole thing harder in general.
3 Likes
‘live’ editing is bad. Collaborative editing, while not perfect, is trying to emulate Git - which is a very good thing and forces scripters to use actual development practises.
3 Likes
To be honest, it would be better if it was multiple developers being able to edit at once. The drafts system should be a feature, at least in my opinion, but not a forced feature.
3 Likes
Update: This is now LIVE! Based on your feedback, we display a warning dialog if you publish the game and have uncommitted scripts in Drafts.
3 Likes
I have to be honest that I do not like this update. I think that we should have the option, as when I use team create normally I’m the only one programming, while others on the game are building. I understand the benefits of it, but it should have an option to be disabled, as I think it’s inconvenient for me, rather than right clicking to apply edits. With a few fixes, this update could be great.
1 Like
Based on the thread you can still disable it, this change was that it is enabled by default.
Overall I still don’t love it being enabled by default. It’s an extra thing to change when doing setup, just so that I can continue to use the experience more natural to me.
1 Like
I don’t like this update either, my other scripts can’t see the live updates right away so they rewrite what I write causing confusion and issues.
I also think making this a default isn’t that good of an idea (the hassle). I’d prefer something where both people can edit a script at once and see live updates.