Thank you for all the great feedback and suggestions on the beta release of Live Scripting, which enables you to code with your peers in real-time when using Team Create. We are pleased to announce that this feature is exiting beta!
Live Scripting is now the default scripting experience in Studio when Team Create is enabled. The legacy Team Create scripting mode, known as ‘script lock’, will be phased out in the coming weeks.
What is Live Scripting?
Live Scripting enables you and your teammates to code together in real-time. It is based on Team Create and it will resolve many of the current friction points in Studio: no need to apply changes anymore, no locking hurdles, and no need for script recovery popups!
Live Scripting automatically saves your scripts every 5 minutes and upon closing (similar to Team Create). You can also save your scripts any time by pressing Ctrl/Cmd + S. These saved versions will be accessible in the Script Version History. As a result of these autosaves, we are removing the script recovery feature in Live Scripting mode.
Of course, we know that it’s not always good to immediately propagate changes to others, especially when working on very complex experiences. As a result, Drafts mode continues to be available and we are committed to making it better. Live Scripting will be the new default script editing mode for Studio in Team Create. In the long term, we plan to make switching between Live Scripting and Drafts as easy and seamless as possible.
Live Scripting is based on the new ScriptEditorService:UpdateSourceAsync
API, our recommended method for editing script source. Plugins that use the now deprecated Script.Source
will face discrepancies in script values. We shared about this change here.
If you wish to opt out of Live Scripting, you have two options:
- Turn Team Create OFF
- Team Create ON, and turn Drafts Mode ON
Resolved Known Issue
We have resolved an issue related to unstable internet connections. Live Scripting demands higher network bandwidth to maintain consistent sessions across all clients and the server. At present, if the network connection is insufficient to sustain session connectivity, to prevent data loss, the Script Editor switches to read-only mode and displays a hint in the editor until the connection quality has recovered. We are committed to ongoing improvements to ensure smoother performance, even in environments with low internet connectivity.
Many thanks to @yohooyohoo, @idevride,@swmaniac, @code4xp,@BobaTops, @sleepyguyray, @iamyourblackjack, @ignotuscaligo, @cruiser_forever, @yipiokay, @Dogekidd2012, @tnavarts, @montximontxi, @lovedanihonjin, @HugoBLH , @altisaltaccount, @ResetVector, @Rusi_002 for making this possible!
Thank you!