Alright, we're going to call it a day with all the Thorin drama, guys. I figured if it was about SI, onGamers, TSM, etc, it had some relevance to League but somehow you guys managed to devolve the discussion into an issue about race of all things.
On June 14 2014 07:05 Alaric wrote: Vi ult still bugged. I ult Kassadin in the middle of our team. He ults during the suppression and gets over a wall and survives under 150 HP. Later in the same game, I ult him, he doesn't get away. I pressed Q to start charging and release to lock him down. I stay stuck in Q charging animation for the full 3 seconds, the spell never casts (I'm using smartcast). And Riot didn't even acknowledge that she's bugged. They just ignored every single issue related to her so far after the initial QoL.
:<
the vi ult bug you talked about isn't a bug. Or at the very least, it's not a bug with Vi. It's a result of the cc buffering mechanism they implemented way back in season 1. Basically, several years ago Riot implemented a cc buffering mechanism so that if you cast/spam anything while cc is being cast on you, the cc is buffered to apply after what the target casts. This is why you see those funny Lissandra ult bugs where the target dashes away even after getting ulted. It also is the cause of players being able to avoid chain stuns even though it seems like they shouldn't. It was implemented supposedly to make it so players playing with high ping can avoid cc easier. At this point it's probably so rooted in their code they can't just remove it/they don't care.
Here's a thread from official forums talking about it from two years ago. It's not new and at this point it doesn't seem like it's going away. Unfortunately I can't find the official red post about the implementation, but I distinctly remember Riot implementing it. Perhaps other old players remember it.
it's something that pros have been complaining about and lobbying for riot to fix, i promise
On June 14 2014 07:05 Alaric wrote: Vi ult still bugged. I ult Kassadin in the middle of our team. He ults during the suppression and gets over a wall and survives under 150 HP. Later in the same game, I ult him, he doesn't get away. I pressed Q to start charging and release to lock him down. I stay stuck in Q charging animation for the full 3 seconds, the spell never casts (I'm using smartcast). And Riot didn't even acknowledge that she's bugged. They just ignored every single issue related to her so far after the initial QoL.
:<
Didn't that Q lockup bug happen in LCS to voyadominar I find it bizarre that shen has been disabled for like over a month now but vi still runs around bugged up
On June 14 2014 07:05 Alaric wrote: Vi ult still bugged. I ult Kassadin in the middle of our team. He ults during the suppression and gets over a wall and survives under 150 HP. Later in the same game, I ult him, he doesn't get away. I pressed Q to start charging and release to lock him down. I stay stuck in Q charging animation for the full 3 seconds, the spell never casts (I'm using smartcast). And Riot didn't even acknowledge that she's bugged. They just ignored every single issue related to her so far after the initial QoL.
:<
Didn't that Q lockup bug happen in LCS to voyadominar I find it bizarre that shen has been disabled for like over a month now but vi still runs around bugged up
The Vi bugs is relatively simple to fix with a simple client restart. Most of the current bugs (particle glitches, CD timer on ult/activated item) are fixed that way, it's just annoying to have it happen every 2-3 games.
It only happened once to me that game, and it doesn't happen every game, so I don't need to restart the client for it, it's not tha tbug where you're permanently stuck. Had yesterday another game as Lulu where it showed me my ult at the ready, so I confidently follow Nasus and burn E offensively to tag someone, certain I can save Nasus. He gets jumped on, I press R... my ult goes from ready to 5s cd and nothing happens.
._.
It was around 30s when we where mid and I checked it because the enemy was near, by the time we killed the incoming wave and walked up to inhib tower the icon said available. I didn't watch it in between. That's the annoying part because if I could observe it I guess I'd see when it goes off cd despite the timer not being 0 (or it ticks down faster), but as you only notice it when you try to cast well, you haven't been riveting your eyes on it before that.
On June 14 2014 07:05 Alaric wrote: Vi ult still bugged. I ult Kassadin in the middle of our team. He ults during the suppression and gets over a wall and survives under 150 HP. Later in the same game, I ult him, he doesn't get away. I pressed Q to start charging and release to lock him down. I stay stuck in Q charging animation for the full 3 seconds, the spell never casts (I'm using smartcast). And Riot didn't even acknowledge that she's bugged. They just ignored every single issue related to her so far after the initial QoL.
:<
the vi ult bug you talked about isn't a bug. Or at the very least, it's not a bug with Vi. It's a result of the cc buffering mechanism they implemented way back in season 1. Basically, several years ago Riot implemented a cc buffering mechanism so that if you cast/spam anything while cc is being cast on you, the cc is buffered to apply after what the target casts. This is why you see those funny Lissandra ult bugs where the target dashes away even after getting ulted. It also is the cause of players being able to avoid chain stuns even though it seems like they shouldn't. It was implemented supposedly to make it so players playing with high ping can avoid cc easier. At this point it's probably so rooted in their code they can't just remove it/they don't care.
Here's a thread from official forums talking about it from two years ago. It's not new and at this point it doesn't seem like it's going away. Unfortunately I can't find the official red post about the implementation, but I distinctly remember Riot implementing it. Perhaps other old players remember it.
it's something that pros have been complaining about and lobbying for riot to fix, i promise
yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
On June 14 2014 10:40 Ryuu314 wrote: yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
Its a big one yeah. catch up XP being so high is a big one too. pretty hard to make level advantages lead to anything when anyone who gets behind of levels catches up so quickly. minmizes choices a lot and creates "best use" situations for a lot of strategies, which means that anyone should know what to do and doing anything else is objectively bad
On June 14 2014 10:40 Ryuu314 wrote: yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
Its a big one yeah. catch up XP being so high is a big one too. pretty hard to make level advantages lead to anything when anyone who gets behind of levels catches up so quickly. minmizes choices a lot and creates "best use" situations for a lot of strategies, which means that anyone should know what to do and doing anything else is objectively bad
Yeah, they nerfing the rubberbanding XP in the jungle hard though, which I think is great as oine of those guys who loved playing the counterjungle style.
On June 14 2014 10:40 Ryuu314 wrote: yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
Its a big one yeah. catch up XP being so high is a big one too. pretty hard to make level advantages lead to anything when anyone who gets behind of levels catches up so quickly. minmizes choices a lot and creates "best use" situations for a lot of strategies, which means that anyone should know what to do and doing anything else is objectively bad
As long as its not as bad as when nunu could rape your jungles big creeps and out level you by like 5 levels lolol.
On June 14 2014 10:40 Ryuu314 wrote: yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
Its a big one yeah. catch up XP being so high is a big one too. pretty hard to make level advantages lead to anything when anyone who gets behind of levels catches up so quickly. minmizes choices a lot and creates "best use" situations for a lot of strategies, which means that anyone should know what to do and doing anything else is objectively bad
As long as its not as bad as when nunu could rape your jungles big creeps and out level you by like 5 levels lolol.
Or you could just kill the nunu. Thats why people fight red in that brush.
If he is leveling Q early he really can't duel for shit.
On June 14 2014 10:40 Ryuu314 wrote: yea...I remember pros complaining about it when it was first implemented. It's the ultimate cater-to-casuals thing Riot's ever done and the worst part is, it actually lowers skill and impacts gameplay in a meaningful way.
Its a big one yeah. catch up XP being so high is a big one too. pretty hard to make level advantages lead to anything when anyone who gets behind of levels catches up so quickly. minmizes choices a lot and creates "best use" situations for a lot of strategies, which means that anyone should know what to do and doing anything else is objectively bad
As long as its not as bad as when nunu could rape your jungles big creeps and out level you by like 5 levels lolol.
Or you could just kill the nunu. Thats why people fight red in that brush.
If he is leveling Q early he really can't duel for shit.
killing nunu solo in the jungle is alot easier said than done
On June 14 2014 07:05 Alaric wrote: Vi ult still bugged. I ult Kassadin in the middle of our team. He ults during the suppression and gets over a wall and survives under 150 HP. Later in the same game, I ult him, he doesn't get away. I pressed Q to start charging and release to lock him down. I stay stuck in Q charging animation for the full 3 seconds, the spell never casts (I'm using smartcast). And Riot didn't even acknowledge that she's bugged. They just ignored every single issue related to her so far after the initial QoL.
:<
Didn't that Q lockup bug happen in LCS to voyadominar I find it bizarre that shen has been disabled for like over a month now but vi still runs around bugged up
The Vi bugs is relatively simple to fix with a simple client restart. Most of the current bugs (particle glitches, CD timer on ult/activated item) are fixed that way, it's just annoying to have it happen every 2-3 games.
Which is odd, because it's never happened to me and I used to play a ton of Vi and Varus(who has the same issue with his Q.)
EPT
