Tedo58 (EUNE)
: Aftershock is having 45 sec cd and is not that broken.
> [{quoted}](name=Tedo58,realm=EUNE,application-id=3ErqAdtq,discussion-id=cVqIE3dU,comment-id=0001,timestamp=2018-12-31T07:11:52.957+0000) > > Aftershock is having 45 sec cd and is not that broken. 35 seconds, but im sure you know what your talking about, Comes off cooldown just in time for it to save you from eletrocute
Sioox (EUW)
: imagine a champion counter your entire champion. Playing as Veigar against Fizz is like fighting for survival. {{sticker:slayer-jinx-wink}}
> [{quoted}](name=Sioox,realm=EUW,application-id=3ErqAdtq,discussion-id=cVqIE3dU,comment-id=0000,timestamp=2018-12-31T07:03:04.968+0000) > > imagine a champion counter your entire champion. Playing as Veigar against Fizz is like fighting for survival. > {{sticker:slayer-jinx-wink}} imagine keeping your comment relevant to the conversation which is regarding a rune path as op, not a champions kit.
Rioter Comments
: 1. May I suggest the Bug Report board for this? You'll get better traction there. 2. Flaming Riot won't help it get fixed. 3. This issue, as far as I'm aware, is a *rare* bug that only happens while dead. On revive the issue is fixed. 4. Yes, it's a game that's been out almost a decade now. But here's the thing: The game is always changing. League isn't the same code as a decade ago, nor is it even the same code as a month ago. It's not like Riot's abandoned the game and is never going to fix any imbalances or bugs. It *will* eventually be fixed. 5. The issue can be worked around by either clicking on desktop, then back in game, or having camera force update (via teleporting or reviving). And, again, it's only in effect while dead (Unless this is an issue of your computer not actually being focused on the game, and rather on a different program).
> [{quoted}](name=DuskDaUmbreon,realm=NA,application-id=yrc23zHg,discussion-id=Ra1wnzGO,comment-id=0000,timestamp=2018-07-28T21:40:41.644+0000) > > 1. May I suggest the Bug Report board for this? You'll get better traction there. > 2. Flaming Riot won't help it get fixed. > 3. This issue, as far as I'm aware, is a *rare* bug that only happens while dead. On revive the issue is fixed. > 4. Yes, it's a game that's been out almost a decade now. But here's the thing: The game is always changing. League isn't the same code as a decade ago, nor is it even the same code as a month ago. It's not like Riot's abandoned the game and is never going to fix any imbalances or bugs. It *will* eventually be fixed. > 5. The issue can be worked around by either clicking on desktop, then back in game, or having camera force update (via teleporting or reviving). And, again, it's only in effect while dead (Unless this is an issue of your computer not actually being focused on the game, and rather on a different program). Not a hard fix at all, you dont need to kiss up to riot. I reserve the right to flame them for having scuffed coding.
Rioter Comments
Rioter Comments
Rioter Comments
: Death of a Marksman? -- "Marksmen are feeling the brunt of "adapt or die" that every other lane has always faced over the years. It's just happening all at once now."
Rioter Comments
Rioter Comments
Rioter Comments

liberalwhiteman

Level 131 (NA)
Lifetime Upvotes
Create a Discussion