Tag: server down (Page 2 of 2)

Patch rolls out, server set to ‘Busy’ all day

Server Busy.

If you tried to log in yesterday, chances are you were met by a menacing image of Blitzcrank before you even logged in. Shortly after the patch went live, Riot had to set the server to ‘Busy’ to manage the traffic when the servers popped up.

That’s how things stayed for the rest of the day. I followed the Server Status forums hoping for a fix, but nothing came until 1AM EST when they shut the servers down for a full restart. Yesterday also marked the first time I’ve seen Riot completely shut down a matchmaking queue. I wasn’t able to queue for 5v5s for a couple hours, which meant queueing in 3s with a pack of players unfamiliar with the map. It was…interesting. I actually saw something other than the usual 5-8 characters on that map, so that was kind of nice.

Everything seem to be working properly today, though, which is good. Can you imagine the backlash if servers were down for the two days directly after a patch?

LoL: The perfect storm

Server farm.I made a post yesterday about my patch day woes, specifically the fact that I had to do a complete reinstall for the patch. It was a long process, impeded by thousands of other players with the same problem. I was talking to a friend who said, “You know, I kinda wish this was a crappier game.” If the game weren’t so good, it would be easy to write off all the technical issues. The game is good, though, great even, so the technical issues are all the more frustrating.

Once I got my game back up and running I hopped into a quick game over lunch. Everything was going splendidly until the other team’s Veigar ran up and dropped Event Horizon. Not typically a problem, but this time it stunned for eight seconds. Eight. Obviously I died, as most people would in an eight second stun. A hotfix came later in the day along with some more server downtime. I figured the worst was over.

I jumped in a game this evening and, low and behold, the server crashed. A post on the forums reveals that a portion of the game servers experienced a power failure, brining matches down for a slew of players. Obviously I don’t blame Riot for this, but it can be hard to keep a level head when so much goes wrong in such a short period of time.

On the one hand, I have to be sympathetic to these guys. They’ve made a great game, so great that they’re growing beyond their means. On the other, I really can’t wait for them to get the hiring process going.

LoL: Did Riot patch too soon?

Server Unavailable.On the whole, I’ve been pretty impressed with Riot for its support. The servers are rarely down, and when they are, it’s typically for short periods of time. Until recently, anyway. It’s no secret that there’s been a lot of server trouble since the last patch. I won’t blame today’s issues on the patch, not in full anyway, but there have been red posts confirming that the latest patch included at least one crash bug. Couple the server-crippling problems with glitches like double spell casting and I have to ask, did they patch too soon?

My answer is yes. Absolutely. Frankly, I don’t know why it wasn’t broken into to two patches. There was so much content that something was bound to go wrong, particularly on a rushed schedule. Granted, the community was getting restless for Pantheon and Gragas, but both in one patch? Why? Pantheon was obviously ready – the only complaint I see about him is his ultimate, which needs very little change in my mind – but Gragas is a confused mess of AP, physical damage, and tanking skills. He doesn’t scale well and fits poorly into most team comps. Why not save him for a later patch.

I wouldn’t bother writing this if it didn’t have me worried about later patches. My hope is that the Twisted Treeline patch will get plenty of testing before it flies through. On the whole, I’d be much happier with six hours of scheduled maintenance each week to roll out small patches than the 10+ hours we’ve had this week to fix the blunders of the latest patch.

Newer posts »

© 2026 Fearless Gamer

Theme by Anders NorenUp ↑