I'm sorry to hear it is not a simple implementation. I always feel guilty about "feature suggestions" as they basically amount to asking someone to do extra work, but I really appreciate that you read and respond!
I did notice the debugger doesn't update every tick as I assumed it did after I went and looked more closely.
Regarding the perception of a single tick, I'd like to disagree. The eye is quite good at noticing differences and changes of state. Quick example - https://www.dropbox.com/s/49cxynn9onjhs ... .capx?dl=0
In this case it would be a simple yes or no, if the event ran or not. It would show if an event is running when it wasn't supposed to, or vice versa. In a chain of events/conditions, you would be able to see how far down they get activated until. This would let you pinpoint where to start looking for mistakes in conditions.
I understand I can (and do) manually add in debugging stystems, but it is clunky and a bit specific - sometimes you want to check a large if/then subevent chain or function, and it can be useful to see multiple events at once. Also as r0j0 mentioned, such techniques are generally beyond beginners.
I brought this up because I saw something similar in the UI of another scripting program (energy management software), and thought that it was great. The use case is a bit different of course, in that software it is running as you edit the script and you only need to look at the script to begin with. But it shows quickly at a glance what is and isn't running, and I thought something like that applied to C2 could be very useful.
Being able to see and confirm picked objects would be also have amazing utility, but I wouldn't even know where to begin regarding how to represent that in a scalable manner. And you definitely wouldn't be able to process that information in the instant that the event is called.
Anyways if it isn't feasible, that's too bad. Thanks for the discussion though!