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.
To claim that live editing it ābadā is prettyā¦ wellā¦ absurd honestly. There are a handful of live editors for code, honestly itās my favorite thing about Repl.it where I do most of my work for pure Lua code, and where I work with a friend when helping teach him basics of coding.
As all systems there are trade-offs, and most of the work comes down to how you manage your code. Itās really no different than if we are using a GIT style and you are working on something the depends on code I have decided to modify which breaks your code as soon as I merge my changes, except now that all happens live.
This is already annoying me and slowing my workflow down. I launch up studio, paste some code in, andā¦ Oh, well now it takes 10 seconds to publish or even start to test your code, and if I test 6 times Iāve already lost a minute Iāll never get back. I disable it and it still makes me commit the script I was working on, which takes like 5 seconds for only 10 lines of code? Now I have to go in practically every game and disable collaborative editing first thing, which is going to take a while. Even if I did want to use this, it takes a second to just look at the many options and think āWhich one do I want? Do I want to accidentally delete all my work or do I want to commit it?ā This should be off by default, and only enabled if someone feels this improves their workflow.
3 Likes
You donāt need to commit your drafts to test them in studio - thatās the whole point. Your drafted scripts go into play solo with you.
Iām completely stunned to see all the resistance to this feature, as itās something that has made my life 10x better since it came out. I am now able to embark on massive systems overhauls and practice a style of coding where I can just jump in and make risky changes without worrying about screwing up the build for my teammates. All the while I am fully capable of testing my progress inside of studio. And If I find my rewrite is going nowhere and has just completely broken everything I no longer have to spend time restoring the game to how it was, I just press a single button and everythingās fixed! It has drastically lowered the engineering cost of major overhauls and rewrites for me and because of this I strongly urge other developers to try engaging with the feature more in this way.
7 Likes
I was referring to my specific case, that some others may share. When Iām testing and fixing bugs, often I will need to test with multiple players as this is a bug that requires multiple players. It takes pretty long to even commit from my test when I made the reply, and I just want a quick way to test and fix bugs with multiple people. There are many different ways that people work and test, some may find this feature terrible for their specific use case. Since we all have different use cases, this shouldnāt be initially forced on us all, we should first choose if we want it or not, not be forced into it and have to opt out. I was fine with this until it was enabled by default, and now itās just an annoying thing to disable when I enter a new team create.
Absolutely agree. Iāve used git and donāt like the commit features. Live editing is better, but obviously in this case that may not be an option and I understand that.
Requiring me to commit and then save is just another keystroke and a waste of time if Iām the only one working on the script anyway. Do not like this commit option at all.
3 Likes
I think the point we are trying to make that this is okay, but Git + Rojo + VSCode + Branch Control is better, so why would we use this?