Amazing! I was whining about needing this just the other day.
So to use this, I need to save individual scripts to roblox?
Can this be/is this retrofitted to work with packages? I structure my packages such that they contain many scripts, and I often get confused as to what’s the real latest dev version thanks to the absolute mess that is local files + published game workflow. I’d love to be able to version scripts inside packages individually rather than per package update.
(It’s difficult to know which “copy” of the game is the true latest; ideally I’d work on the local files only, but then I can’t use published features i.e. datastores, assets etc, which is furiously painful)
Wow, it seems like collaborative editing will actually be worth having on. I’d love to see some sort of log for whenever a person accesses studio and leaves (sessions). This way we can keep track with our own developers to determine suspicious sabotages or in general work hours.
That’s pretty neat, although from the screenshots shown it looks to be very visual/pop-up based and somewhat rudimentary still. Will be looking forward to how this evolves over time. In general I think reducing the amount of visual clutter / spacing / different windows on these features and better integrating it with the script view is important if developers are meant to adopt this over other version control methods. As a programmer reducing visual clutter while working is highly important to me.
You really don’t want Roblox to maintain this and they don’t need to maintain it for it to be usable. Just file a feature request for native access to the file system via plugins instead of needing to stream it via localhost http. This proposed solution (rojo/git/etc natively in Studio) is bad and non-generic. File system access on the other hand is a very broadly applicable feature.
TLDR; should tone it down with the fad and start thinking in problems, not proposed solutions.
Finally, I was waiting for this for too long. Now any developer I get to work with that tries to change my scripts will be catched really easily. This is not only for me, but for many others that have problems with their scammy “developers” where someone insert viruses inside of scripts in their game(s). Thanks!
Hi @R0bl0x10501050 - there is no limit on version history / expiration. Version history is stored in the cloud, not on the local machine. And, no, we don’t have plans for ability to remove older version.
Hi @BostonWhaIer - thanks! Can you elaborate on what you mean by memory allocation for this feature? The script version history is stored in the cloud and list / content fetched when you access the history.
Hi @FilteredStudio, aw sorry to hear that. To clarify couple of things, script version history is not limited to collaborative editing. Version history will be available even if you have collaborative editing turned off. Script versions are stored in the cloud and do not take up storage on your local machine.