I believe the suggestion is for extented internal debugging to include non send/recieve server messages. Without the need to shove random code into your scripts, or in the case of a bug fixer / tester, into another script that you are unfamiliar with. Your suggestion is basically a manual debugging method, no different than how everybody currently does it already.
I think somebody suggested in this thread already, something similar to a local debug binded to a specific alias or event. ie /debug ALIASNAME that would track the use of the alias and/or allow 'simulation' of the alias with dummy data (user input)... would show the extended logic path taken through the alias (messages in debug window like ALIASNAME: VAR %X IS NOW VALUE, ALIASNAME: IFMATCH FALSE, JUMPING TO ELSEIF/ELSE/END, or similar)
I generally like the suggestion, however i dont believe its a simple feature to implement, so i wouldnt hold my breath for this being added any time soon.
