Re-inventing Debug

[RhoSigma]

Somewhere in the system, there’s a Debug that used to be available for finding and fixing coding errors, but it seems to be no
 longer usable or available.
I would like to see one re-produced that could be used by pleb- coders (like me) easily and effectively, to help find some of 
those elusive bugs we all encounter. I’m not capable of this kind of project, but here are the “bare bones” for an algorithm that 
I believe would be close to what we need:

1.     The declarant that starts the debug feature, _Debug  which is placed before executable code.
2.     Coders place a breakpoint, maybe * or BP, at any points they wish to see the state of their variables.
3.     When run, when the program reaches a BP, it pauses execution, and switches to another screen that displays (only) the 
variables that have changed since the last BP, with their new state.
4.     Pressing a key clears the new screen, returns the original screen and resumes the programme.
5.     A closing key is needed for when coding is complete, that removes all BPs and the Debug declarant.
 
Whatever is produced, it needs to be simple to use, flexible, and easily accesssed.

This may seem like re-inventing the wheel, but some of our wheels are a bit flat-bottomed or even triangular at the moment!
  Any takers?

I told you the debug feature is still there and working, but if people are to lazy to use the wiki and spend some time to learning by doing, then this is not the fault of QB64.