I’ve had to enable Team Create so I could add someone to studio, and one downside I’ve noticed is breakpoints are not saving. If I set a breakpoint and test, it doesn’t catch that breakpoint. Upon exiting play, the breakpoint is gone. This seems to happen in any script.
As a side note, I have intentionally disabled Collaborative Editing (I don’t like commit)
Enabled Beta Features:
Terrain Tools
New Lua Script Analysis
New Lua VM
Safe Studio Updates
Insert Object Streamlining
Disabled Beta Features
Lua Draggers Beta
Asset Manager
Before Playtest: During Playtest (Server)
Note, the script is in a tool that gets copied to the player. During Playtest (Client) After Playtest:
Breakpoints only show up on the Server during test and are deleted after closing the test.
Hi Chexburger, thanks for bringing this to our attention. The behavior that you are seeing is part feature, part bug.
The “feature” part is that depending on whether you are viewing the Server or the Client, a different set of breakpoints is shown. This happens because the set of files on the Server is different than the ones on the Client. This comes into play when you put breakpoints on files that are children of ServerScriptStorage or ServerStorage in Edit mode, because in Play mode, this files will only be on the Server, and we will therefore not show breakpoints in those files on the Client. If you notice that when you are in Server mode, you are able to see ServerStorage and ServerScriptStorage in the Explorer, but in Client mode you are not. Furthermore, we will only keep breakpoints for files that exist in the same place between Edit mode and Play mode, so we do not currently keep breakpoints of files created during Play mode.
The “bug” part is that depending on the mode you are viewing, we seem to choose whether we bring breakpoints back into Edit mode from Play mode. I have put in a fix for this bug, and we should be rolling it out soon. Thanks again for bringing this behavior to our attention.
