@royee354, I will send you a direct message to learn more about your experience with Draft mode. We are seeking user feedback to enhance LiveScripting and better meet user needs.
1 Like
its still not fixed. I insert a package which is kinda big, and after inserting it and trying to edit some file inside a place the scripting editor has a stroke and kicks me out of scripting session, and after that the current studio session is unusable! Attempts to publish the place changes end up in the studio being stuck at publishing and i have to force close it, scripting changes dont apply either after that. Im basically forced to use rojo and that does not work either after studio session breaks
Hi @Profesornoobz1440, sorry to hear that. I’ve just sent you a DM requesting the package file so we can conduct a further investigation.
It is nice to see the feature live, but you can not disable it when Team Create mode is enabled and some of us OG coders liked it that way before where you had to apply the script save before the changes would become active. Right now, having “EditorLiveScripting” disabled has no effect. When it was enabled, is that what is referred to as “Script lock” mode?
Hi @knightmb1, in that case, we suggest that your team enables Draft Mode, which will keep changes local until they are committed. Please note that ‘Script Lock’ mode has been removed, and the ‘EditorLiveScripting’ property will also be removed soon.
1 Like
Ok, that makes more sense about the setting. We never used it before when it was in beta because of frequent disconnects that would interrupt coding. But…I’ve been using it for a while now and only had one time where it lost connection, so it is much more stable now. That was the only issues I remember back in the beta that prevented its full time usage.
Thanks for mentioning the draft mode, I do use this on other projects where I’m not the lone coder and while it does take a little getting use to, totally necessary for coding accountability. 
2 Likes
Hi when using live scripting, an message appeared saying unstable connection. It would not let me write anything I believe until stable connection was back. But when connection came back, all my progress since the last commit was lost and reverted to the last commit. It wasn’t to bad, just lost a couple functions I had wrote in that timeframe was lost, but still a minor inconvenience. I think perhaps every 30 seconds or so the local version of the script displayed on your computer should be saved onto a back up folder, so incase of an unstable connection. And when connection comes back, it should warn maybe that some progress may have been lost, and give the client the option to open the last locally saved script to check if anything was lost.
2 Likes
Really need back the ‘Script Lock’ mode.
Live scripting is great, helped me assist beginners when working in a team. But it is inconvenient when working as a solo scripter.
Sometimes I have a slow and unstable internet, getting stopped in the middle of writing something is just unacceptable. I switched to Draft Mode, it just adds more unnecessary steps and the need to wait for commits. Why force into a more complicated solution when everything worked fine with the ‘Script Lock’?
Since a few days ago the script editor has become unstable every time Studio creates an auto-recovery file, which is extremely annoying as it can last up to 30 seconds before it becomes stable again.
1 Like
If you’re solo and you have problem with Live Scripting, you can still disable TeamCreate. This will save you from the unstable internet issues and can still give you the benefit of saving to the cloud, and also there is no unnecessary steps with Drafts.