thx for the video ur the best Ive been playing kayle for a while but actually didnt know about ult reseting passive, W TP and hitting drag/baron out of the pit
the W bug has something to do with the lecture of the disks of the computer. The engine used for the game has a lot of years since it's creation and computers have already evolved a lot, therefore making the framerates a lot higher. The problem this causes is related to the frame counting since this is a really important thing for all game engines, making it essential for loading certain stuff (for example some games load certain events based on how many ticks {or fps} happens each time, like the duration of certain events and so on), in this case, the W proc could actually have a duration based on certain amount of fps, let's say 200 fps, but since your computer is loading a LOT more than that it makes the engine to collapse, therefore, Riot could actually made a patch to partially solve it capping the fps limit your computer loads on the background. This interaction can cause a milisencond freeze that looks like a teleport and it happens on all the computers that are loading this interaction. Hope this helps explaining it
I managed to constantly recreate it using this theory, you have to have uncapped fps, more than 200 fps, movement prediction disabled, press W and instantly face the opposite direction your character is facing. This seems to bug the enginge enough.
FYI, braum shield doesn't block kayle melee autos. Braum shield always blocks first instance of damage from the direction, and halves damage to Braum after that (all sources) (think pantheon e but weaker). You're autoing the braum, and he's getting the reduction, but if he was stacked on top of someone, you would hit the person through braum shield.
@@anon1963 Correct. But until investigating it further it was not possible for me to discern which theory applied, I couldn't personally recreate it consistently, and had no way of knowing if it was a Client-Side parsing error or if it was server side or if it was simply a Lag-Related issue. Seeing it actively used shows us that it is a Bug, err feature, in how the Server is handling the data if it renders the same for all parties. We can dive deeper and theorize that it's technically an exploit related to user input, however it appears Riot sees it no differently than animation cancelling, for now...
Do you have movement prediction on when the tp hack happens? I’ve noticed on other champions it’ll happen as well if I have it on and I’m leaving base with ms buff
For the TP Kayle, at view I can say that it has to do with E animation, maybe if you try to W while E animation it will trigger, maybe while casting E or something
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Which mechanic didnt you know before? 🤓
Turns out just the W Tp thing, pershlaps I play too much kayle ._.
I didn't know the melee attack tip.
I didn't know the ultimate reset the duration of passive 😮
Melee attack tip and tp hack, actually sad i didn't know those cus i have 1,5 k almost on kayle 😅
the first one, didn't know the passive could get a reset
i play on 120ms, all my moves are tp hacks
😂😂😂
Frfr lmao
Homie my lowest is 179ms
@ettienneherbst1817 gg
@@ettienneherbst1817bronze elo?
Damn I had no idea about ult resetting passive, that's definitely something to keep in mind
I'm a new Kayle player and your videos have been very helpful. THANK YOU!
thx for the video ur the best
Ive been playing kayle for a while but actually didnt know about ult reseting passive, W TP and hitting drag/baron out of the pit
I miss old Kayle man.
the W bug has something to do with the lecture of the disks of the computer. The engine used for the game has a lot of years since it's creation and computers have already evolved a lot, therefore making the framerates a lot higher. The problem this causes is related to the frame counting since this is a really important thing for all game engines, making it essential for loading certain stuff (for example some games load certain events based on how many ticks {or fps} happens each time, like the duration of certain events and so on), in this case, the W proc could actually have a duration based on certain amount of fps, let's say 200 fps, but since your computer is loading a LOT more than that it makes the engine to collapse, therefore, Riot could actually made a patch to partially solve it capping the fps limit your computer loads on the background. This interaction can cause a milisencond freeze that looks like a teleport and it happens on all the computers that are loading this interaction. Hope this helps explaining it
I managed to constantly recreate it using this theory, you have to have uncapped fps, more than 200 fps, movement prediction disabled, press W and instantly face the opposite direction your character is facing. This seems to bug the enginge enough.
FYI, braum shield doesn't block kayle melee autos. Braum shield always blocks first instance of damage from the direction, and halves damage to Braum after that (all sources) (think pantheon e but weaker).
You're autoing the braum, and he's getting the reduction, but if he was stacked on top of someone, you would hit the person through braum shield.
Wow, I didn t know the bonus and even baron 🤣 thanks!
I've seen the W bug before, I assumed it was a server-side issue or otherwise packet rubberbanding, neat that it's happening on enemy's screen too
It is a server side issue because the game literally is running on the server
@@anon1963 Correct. But until investigating it further it was not possible for me to discern which theory applied, I couldn't personally recreate it consistently, and had no way of knowing if it was a Client-Side parsing error or if it was server side or if it was simply a Lag-Related issue.
Seeing it actively used shows us that it is a Bug, err feature, in how the Server is handling the data if it renders the same for all parties.
We can dive deeper and theorize that it's technically an exploit related to user input, however it appears Riot sees it no differently than animation cancelling, for now...
Ohhh great video! Thanks :D
The W TP bug/feature seems like when you hit W + Another skill + Moving (or AA move) at the same time. Since it happens when you W + another skill.
first kayle main
Do you have movement prediction on when the tp hack happens? I’ve noticed on other champions it’ll happen as well if I have it on and I’m leaving base with ms buff
no movement prediction
just to correct, Tristana, Jinx and Senna also can hit baron behind the wall
So can Kog'Maw with W active.
@light_at_night1816 but only a for a few seconds
@@kayle_1v9 8 seconds is plenty
the W TP hack might be caused by FPS, try replicating the trick with uncapped FPS
How can u cast ur R on your self without putting the mouse on it? Can u please explain?
Hold alt when you R to self cast it.
There's also a setting for selfcast that you can do. I have mine set on a mouse button
The top hack looks more like a visual bug, try if Allie can see the TP hack the same time you see
Both allies and enemies can see it the exact same way that I do
the tp hack is crazy
May the W tp be triggered by enemy cc abilities during W animation?
nope u just need to use w and right click in a very small time window
Very cool.
For the TP Kayle, at view I can say that it has to do with E animation, maybe if you try to W while E animation it will trigger, maybe while casting E or something
I do it quite often in base after recalling just using W so you don’t need e
Comment for algorithm 🗣️
The only one I knew was #4. I didn't know everything else.
Senna 5:01 can do this too
btw also jinx kog and azir
Senna left the chat
Is it just me or he didnt actually explained what the W tp hack is about?
Alguien que traduzca xd
x2
Boobies !
I nomally use TP hack but idk how to explain that 100% but yea its good for confused other players