Super glad I've still saved that image then! :p But I do look forward to whatever changes are coming!
I will say that the error codes, while still a problem, are actually handled better now than way back then. In the past, a sitewide error would shut down an ongoing event for a couple of hours; now, for the most part, it usually takes a few refreshes and the site kicks itself back into action. I can't necessarily speak for everyone though, but that's just what I've experienced throughout this current plot.
Whatever was done during last year's plot (the discovery of Shengui-Guo plot) was fantastic; hardly any Cloudflare errors encountered afaik. again, imperfect memory.
Wanna know more about battling? ❤️ The Official Battle Guide v3.3 ❤️ Need to find books? 🌈 The Book Grind Guide v1.0 🌈
PS: After all of the server changes yesterday, we turned off 50% of our server capacity and the site is still running much better. MongoDB was filling up thousands of requests to those servers and making it impossible for PHP to run. So, in this instance, more servers really wouldn't have helped.
💖 ✨ 🤗
well, the cloudflare errors didn't even start being a problem until a few months after last year's plot. ;)
Petitions don't help with this kind of stuff. Staff wants it fixed as well and they work on it being fixed so no need to petition. This is IT, an angry mob isn't going to make code run smoother. Things are evolving in web development so being patient might pay off because who knows: there might pop up this really good framework that helps fixing things.
Or I might just be calm because lately I spend more time coding instead of playing subeta

Yeah. It's just weird. I think whatever worked back then was perfect, and I wish we could go back to it. Weren't we using a different host at that time?
Wanna know more about battling? ❤️ The Official Battle Guide v3.3 ❤️ Need to find books? 🌈 The Book Grind Guide v1.0 🌈