deleted by creator

I used the greasymonkey script with tampermonkey without any modification. And it seems like that script magically worked even though the code doesn’t look like it applies to all of the cases. Thanks, this helped a lot.

Update: After further testing, the script doesn’t really help a lot, because it broke all the JavaScript used on that website all together, which explains why the debugger stopped spamming. Disabling all the JavaScript is not what I want; I want to be able to use the browser tools to trace certain functions.

curl the source down works, but it makes things more complicated. The source code is obfuscated making it incredibly hard to read. This is where using the web debugging tools shine. If I want to figure out which code is trigger what, I can just look at the call stack. I also wanted to look at the internet traffic to see how things work from there. I could intercept all the HTTP requests but that wouldn’t give things like the call stack. I think it would be much easier if there’s a way stopping the debugger spamming trick.

oh that forever loop caused my browser to crash

That icon did skip over the debugger keyword, but it didn’t solve my issue because it still prevented me from viewing that website’s source. Now the websites just becomes super laggy. I’m assuming that there’s a forever loop that does nothing running in the background now that the debugger keyword constantly gets skipped over.

Can there be a solution where I can replace debugger to something that can cause the thread to sleep for like half a second?

that doesn’t work because the debugger spam spawns a new console/thread or whatever; making a “new file” every time the spam started. There’s no fixed line number to skip over.

What does this mean? Is this latex?