Remember a couple months ago when the client wouldn't load or the server would time out after login?

Aerothal·Apr 23, 2015·1 votes·370 views

there were tons of posts about it, many, many people complained and there was the standard message: check your firewall, your internet, your ports etc...

IT HASN'T HAPPENED FOR A LONG TIME NOW!!! THANK YOU!

But guess what: i did not change anything!!!! So it was all Riot side, despite the Red posts suggesting otherwise and the customer support emails pointing to all the fun network stuff one could change!

I think its great that it got fixed, but there was never an acknowledgement that it was actually Riots problem!

5 Comments

JubbinautApr 23, 20151 votes

But was it, though? Or was it simply a weird interaction between that particular patch and your configuration?

AerothalApr 23, 20151 votes

{quoted}

But was it, though? Or was it simply a weird interaction between that particular patch and your configuration?

possible. but at the time, nothing i tried to change did any good. I had to start/restart the client 10+ times to even get to the login screen and then would get server timeouts all the time on top of that. I tried everything, nothing helped. and then with one of the latest patches...All good no problems. havent seen a post about it since!

JubbinautApr 23, 20151 votes

Well, sure! And obviously a patch resolved the issue, which indicates that it was a client interaction. But that doesn't necessarily mean it was a problem explicitly with the client. It's more likely (given that the issue - while widespread - wasn't universal) that it was an unforeseen interaction with aspects of your system configuration.

The point being this: if they made a change the removed that interaction and prevented the problem, they may have done so without intending to - perhaps without even realizing it. So it's not likely something they'd mention.

AerothalApr 24, 20151 votes

{quoted}

Well, sure! And obviously a patch resolved the issue, which indicates that it was a client interaction. But that doesn't necessarily mean it was a problem explicitly with the client. It's more likely (given that the issue - while widespread - wasn't universal) that it was an unforeseen interaction with aspects of your system configuration.

The point being this: if they made a change the removed that interaction and prevented the problem, they may have done so without intending to - perhaps without even realizing it. So it's not likely something they'd mention.

i don't know man. that was a very widespread issue. happy that its gone. at the same time, my config is nothing special. I have a pc, i have a modem, a router. i have a firewall but allow league app through it. I have all the recommended ports forwarded for league. I mean its a pc. there is NOTHING special that should negatively interact with league. It all came with a patch and then, 6 months or more later went with a patch. And in between that time, Riot tried to tell me it was my setup. thats so dumb. If i was alone with this, i would shut up, but i wasnt. 25% of my friends had the same issues!

JubbinautApr 24, 20151 votes

I was primarily referring to software conflicts and the like. I don't know enough about League to know what it may have had issues with, but I do know enough about repairing computers to know that sometimes the weirdest programs can create havoc when they're both (or all - I've seen some that only showed up with 3+ programs) installed on the same computer.