1) Create any plugin
2) Enable plugin debugger:
We’ve promoted two features in our debugging army from “Beta” to “Live”! These are Universal Breakpoints and Plugin Debugging.
Universal Breakpoints make using breakpoints more intuitive by applying them across all contexts (Edit/Client/Server) by default. From here on, breakpoints set in any Script will be copied to all contexts where that script exists. This ensures that the breakpoint you set will always be hit.
New Behavior w/…
3) Set a breakpoint at any line
4) Run the plugin
When the debugger stops at the breakpoint line, it should be able to be stopped, as a normal script debugging.
When the debugger stops at the breakpoint line, the stop button is disabled.
Sometimes, I can’t even close Studio, so I have to abort it via Windows Task Manager
And, even closing and reopening Studio, the “Resume” button is still active!
I have to close Studio and reopen it in order to stop the plugin debugger.
Issue Area: Studio
Issue Type: Freezing
Having same issue. Plugin debugger cannot be exited until all breakpoints are reached due to the stop button being disabled. Only workaround is to temporarily disable ALL breakpoints entirely and click resume, which isn’t ideal if you are debugging multiple scripts since you won’t be able to stop them at their breakpoint line if they are all disabled.
Thanks for the report! We’ll investigate.
It’s being very difficult to debug a plugin because of this bug.
We have feature improvements planned for plugin debugging and this will be addressed when those ship. Thanks!