Can you with it remove all variables with the same text as seen in the preview gif
And is the error in the script on the end of the gif fixed there one red indicator left a the end from the gif
Can you with it remove all variables with the same text as seen in the preview gif
And is the error in the script on the end of the gif fixed there one red indicator left a the end from the gif
bro whoever is in the gif (probably admin test accounts) created a lag bomb script that spawns parts at a faster rate than they get destroyed, with throttling
I could easily see this being used as an educational resource for classes that teach beginner level programming through roblox.
Otherwise, itās likely more useful for smaller/younger developers who donāt quite have a grasp on or feel the need to use version control.
woah thanks so much roblox devs we finally got a good update
I like this. Not useful to me as I usually work on my stuff alone though.
Would love to see an easy 3rd party code software support. Iād love to be able to use VS Code as well.
Also instead of this setting being globally utilized in Workspace as a property, on release, please make it a local setting
Just like you change color theme for scripts, I want to be able to toggle that feature. So if I am in the script with the toggle off, it wonāt let anyone in.
Honestly it shouldnāt be available on services.
I literally only use this in specific plugins and when cloning a player character.
True statement.
ā¦ to collaborate in the least productive way possible.
Assuming Iām understanding this correctly, this will effectively undermine features that prevent footguns. If thatās the case, bravoā¦
Thanks, I never knew! As @metatablecatmaid said, a lot of the plugin autocompletion (and even documentation) is pretty confusing and had me asking many questions.
Noticed the new release of the Assistant has allowed many of these questions to be answered.
Yes, This will be very helpful for stuff like this. Agreed 100%
Finally! Iāve been waiting so long for this. Great update
I want some markers/models to be placed in studio without them replicating to the deployed server.
How about putting your models into ReplicatedStorage? Alternatively, I suggest starting another post/thread to discuss the Archivable property. This should be an unrelated topic to LiveScripting.
Wonderful update! Been waiting for this for years!
When using the live scripting feature, the script changes will continue to be local to the team create session (just like they are before the live scripting feature). Deployed servers will only get new source after you publish, and even then only servers started after the publish will reflect your changes. You should not need to start using Archivable to protect your deployed servers when using live scripting.
This is amazing! Amazing update!
bludās coding so bad itās straight up a lag nuke
Really cool but whatās the point if itās not compatible with drafts? Been looking forward to this and Iām disappointed it doesnāt have any practical use. If you are working with teams, you use version control. If you arenāt working with teams, you canāt use this feature. Am I misunderstanding, is this intentional by design?
This is a really long overdue update. Thanks for finally doing this
Cool for multiple scripters to be able to work together. Nice work!
This is interesting, though, why would someone use this over something like rojo?