I have a system in my mod that's rather rare I think: I raise custom events that I consume myself. It's a way to implement a listener-based approach to certain things rather than calling everything explicitly.
Anyways, the annoying thing with this is that when an error occurs in one of these internal events, it makes the debugger break twice, once inside the event, and then once where the event was raised. I'd like to avoid having to press continue twice (and opening another file) after most errors. I get that this is mostly a me-being-weird problem.
A solution that could work is to have a setting that lists files the debugger should not break in. I think I saw something of the like for a node debugger or something. Could be useful for other situations too potentially.
I have a system in my mod that's rather rare I think: I raise custom events that I consume myself. It's a way to implement a listener-based approach to certain things rather than calling everything explicitly.
Anyways, the annoying thing with this is that when an error occurs in one of these internal events, it makes the debugger break twice, once inside the event, and then once where the event was raised. I'd like to avoid having to press continue twice (and opening another file) after most errors. I get that this is mostly a me-being-weird problem.
A solution that could work is to have a setting that lists files the debugger should not break in. I think I saw something of the like for a node debugger or something. Could be useful for other situations too potentially.