Invalid ITS LAGGY

every time i use a the history thingy to go back through pages when on a addon page it lags and takes a long time (im putting it in this subject beacuse idk were else to) put it

"History thingy"? Please provide more detail, I have no idea what you're talking about.

bonkeya the fox said:

every time i use a the history thingy to go back through pages when on a addon page it lags and takes a long time (im putting it in this subject beacuse idk were else to) put it

Click to expand...

i think your talking about the history page becuase thats the only thing you're talking about

SeventhSentinel said:

"History thingy"? Please provide more detail, I have no idea what you're talking about.

Click to expand...

I'm pretty sure (s)he was referring to the tab history functionality of the Web browser (back/forward buttons). I did notice yesterday that the SRB2 homepage was down/unresponsive (confirmed at the time using DownForEveryoneOrJustMe.com). I was subjected to a challenge by Cloudflare (as usual, unfortunately), but after passing it it was loading the homepage forever when it said "Redirecting...". Initially I tried reloading the page multiple times and the challenge restarted and froze on "Redirecting..." again and again until I figured out that Cloudflare fails to redirect me to the website because it's down, which proved to be true. The forums weren't down, however. Only the SRB2 homepage.

bonkeya the fox said:

every time i use a the history thingy to go back through pages when on a addon page it lags and takes a long time (im putting it in this subject beacuse idk were else to) put it

Click to expand...

If you still have problems it would be more useful if you provided more details. You can also try these connectivity tests:
Make sure you read the instructions "Before You Start" if you use the bufferbloat test by Waveform. Ideal "ping", "jitter", "packet loss", "latency", and "round-trip time" (RTT) values are as low as possible.

Ah, yeah the MB was acting weird for me too. MB issues don't really belong in Bug Reports, though, that's an issue best brought to staff directly.