|
On March 30 2015 18:50 AlterKot wrote:Show nested quote +On March 30 2015 12:51 Zdrastochye wrote: It's only doable on very low ping. No chance in hell an east coaster could pull that micro off. When you have virtually no delay, there's nothing stopping you. Yeah that's bullshit. you just have to take ping into account and buffer your spells. I mean, you do buffer them anyway, but in this case youd just have to do it 0.1 second earlier. After whole night of inhouses on NA I can usually do insec kicks and this doesn't seem harder. Actually let me retract that cause I'm not sure at this point how riot's coding works - does it check spell availability client side or server side? Because if it's the former then it'd actually mean that you can only use the second jump 0.1s after it's actually available and buffering wouldn't work.
Yeah big sorry it's not bullshit.
|
Wat do as an adc vs Zac? I tried kiting but that is literally impossible, can't run away because of huge engage range and cc. I was really annoyed since I hadn't seen him in forever and already hated him back then.
|
On March 30 2015 19:58 cLutZ wrote:Show nested quote +On March 30 2015 18:50 AlterKot wrote:On March 30 2015 12:51 Zdrastochye wrote: It's only doable on very low ping. No chance in hell an east coaster could pull that micro off. When you have virtually no delay, there's nothing stopping you. Yeah that's bullshit. you just have to take ping into account and buffer your spells. I mean, you do buffer them anyway, but in this case youd just have to do it 0.1 second earlier. After whole night of inhouses on NA I can usually do insec kicks and this doesn't seem harder. Actually let me retract that cause I'm not sure at this point how riot's coding works - does it check spell availability client side or server side? Because if it's the former then it'd actually mean that you can only use the second jump 0.1s after it's actually available and buffering wouldn't work. It almost certainly checks if you have killed someone server side, which is the important information for the reset. Yeah but here's a thing - if it checks one thing server side but one client side, then you are actually more screwed than if it checked everything server side. First, let's assume it's all server side - If you know that Q will kill the target, then you can just press E after 0.5 seconds or whatever the cast time of Q is and that way you should always perform E right after the target dies, even if it all happens on your screen after a 0.2 second delay. In other words, you perform it automatically - you don't press E on reaction after seeing that you have it available, you treat it like a combo in a fighting game, where it's just muscle memory that you press one spell, wait exactly X time and then press the other.
Now, the problem is that client might first separately check if the spell is avalaible to you. You know, you press E and you immediately get the sound and message that it's on cooldown. If that's the case, you can't do what I described earlier, because you actually do have to receive the information from server that your Q killed the opponent and in that case the delay actually affects you. But if I just made it up and the game actually checks your cooldowns server side then I see no reason why high ping would make a 2-spell combo significantly harder.
|
On March 30 2015 23:24 Doctorbeat wrote: Wat do as an adc vs Zac? I tried kiting but that is literally impossible, can't run away because of huge engage range and cc. I was really annoyed since I hadn't seen him in forever and already hated him back then. ADCs main function in team fights is to get rid of the tanks, kind of. Perhaps in a specific cases like Zac you'll have hard time if you play immobile adc and/or support (team) does not peel for you.
|
On March 30 2015 23:24 Doctorbeat wrote: Wat do as an adc vs Zac? I tried kiting but that is literally impossible, can't run away because of huge engage range and cc. I was really annoyed since I hadn't seen him in forever and already hated him back then. If he is in a position to Q on you, you're in a bad position. Otherwise just run away during his ult and then start autoattacking him I think. This of course only applies if he goes straight for you, otherwise you can probably auto him anyway.
|
On March 30 2015 23:28 AlterKot wrote:Show nested quote +On March 30 2015 19:58 cLutZ wrote:On March 30 2015 18:50 AlterKot wrote:On March 30 2015 12:51 Zdrastochye wrote: It's only doable on very low ping. No chance in hell an east coaster could pull that micro off. When you have virtually no delay, there's nothing stopping you. Yeah that's bullshit. you just have to take ping into account and buffer your spells. I mean, you do buffer them anyway, but in this case youd just have to do it 0.1 second earlier. After whole night of inhouses on NA I can usually do insec kicks and this doesn't seem harder. Actually let me retract that cause I'm not sure at this point how riot's coding works - does it check spell availability client side or server side? Because if it's the former then it'd actually mean that you can only use the second jump 0.1s after it's actually available and buffering wouldn't work. It almost certainly checks if you have killed someone server side, which is the important information for the reset. Yeah but here's a thing - if it checks one thing server side but one client side, then you are actually more screwed than if it checked everything server side. First, let's assume it's all server side - If you know that Q will kill the target, then you can just press E after 0.5 seconds or whatever the cast time of Q is and that way you should always perform E right after the target dies, even if it all happens on your screen after a 0.2 second delay. In other words, you perform it automatically - you don't press E on reaction after seeing that you have it available, you treat it like a combo in a fighting game, where it's just muscle memory that you press one spell, wait exactly X time and then press the other. Now, the problem is that client might first separately check if the spell is avalaible to you. You know, you press E and you immediately get the sound and message that it's on cooldown. If that's the case, you can't do what I described earlier, because you actually do have to receive the information from server that your Q killed the opponent and in that case the delay actually affects you. But if I just made it up and the game actually checks your cooldowns server side then I see no reason why high ping would make a 2-spell combo significantly harder. Everything is governed server side. That's why League is so hard to hack unless you fuck with packets in a way Riot doesn't expect. If you try to do something that the server hasn't told your game is possible yet, it's not gonna happen.
|
On March 31 2015 00:09 Gahlo wrote:Show nested quote +On March 30 2015 23:28 AlterKot wrote:On March 30 2015 19:58 cLutZ wrote:On March 30 2015 18:50 AlterKot wrote:On March 30 2015 12:51 Zdrastochye wrote: It's only doable on very low ping. No chance in hell an east coaster could pull that micro off. When you have virtually no delay, there's nothing stopping you. Yeah that's bullshit. you just have to take ping into account and buffer your spells. I mean, you do buffer them anyway, but in this case youd just have to do it 0.1 second earlier. After whole night of inhouses on NA I can usually do insec kicks and this doesn't seem harder. Actually let me retract that cause I'm not sure at this point how riot's coding works - does it check spell availability client side or server side? Because if it's the former then it'd actually mean that you can only use the second jump 0.1s after it's actually available and buffering wouldn't work. It almost certainly checks if you have killed someone server side, which is the important information for the reset. Yeah but here's a thing - if it checks one thing server side but one client side, then you are actually more screwed than if it checked everything server side. First, let's assume it's all server side - If you know that Q will kill the target, then you can just press E after 0.5 seconds or whatever the cast time of Q is and that way you should always perform E right after the target dies, even if it all happens on your screen after a 0.2 second delay. In other words, you perform it automatically - you don't press E on reaction after seeing that you have it available, you treat it like a combo in a fighting game, where it's just muscle memory that you press one spell, wait exactly X time and then press the other. Now, the problem is that client might first separately check if the spell is avalaible to you. You know, you press E and you immediately get the sound and message that it's on cooldown. If that's the case, you can't do what I described earlier, because you actually do have to receive the information from server that your Q killed the opponent and in that case the delay actually affects you. But if I just made it up and the game actually checks your cooldowns server side then I see no reason why high ping would make a 2-spell combo significantly harder. Everything is governed server side. That's why League is so hard to hack unless you fuck with packets in a way Riot doesn't expect. If you try to do something that the server hasn't told your game is possible yet, it's not gonna happen. In my example it would be one-sided - the game can tell you that the cooldown is avalaible, but then the server would double-check. But now that you mention it, it would make very little sense.
Guess I'll have to play Kha in inhouses to prove how hard this combo is :>
|
Keep in mind he also uses Hydra procs mid jump as well, so if you're going to prove double jumps I want to see triple jumps with Hydra procs midair, since my point about lag was bullshit.
|
You only mentioned hydra procs now, you first responded to a post that explained the double jump. Imo there's a big difference between 2-spell combo and 4-spell combo so I'm willing to admit that the latter would be much harder on high ping :f.
|
He gets several of these jumps via assists or ignite finishing someone too, the jump itself isn't too hard (is the jump "duration" fixed or does it get longer once E is evolved?), pulling it off consistently wrt the timing (and when you have to hit someone while they're in range, since you're moving) is probably the harder part.
|
Well if you watch the video he clearly does use it (like 14 seconds in, did you even watch it?), so thus my point of him being a great low ping player. Being on the east coast I can't imagine being able to do any of that, though physically I'm sure it's not THAT hard to pull off.
|
Baa?21248 Posts
Everything that looks flashy in League is basically 10x more difficult on east coast. Reset champs in particular are significantly harder to play with higher ping.
|
|
|
On March 31 2015 00:41 Zdrastochye wrote: Well if you watch the video he clearly does use it (like 14 seconds in, did you even watch it?), so thus my point of him being a great low ping player. Being on the east coast I can't imagine being able to do any of that, though physically I'm sure it's not THAT hard to pull off. Dude chill. He does a lot of different stuff in the video, when I first responded to you I thought we're discussing the double jump in particular. I think I'll be able to do stuff like that with 200 ping, we might see soon (provided that account I use has Kha'Zix).
|
If you go into a game its actually pretty easy to do the kha double jumps, its just hard to find a use for them and get fed enough that your Q does a good chunk of burst. After the nerf you have to scrap it out a lot more and there is little opportunity to just bounce around assassinating people.
|
Someone just added me and it seems like I'm getting poached, sorry guys I will miss you. + Show Spoiler +[7:28] losleb: ? [7:29] Santa Smurfing: tursime 5ti chovek za top laner za 5ci cuka li ti se ? I don't understand what he is saying yet, but communication is no problem anyway as we see with koreans.
|
Take it, they're offering you loads of money.
|
|
|
|
|
The land of freedom23126 Posts
To be fair, Marin plays A LOT of Ryze, but I don't think T1 are going to bust it out yet.
|
|
|
|
|
|