Amazing update, i kinda suck and just code blinded so i always end up debugging, this will be amazing for sure!
We can see how hard the ROBLOX team is working to make it easier to make games, and plugins. Thanks for the update!
100% i always end up forgetting to remove them too.
Combine with with the Better Breakpoints feature and you have essentially Visual Studio’s debugger. Thank you Roblox, this fails to disappoint. Keep pushing updates like this; errors are always a pain for everyone (unless you’re using error()
) and the more tools we have to deal with them, the better.
I’m excited about all the work that’s being done with the debugger.
- Performance is still very noticeably slower than the original debugger.
- Holding the Step Into key crashes Studio.
- You should be able to expand table and object keys in tables, such as in the tree view. They’re very commonly used.
- Plugins should have permission to use the debugger API.
- Table keys should be sorted during inspection.
woah! i cant wait to never use this and continue to print my variables like any normal person would
Full Plugin Debugging Support, Script Editor Mouseover Integration, UI/UX Improvements, Performance Improvements, Responses to User Feedback, Release Plan…
As always, we need it all of this and more A little less printing
oh my god finally I don’t have to tear my hair out over trying to debug things in studio with prints
shoutout to “Log Mode” in the output menu for being the cause of 90% of developer stress.
In my opinion this is one of the greatest updates this year, thank you so much for this debug feature!
Thank you Roblox for all your hard work in this update it’ll save a ton of time and energy for many
Woohoo! Now we don’t have to use print()
to attempt to debug our code! Thanks a bunch.
Love how it looks, not a fan of the scrolling. Always overshoots like crazy. Generally seems to not look/act great when I have it in the small widget I usually put it in.
Any chance it can be smarter about hovering? When I hover over clips here, it should treat it as if I’m looking at video.clips.
Too complicated.
Sticking to print("AAAAAAAAAAAAAAAA")
Awesome. Can’t wait to try it out.
Thank you! I would attempt to nail something and then accidentally break everything and have to resort to printing things a million times.
Hahaha… It might actually be more time efficient to just print the variables tho…
Oh it was sarcastic. I will still be using print
because I use VSCode/Rojo.
Seems like it would be for a pretty niche amount of users. I will still be using warn
and print
because there are less steps involved. Also since I use VSCode + Rojo often. ¯\_(ツ)_/¯