Skip to content

Hero could not pass through energy wall with R-Kayn inside.

Neosphoros··9 votes·7,837 views

The hero could not pass through the energy wall with the R-Kayn inside, even though Kayn himself could jump over this wall. There is no information about that on wikia. Game full of bugs.

start from 24sec

https://www.youtube.com/watch?v=HJKK_-F-p1c&feature=youtu.be

Knowing that the Kayn was an enemy, then maybe the gate wouldn't let an enemy through... but in the same way... why the turrets can not shoot hero (or just only Kayn inside) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?

28 Comments

Cycera1 votes

That's a big oof for sure, however, Riot may have intended that one. Nice job spotting it though, I hope the situation is resolved somehow.

Neosphoros1 votes

{quoted}

That's a big oof for sure, however, Riot may have intended that one. Nice job spotting it though, I hope the situation is resolved somehow.

If so... information about that should not be somewhere provided?

http://leagueoflegends.wikia.com/wiki/Kayn

I have not seen something like this before.

Cycera1 votes

{quoted}

If so... information about that should not be somewhere provided?

http://leagueoflegends.wikia.com/wiki/Kayn

I have not seen something like this before.

I've never seen something like this before either, but knowing that the Kayn was an enemy, then it makes sense that the gate wouldn't let an enemy through. Whether that is intentional or not, I hope Riot responds and fixes or justifies this "bug"

Neosphoros1 votes

{quoted}

I've never seen something like this before either, but knowing that the Kayn was an enemy, then it makes sense that the gate wouldn't let an enemy through. Whether that is intentional or not, I hope Riot responds and fixes or justifies this "bug"

But in the same way... why the turrets can not shoot hero (or Kayn inside - if you like) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?

Kai Guy1 votes

Your English is a bit unclear here. I am makeing the assumption because your talking about ability's and tower aggro and not doing damage to folks during Kayns R that you have questions on how his R functions.

http://leagueoflegends.wikia.com/wiki/Untargetability

Kayne R makes him untargetable for 2.5 seconds. Above is the link to the relevant page on league wiki.

The dash when his R is mobility. Its very small range. However there are some walls you can dash over when using it.

Let me know if you have any further questions about game mechanics and I will happily provide you with relevant information.

Cycera1 votes

{quoted}

But in the same way... why the turrets can not shoot hero (or Kayn inside - if you like) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?

You do bring up a lot of valuable questions about Kayn's ult. I now kinda wish Riot issued more details on the parameters of this. I guess when Kayn was released, we failed to see walking through walls wasn't the only brand new, and possibly buggy, concept introduced to the game.

Kai Guy2 votes

Its not to special. 1. he becomes untargetable. 2. he dashes to a point and click enemy. 3. he deals damage and dashes in a chosen direction. This is all stuff we have seen before. Kalista TahmKench got a bunch of data on testing long duration untargetablility. And like Vladimir has been around for ages. Dudes like an OG data point for the mechanic. Troll pool is the reason we call Fizz troll pole.

check out http://leagueoflegends.wikia.com/wiki/Untargetability for more information if you are curious.

Wall walking is not entirely that new of a concept. A massive # of abilitys ignore terrain. Kaynes is that but more flexiable.

Neosphoros2 votes

{quoted}

You do bring up a lot of valuable questions about Kayn's ult. I now kinda wish Riot issued more details on the parameters of this. I guess when Kayn was released, we failed to see walking through walls wasn't the only brand new, and possibly buggy, concept introduced to the game.

I have nothing against Kayn and his skills but regarding to my problem and "no-problem" from Kais Guy movie it is possible to say that it maight be some kind of bug. Bug for some of us and "no-bug" for others - which is weird.

Kai Guy2 votes

So Cycera I tried but couldn't recreate the bug. https://www.youtube.com/watch?v=hvpIMScyR18&feature=youtu.be It looks like the solutions just using a right click outside of the wall.

Cycera1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=00000001,timestamp=2019-01-06T23:41:33.323+0000)

So Cycera I tried but couldn't recreate the bug. https://www.youtube.com/watch?v=hvpIMScyR18&feature=youtu.be It looks like the solutions just using a right click outside of the wall.

That's very strange. That makes me wonder if it is somehow related to the skins or to item passives or something. That's very, very strange.

Kai Guy2 votes

Skins don't change gameplay code. Hitboxes, base stats, scaling, etc. Just changes animations. That'swhy its a skin.

Very strange to me is that Mao is clearly inside the terrain. He has walked farther up on the map the would be allowed for any enemy players. I think its strange he would interact randomly with a few pixles of terrain when they should all be coded the same. enemy champions cant move into the wall that far, its odd.

And stutter stepping which mao does a few times. I find that Also kind weird. Like, you typically only see a stutter when you end a movement command or you use a stop command. Attack commands and CC can be ignored because mao did not suffer those after walking partially thru the terrain. Also, Rapid clicks or Drag click don't interrupt the movement commands. Its choppy but they champion wont stutter.

Well, what I tested it for when Kanye R cast after I Was inside of wall and also for if kayn R cast when I was outside of wall and later walked into terrain. 0 issues. movement was smooth and clean. As I show in the vid I had no issues.

Now, items might honestly make for a bug or problem. I can always be wrong in my understanding. So,I will try to check tommrow if the item 3147 or a item 2055 triggering a ward will somehow change the terrain interactions and if going Rhast will change it. Skins can be discounted, they really don't truly affect anything other then animations.

Apart from the few times riot trolled everybody and added crap like champions wearing sunglasses take -1 damage from Leona passive. if I can steal a some ones time I will test Rhast and items item 3364 item 3147 tomorrow.

Also do note there may just be translation issues in the op's post. To my understanding the op is not a native English speaker and machine translates things to his native language. However I May be wrong on that as well.

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=0000000100000000,timestamp=2019-01-07T10:39:10.992+0000)

Very strange to me is that Mao is clearly inside the terrain. He has walked farther up on the map the would be allowed for any enemy players. I think its strange he would interact randomly with a few pixles of terrain when they should all be coded the same. enemy champions cant move into the wall that far, its odd.

There is nothing to do with pixels. All of skins are based on the same specific valuses templates. Pixels are not programed singly.

In the same way I will ask... is it a chance that - it was a cheat?

Kai Guy2 votes

OK Cycera. I had the time to do some more testing.

https://www.youtube.com/watch?v=XvMKtzvAb7Q. This shows the walls collision for Mao. As you can see, he cant walk into it as far as the OP did. I screen cap it so that my movement commands are very clearly showen.

Next. https://www.youtube.com/watch?v=mdIJJn-OCaM Tested if Rhast or the Items had any effect.

Not able to notice a difference in the slightest. I also show how Stutter steeping, you can see the animations get choppy when you input stop commands rapidly.

My conclusion.

If its a proper bug it seems pretty rare. I tried a few times and failed to recreate the issue. I tested oracles, tested dusk blade, tested Rhast and tested base kayne. I also tested starting inside the terrain on R cast as well as starting outside terrain on the R cast. Nothing affected my ability to walk thru base wall. Much less interrupt movement animations with out usage of Stop commands. Constant movement commands cause re-pathing, they don't break animation.

My opinion here. Its likely the OP is just having language barrier issues. He uses Machine translation and that can really make it hard to communicate. Its also possible he just exaggerated or lied in his post. I am trying to treat him in good faith, so lets roll with language barrier.

Worth a note. There is also the fact he is confused how Kayne does not get stunned during his R by a veigar W. That's completely unrelated to the shown clip. That comment shows a weak understanding of in game mechanics. First. Because Veigars stun is on his E not W. Second it doesn't show a good understanding of how Untargitability works. Hence I linked him to http://leagueoflegends.wikia.com/wiki/Untargetability to learn about the mechanic and its functionality.

Let me know if you have any questions or issues with how I went about testing for this.

@Neo. If you need help with language problems. let me know your native language and I can try to find the relevant wiki pages in your language.

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=0000000100000001,timestamp=2019-01-09T00:16:00.488+0000)

OK Cycera. I had the time to do some more testing.

https://www.youtube.com/watch?v=XvMKtzvAb7Q. This shows the walls collision for Mao. As you can see, he cant walk into it as far as the OP did. I screen cap it so that my movement commands are very clearly showen.

Next. https://www.youtube.com/watch?v=mdIJJn-OCaM Tested if Rhast or the Items had any effect.

Not able to notice a difference in the slightest. I also show how Stutter steeping, you can see the animations get choppy when you input stop commands rapidly.

My conclusion.

If its a proper bug it seems pretty rare. I tried a few times and failed to recreate the issue. I tested oracles, tested dusk blade, tested Rhast and tested base kayne. I also tested starting inside the terrain on R cast as well as starting outside terrain on the R cast. Nothing affected my ability to walk thru base wall. Much less interrupt movement animations with out usage of Stop commands. Constant movement commands cause re-pathing, they don't break animation.

My opinion here. Its likely the OP is just having language barrier issues. He uses Machine translation and that can really make it hard to communicate. Its also possible he just exaggerated or lied in his post. I am trying to treat him in good faith, so lets roll with language barrier.

Worth a note. There is also the fact he is confused how Kayne does not get stunned during his R by a veigar W. That's completely unrelated to the shown clip. That comment shows a weak understanding of in game mechanics. First. Because Veigars stun is on his E not W. Second it doesn't show a good understanding of how Untargitability works. Hence I linked him to http://leagueoflegends.wikia.com/wiki/Untargetability to learn about the mechanic and its functionality.

Let me know if you have any questions or issues with how I went about testing for this.

@Neo. If you need help with language problems. let me know your native language and I can try to find the relevant wiki pages in your language.

Excuse me... what to do with this problem have my language or translator that I'm using? It is clearly visible that mao can not pass energy wall. Are you trolling/provoking me again to continue stupid conversation about problem that is not exist to distract attention from the main problem? It is boring mate.

Kai Guy1 votes

Machine translation creates broken English. It can convey a different meaning then your intent. Its worth mentioning to folks to set an expectation that there may be difficulties with a language barrier.

There's been gate bugs. Lots of them. You had teleporting champions, folks getting stuck on teammates because of awful pathing. Traps like Teemo R could not be placed inside of them, Sion ulti was stopped by his teams gate. It would also displace folks really badly. That all has been worked on. So a lot of the old bugs are fixed. That being said thats not proof that non still exist.

Far as my testing, still inconclusive. I am thinking it is likely more related to the knockup then the rhasst R. Standard R casts don't seem to make any issue. Inside the terrain or outside on cast don't cause a problem. The duskblade and also Oracles did not make an issue as well. Being in Rhasst or Kayne did not recreate the bug.

why the turrets can not shoot hero (or just only Kayn inside) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?

http://leagueoflegends.wikia.com/wiki/Untargetability answers this for you.

Again, the reason I bring up language barrier is that on the English http://leagueoflegends.wikia.com/wiki/Kayn Under the section of kaynes R it list untargitability as one of the effects that happens. If you hover over the link it opens a list of how the mechanic functions.

You claimed this information was non existent when It does exist.

If so... information about that should not be somewhere provided? http://leagueoflegends.wikia.com/wiki/Kayn I have not seen something like this before.

I can show that Its clearly there and I did. I Took additional steps to let Cycera know its most likely because of a language issue. I did that as a sign of good faith given the bad blood between you and I.

So although Its possibly your lying. Personally i feel Its more likely your translation program creates difficulty when your using lolwiki becuase this is not the first time I have seen you struggle to find relevant information using the English Lolwiki pages.

Far as bug goes, further testing would be required just to recreate it. So far I have not been able to do it. Seems like a niche bug or related to Displacement. It may possibly still be displacement in combination with R. Thou I find that unlikely. Kaynes Dashes on the start and End of his R makes him immune to terrain.

Now slowed down, it kind of looks like you input stop commands and are just trying to wait out the kayne R. You said its a bug and prevents movement so I am taking that in good faith. So far, the R cast alone very much does not seem to cause the issue you experienced.

I am taking steps and trying to be fair to you, yes?

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=000000010000000100000000,timestamp=2019-01-09T21:43:43.212+0000)

Machine translation creates broken English. It can convey a different meaning then your intent. Its worth mentioning to folks to set an expectation that there may be difficulties with a language barrier.

There's been gate bugs. Lots of them. You had teleporting champions, folks getting stuck on teammates because of awful pathing. Traps like Teemo R could not be placed inside of them, Sion ulti was stopped by his teams gate. It would also displace folks really badly. That all has been worked on. So a lot of the old bugs are fixed. That being said thats not proof that non still exist.

Far as my testing, still inconclusive. I am thinking it is likely more related to the knockup then the rhasst R. Standard R casts don't seem to make any issue. Inside the terrain or outside on cast don't cause a problem. The duskblade and also Oracles did not make an issue as well. Being in Rhasst or Kayne did not recreate the bug.

http://leagueoflegends.wikia.com/wiki/Untargetability answers this for you.

Again, the reason I bring up language barrier is that on the English http://leagueoflegends.wikia.com/wiki/Kayn Under the section of kaynes R it list untargitability as one of the effects that happens. If you hover over the link it opens a list of how the mechanic functions.

You claimed this information was non existent when It does exist. http://leagueoflegends.wikia.com/wiki/Kayn I have not seen something like this before.

I can show that Its clearly there and I did. I Took additional steps to let Cycera know its most likely because of a language issue. I did that as a sign of good faith given the bad blood between you and I.

So although Its possibly your lying. Personally i feel Its more likely your translation program creates difficulty when your using lolwiki becuase this is not the first time I have seen you struggle to find relevant information using the English Lolwiki pages.

Far as bug goes, further testing would be required just to recreate it. So far I have not been able to do it. Seems like a niche bug or related to Displacement. It may possibly still be displacement in combination with R. Thou I find that unlikely. Kaynes Dashes on the start and End of his R makes him immune to terrain.

Now slowed down, it kind of looks like you input stop commands and are just trying to wait out the kayne R. You said its a bug and prevents movement so I am taking that in good faith. So far, the R cast alone very much does not seem to cause the issue you experienced.

I am taking steps and trying to be fair to you, yes?

I see that you always argue, always you are not agree, even you have understand this topic you are able to say that "you do not understand". Mate, WTF is wrong with you?

Kai Guy1 votes

"why the turrets can not shoot hero (or just only Kayn inside) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?"

^ this is a good example of broken English from a translation program.

As far as I can tel whatl you are trying to ask would be: 1)Why is kayne not targeted by towers when he is ulting a champion? 2)Why do skills not hit Kanye when he is inside a champion, why does this not have a counter? 3)Why does Kanye not get stunned by Veigar E when he is inside a champion?

The answer to all of the above is that his ulti makes him untargitable. So the mechanic you need to learn and understand is untargitibility. It may be this is not what your asking, but that's what it looks like. If your meaning is lost to translation then that's the very language barrier I am talking about with Cycera.

I don't know your getting upset at me here. Your asking questions, that implies you don't understand something. Im giving you the correct answer and providing a source for you to use to learn so that your not just takeing my word for it.

Whats the issue? I really don't understand why you keep getting so mad at me for explaining things. Here is the relevant mechanic, here is the lolwiki page explaining it http://leagueoflegends.wikia.com/wiki/Untargetability.

Does this fail to answer your questions in your opening post? Am I missing something? Is something being lost in translation?

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=00000001000000010000000000000000,timestamp=2019-01-09T22:12:34.137+0000)

"why the turrets can not shoot hero (or just only Kayn inside) with Kayn inside or why any (in general) of teammates skills can not counter/not working on Kayn-R when he is inside of one of enemy champions. Why ex Veigars W not "stuning" (enemy) Kayn when he is passing through his cage inside other champ?"

^ this is a good example of broken English from a translation program.

As far as I can tel whatl you are trying to ask would be: 1)Why is kayne not targeted by towers when he is ulting a champion? 2)Why do skills not hit Kanye when he is inside a champion, why does this not have a counter? 3)Why does Kanye not get stunned by Veigar E when he is inside a champion?

The answer to all of the above is that his ulti makes him untargitable. So the mechanic you need to learn and understand is untargitibility. It may be this is not what your asking, but that's what it looks like. If your meaning is lost to translation then that's the very language barrier I am talking about with Cycera.

I don't know your getting upset at me here. Your asking questions, that implies you don't understand something. Im giving you the correct answer and providing a source for you to use to learn so that your not just takeing my word for it.

Whats the issue? I really don't understand why you keep getting so mad at me for explaining things. Here is the relevant mechanic, here is the lolwiki page explaining it http://leagueoflegends.wikia.com/wiki/Untargetability.

Does this fail to answer your questions in your opening post? Am I missing something? Is something being lost in translation?

Facepalm. That was a rhetorical question. RIOT as the creator of the game universe could freely give rules to these events. Nevertheless, I meant that R Kayn would not be described properly if it worked just like in the film I shared. Nevertheless, as you have proved, this description was unnecessary because you proved yourself that there was an bug in the game. Please, do not answer my threads anymore, you always "spliting hairs". Yours answers are not helping.

Kai Guy1 votes

Nevertheless, as you have proved, this description was unnecessary because you proved yourself that there was an bug in the game

No. My testing is very much still inconclusive. That's why I said "Far as my testing, still inconclusive" All I have found is that this bug if it exists does not trigger off Kayne R alone. I am very clear about this in my post. I very clearly show this in my video. I would appreciate it if you don't put words in my mouth. I very clearly show an inability to recreate the bug in the game in my videos.

was a rhetorical question. RIOT as the creator of the game universe could freely give rules to these events. Nevertheless, I meant that R Kayn would not be described properly if it worked just like in the film I share

I don't quite understand what your trying to say here. "RIOT as the creator of the game universe could freely give rules to these events." I assume that's the tower, veigar,counterskill? Yes. They have rules to these events. Its what I linked you to. Untargitibility. Same mechanic is relevent to answering your question and Its consistent in its patterns of behavior. Also a bug would never be described properly? Its a bug, so its unintended.

I am not shure why your accusing me of splitting hairs. You asked multiple questions. Your questions had 0 relation to the clip. I have no context to treat it as anything other then you don't know why Kayn R functions the way it does. Look, I can break it down for why I think your questions are not related to your clip. Veigar is on kaynes team. Kayne will not be stunned by his teammates ability. This is related to basic mechanics. Your not near a tower. Asking why towers wont target kayne is unrelated to your clip. This is also related to basic mechanics. Discussing why you cant counter kayne during R with an ability, again unrelated to the clip. How untargitibility works, is once again part of basic mechanics.

Its not very good rhetoric on your part. Don't ask questions that make you sound oblivious to game mechanics, please. IM trying to give you an out here, Language barrier. Stop digging yourself deeper.

Look, if you have questions about the game then odds are I have the answer and provide the source. I cant make you believe me, and that's fine.

If you don't ask questions in your threads. The odds of me ever posting massively decrease. Instead, in your post just make a statement. Say this is how you think the game works and functions. Don't make it sound like you need help or are curious about mechanics.

Because its pretty frustrating to see a question on a mechanic. Answer it, provide source. Then get told What ever its rhetorical you already think you know why.

I really don't mind taking the time to help.

But hey that's fine if you don't want it. Please don't reply, don't invite me back into a conversation. Don't force me to correct you for saying something like "Nevertheless, as you have proved, this description was unnecessary because you proved yourself that there was an bug in the game"

No I did not. This is untrue, provably untrue. Please understand, I dislike people twisting my words and I feel obligated to respond if they do.

Don't want me around to help? That's fine. Don't ask questions about basic mechanics. Don't reply to me.

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=0000000100000001000000000000000000000000,timestamp=2019-01-09T23:32:07.945+0000)

No. My testing is very much still inconclusive. That's why I said "Far as my testing, still inconclusive" All I have found is that this bug if it exists does not trigger off Kayne R alone. I am very clear about this in my post. I very clearly show this in my video. I would appreciate it if you don't put words in my mouth. I very clearly show an inability to recreate the bug in the game in my videos.

I don't quite understand what your trying to say here. "RIOT as the creator of the game universe could freely give rules to these events." I assume that's the tower, veigar,counterskill? Yes. They have rules to these events. Its what I linked you to. Untargitibility. Same mechanic is relevent to answering your question and Its consistent in its patterns of behavior. Also a bug would never be described properly? Its a bug, so its unintended.

I am not shure why your accusing me of splitting hairs. You asked multiple questions. Your questions had 0 relation to the clip. I have no context to treat it as anything other then you don't know why Kayn R functions the way it does. Look, I can break it down for why I think your questions are not related to your clip. Veigar is on kaynes team. Kayne will not be stunned by his teammates ability. This is related to basic mechanics. Your not near a tower. Asking why towers wont target kayne is unrelated to your clip. This is also related to basic mechanics. Discussing why you cant counter kayne during R with an ability, again unrelated to the clip. How untargitibility works, is once again part of basic mechanics.

Its not very good rhetoric on your part. Don't ask questions that make you sound oblivious to game mechanics, please. IM trying to give you an out here, Language barrier. Stop digging yourself deeper.

Look, if you have questions about the game then odds are I have the answer and provide the source. I cant make you believe me, and that's fine.

If you don't ask questions in your threads. The odds of me ever posting massively decrease. Instead, in your post just make a statement. Say this is how you think the game works and functions. Don't make it sound like you need help or are curious about mechanics.

Because its pretty frustrating to see a question on a mechanic. Answer it, provide source. Then get told What ever its rhetorical you already think you know why.

I really don't mind taking the time to help.

But hey that's fine if you don't want it. Please don't reply, don't invite me back into a conversation. Don't force me to correct you for saying something like "Nevertheless, as you have proved, this description was unnecessary because you proved yourself that there was an bug in the game"

No I did not. This is untrue, provably untrue. Please understand, I dislike people twisting my words and I feel obligated to respond if they do.

Don't want me around to help? That's fine. Don't ask questions about basic mechanics. Don't reply to me.

No, for the 2nd time I do not want you here. You feeling plesure by argueing with me... so discuson with you is like scrubbing with concrete. ABRA KADABRA ! Go away you bad spirit !

Kai Guy1 votes

I tested this a few times in custom game.

As far as I can tell, any movement commands outside of the wall fixes this "bug."

https://www.youtube.com/watch?v=hvpIMScyR18&feature=youtu.be

The footage is from my POV to show movement commands clearly.

Neosphoros1 votes

[{quoted}](name=Kai Guy,realm=NA,application-id=LqLKtMpN,discussion-id=83AALGE9,comment-id=0001,timestamp=2019-01-06T23:49:46.165+0000)

I tested this a few times in custom game.

As far as I can tell, any movement commands outside of the wall fixes this "bug."

https://www.youtube.com/watch?v=hvpIMScyR18&feature=youtu.be

The footage is from my POV to show movement commands clearly.

So whats the conclusion? Bugs may occur individually and may not be fixable? In this case any bug may happened for every each of us in any (different) moment but for others may not happened at all but becouse of that it may afect on final match result.

This game is unfinishable... still and to rest of LOL days - ALPHA version.

LOL is like a coal mine (even better - LOL is not that "dirty")... it is possible to dig over and over (try to fix) but it is so many coal (bugs) that its not possible to extract everything (fix all errors) - for programists - "golden job"

AidanWR1 votes

This may have just been a one in a million cases interaction where the Kayn happened to ult at an exact time that created this

Neosphoros1 votes

Fact is that in game there is a lot of bugs that may effect on our match result. It is not a problem if they would happened in normal mode, becouse we are playing for fun but if those bugs would happened in ranked games it changing whole case... is the system will give us back time and points that we will lose becouse those bugs?

Neosphoros1 votes

System may penalitize us becouse our behaviour to other players, becouse we are angry. What if we are angry sometimes becouse those bugs? Maybe we should have possibility to report - system?

Neosphoros1 votes

There is something about this energy wall...

This time I could not pass through this wall with cho

https://www.youtube.com/watch?v=NNLKxUTS6DY&feature=youtu.be

Neosphoros1 votes

We could not move in any way till the champions were unblocked automaticly after few seconds.

More from Report a Bug

More by Neosphoros