As I understand debugging, the fact that Roll20 is hosted on its own server and we lack full access to the operating code prevents using standard debugging tools that generally require running the entire application locally. As a result, instead of using watchlists and setting breakpoints to observe real-time property values and the like, we're all sort of doing the equivalent of spamming our code with console.log statements (or variations) to try to get a look at the problem. The Visual Studio Code extension Debugger for Chrome allows VSC to attach to a running Chrome window to enable its debugging tools on whatever Chrome is running. Unfortunately, the extension is no different from the others in requiring you to run the whole thing locally. But I caught this in the extension description and realized I wasn't savvy enough to figure out whether this might work with Roll20 if, say, we were given SSH access on an isolated testing server? Perhaps by invite-only or something, if opening up the code like this makes it vulnerable to malicious code in some way?