EPT"Your position in queue: Over 20,000
Approximante wait time: 46 min 40sec"
[Patch 1.0.0.141: Draven] General Discussion - Page 174
| Forum Index > LoL General |
|
Ghost-z
United States1291 Posts
"Your position in queue: Over 20,000 Approximante wait time: 46 min 40sec" | ||
|
iCanada
Canada10660 Posts
On June 26 2012 08:27 TheLink wrote: For the love of god do not learn from Nhat's stream. He and Aphro do so many suicidal things in lane just to find out if they can. No, Nunu/Ezreal can not double kill Janna/Graves at level 2, thats just Nhat and Aphro vs a solo-queue lane. That and he never buys many wards in solo-queue. Watching Xpecial on support is cool but he only plays AP mid in solo-queue so its hard to catch him at it. Krepo is similar and also rages way too hard for my liking. Chauster and GosuPepper troll every game. I remember Curse's support was great to watch but I can't remember his name now. Which Curse? Elementz is Curse NA's Support player, Xinec is Curse.EU's Support Carry. | ||
|
Lmui
Canada6223 Posts
| ||
|
PrinceXizor
United States17713 Posts
On June 26 2012 08:48 Lmui wrote: NA LoL bugged out bigtime with the latest patch and riot lowered the logins/second rate to a really low number to "maintain server stability" so now, login Q's are ridiculously long. Log in early in the day and stay logged in throughout is the best way to handle it. yeaaahhh, also server stability is bs considering all the dcing and everyone on earth having serious issues getting real games in on NA | ||
|
iCanada
Canada10660 Posts
My antivirus just updated, had to restart computer. So much for playing LoL. 55 minute queues OP. | ||
|
PrinceXizor
United States17713 Posts
On June 26 2012 08:54 iCanada wrote: Zzz... My antivirus just updated, had to restart computer. So much for playing LoL. 55 minute queues OP. yeah seriously the worst part is you can't bluff your way into a dodge anymore on NA. team full on non english speakers pick tryn top "AP taric bot" "Kat bot" Morde mid... so i naturally pick Eve surge + promote and call mid (as 5th pick) to bait a dodge, end up having to dodge to avoid the ELO loss.  waiting an hour for it sucks.I guess i should have played it out, since Eve can weirdly mid if you start null magic mantle + 2. Taking 0 damage from minions means you can just right click them in lane and they have to throw everything at you to get you to back off. but besides that lol it's awful. Oh well just goin to play dota 2 instead. | ||
|
Sermokala
United States14104 Posts
Its pretty funny beacuse all the patch was is a bunch of quality of life changes to some champs and other small business that could have waited until the next champ came out but instead they introduced it now and everything went to shit. | ||
|
Goragoth
New Zealand1065 Posts
On June 26 2012 09:07 Sermokala wrote: if you look at the client when you login they have a new stamp for it from the 15th that's around when the problem started. There are new fonts for everything which suggests a major change to the client probably server side. Its pretty funny beacuse all the patch was is a bunch of quality of life changes to some champs and other small business that could have waited until the next champ came out but instead they introduced it now and everything went to shit. They changed a lot of backend/under-the-hood stuff with this patch, hence the breakage. Patch notes only ever contain stuff relevant to players and never things to do with the internals. That's why it's been wreaking havoc (specifically the main problem, or one of the main problems, was that they introduced a new bottleneck on the database side of things which didn't show up in testing but destroyed the servers when it went live). | ||
|
Shikyo
Finland33997 Posts
On June 26 2012 09:00 PrinceXizor wrote: yeah seriously the worst part is you can't bluff your way into a dodge anymore on NA. team full on non english speakers pick tryn top "AP taric bot" "Kat bot" Morde mid... so i naturally pick Eve surge + promote and call mid (as 5th pick) to bait a dodge, end up having to dodge to avoid the ELO loss. waiting an hour for it sucks.I guess i should have played it out, since Eve can weirdly mid if you start null magic mantle + 2. Taking 0 damage from minions means you can just right click them in lane and they have to throw everything at you to get you to back off. but besides that lol it's awful. Oh well just goin to play dota 2 instead. 1 hour queue and 10 elo loss versus a 20min surrender and ~60 ip and 13 elo loss Silly to dodge imo Oh nevermind I guess over there you already dont lose elo for dodging, not sure about here... Lost the last time I dodged | ||
|
Chiharu Harukaze
12112 Posts
On June 26 2012 08:22 PrinceXizor wrote: I'm gonna go ahead and say if Draven is fighting a bruiser 1v1, without red buff, and if the bruiser has any sort of gap closer that draven loses bad, that guy goes all in every time he chooses to auto attack. now ezreal.... that poor poor bruiser. corki? same. ashe? same. Draven in his currently state may actually win. His Q gives him a 85% (!!) AD steriod along with up to 60% MS and 40% AS boost. His passive also boots his Q damage by a further 50% or so. That's... disgusting. In fact, the Koreans have been experimenting with him top lane. Probably even better than release Vayne in terms of raw numbers. | ||
|
iCanada
Canada10660 Posts
On June 26 2012 10:17 Chiharu Harukaze wrote: Draven in his currently state may actually win. His Q gives him a 85% (!!) AD steriod along with up to 60% MS and 40% AS boost. His passive also boots his Q damage by a further 50% or so. That's... disgusting. In fact, the Koreans have been experimenting with him top lane. Probably even better than release Vayne in terms of raw numbers. Does that mean that Draven is getting nerfed next patch? Ironically i dont even think his Q is the best part of his kit, it is the stupidly high attack speed steroid that you can have up the whole teamfight. | ||
|
zulu_nation8
China26351 Posts
| ||
|
Mogwai
United States13274 Posts
On June 26 2012 10:24 zulu_nation8 wrote: every AD loses to equally powered bruiser with or without gap closer at most stages of the game lol they really don't. they only lose lategame when a bruiser gets the jump on them and most are more than capable of freefarming vs. if not bodying your standard bruiser in lane. | ||
|
zulu_nation8
China26351 Posts
| ||
|
Shikyo
Finland33997 Posts
On June 26 2012 10:27 Mogwai wrote: they really don't. they only lose lategame when a bruiser gets the jump on them and most are more than capable of freefarming vs. if not bodying your standard bruiser in lane. In lane... perhaps. In 1v1 though the ranged AD loses just about always unless they can kite for an extended period of time. However even in lane if they get caught without the escape they are usually dead if forced into a 1v1 situation. I actually can't even think of a bruiser who loses 1v1 vs any ranged carry unless they can kite 75% of their hp away without the bruiser getting a hit in... Can you? | ||
|
Sufficiency
Canada23833 Posts
On June 26 2012 09:23 Goragoth wrote: They changed a lot of backend/under-the-hood stuff with this patch, hence the breakage. Patch notes only ever contain stuff relevant to players and never things to do with the internals. That's why it's been wreaking havoc (specifically the main problem, or one of the main problems, was that they introduced a new bottleneck on the database side of things which didn't show up in testing but destroyed the servers when it went live). Here's the problem. Riot has almost certainly modified certain services on the server during the 15th patch. Afterwards the server ran into problems which basically is still happening now. The issue, as far as I can see, is a stress-load issue; we have a long login-queue right now because the server can no longer handle the same amount of players as it could before. In the end I think it's still caused by bugs in their code which is causing higher server load. Also there is the baron bug. I don't even know how they managed to break that. | ||
|
iCanada
Canada10660 Posts
On June 26 2012 10:47 Sufficiency wrote: Here's the problem. Riot has almost certainly modified certain services on the server during the 15th patch. Afterwards the server ran into problems which basically is still happening now. The issue, as far as I can see, is a stress-load issue; we have a long login-queue right now because the server can no longer handle the same amount of players as it could before. In the end I think it's still caused by bugs in their code which is causing higher server load. Also there is the baron bug. I don't even know how they managed to break that. Yeah, baron is scary as hell right now. Taking him is like instathrows now. Dont really matter how ahead you are, that guy just shreds things... scary part is it is seemingly random. You can do like half his HP like normal then suddenly he goes man mode and like instagibs you. One time he just flat out made our whole team too low to finish him off when we were literally uuncontested and went in all above 80%. Was such a "dafuq?" moment. | ||
|
obesechicken13
United States10467 Posts
On June 26 2012 10:47 Sufficiency wrote: Here's the problem. Riot has almost certainly modified certain services on the server during the 15th patch. Afterwards the server ran into problems which basically is still happening now. The issue, as far as I can see, is a stress-load issue; we have a long login-queue right now because the server can no longer handle the same amount of players as it could before. In the end I think it's still caused by bugs in their code which is causing higher server load. If there are any bugs in their code. Any threads or processes that run for longer than they should, then they will continue to run and mess with how much load the machines are experiencing. I don't see why Riot hasn't just restarted their servers if it were a hanging process issue. And since they're so heavily loaded, I'd expect them to have someone to monitor cpu usage by process type. They could also theoretically revert their changes since they probably use version control. Does anyone have any idea of what's going on with the riot servers? Could it be hardware related? | ||
|
Sufficiency
Canada23833 Posts
On June 26 2012 10:58 obesechicken13 wrote: If there are any bugs in their code. Any threads or processes that run for longer than they should, then they will continue to run and mess with how much load the machines are experiencing. I don't see why Riot hasn't just restarted their servers if it were a hanging process issue. And since they're so heavily loaded, I'd expect them to have someone to monitor cpu usage by process type. They could also theoretically revert their changes since they probably use version control. Does anyone have any idea of what's going on with the riot servers? Could it be hardware related? I hypothesize that all the "processes" are running fine, but they don't run as efficiently as they used to because of the recent changes. This also makes it difficult for them to buy new hardware, because the hardware is fine and sufficient but the software has issues. | ||
|
Goragoth
New Zealand1065 Posts
On June 26 2012 10:58 obesechicken13 wrote: If there are any bugs in their code. Any threads or processes that run for longer than they should, then they will continue to run and mess with how much load the machines are experiencing. I don't see why Riot hasn't just restarted their servers if it were a hanging process issue. And since they're so heavily loaded, I'd expect them to have someone to monitor cpu usage by process type. They could also theoretically revert their changes since they probably use version control. Does anyone have any idea of what's going on with the riot servers? Could it be hardware related? My guess as to why they haven't reverted back to Draven again (they already did once so clearly they could do it again) is that they had a hard time identifying the bug(s) that were causing the problems without having the system running at full capacity. By keeping the new code live and restricting log ons they are no doubt trying to pinpoint the problem(s) and fix them as they go. I'd do the same, rather than revert the patch again and stab in the dark hoping to fix the issue. Despite what people might think testing a system to be stable with millions of users without actually exposing it to millions of users is kinda hard. | ||
| ||
