In practice that’s a bit of an oversimplification. 9 times out of 10 its more likely you hit a breakpoint and then hit a snag, where there’s no info after hovering over the problem area (the debugger likes to return ‘out of scope’ a lot ). Think sub-components / sub-actors / sub-objects / structs (and pure function calls).
Same goes for watching values. Its only useful some of the time, as by default it often shows the wrong value when its out of scope, which is highly-deceptive for beginners, and why this has been documented in lots of other threads.
The big catch is though, even if you go in and then set a breakpoint on say a sub-component, it may not be possible to debug the value anyway, as the timing is off when the breakpoint hits. Or the value of a variable being targeted isn’t accessed there except from external BP’s (nod to vars / components set at design-time).
You also need to always remember to debug the right instance in the first place. But you have to wait until the debugger is running to do that. So overall a lot of the time you need to look for other solutions. For example creating a quick sub-project to find out where problems are. Often the cause is you yourself and bad assumptions, so its a self-inflicted wound. But not always. Sometimes the editor is to blame, and you’ve lost a whole morning debugging a phantom error an editor restart magically fixes.
Going back to the wish-list here. Often there’s no other practical way to debug a problem than inserting a Print String or series of them, and color coding them all. For example in multiplayer especially, because color-coding print string messages from Client1 / Client2 / Server helps to make sense of everything happening rapidly!
Nod to Pure function calls too as they’re quick to code, but a PITA to debug. Its often necessary to create extra vars all the time, just to store intermediate values to aid debugging. And Construction-Scripts??? Lots of gotchas!
It’d also be cool to have an Edit and Continue type feature in Blueprints, with a console window to call or evaluate something while a breakpoint is active. I’m probably dreaming though. Is any of this possible @BrUnO_XaVIeR?