League of Legends Dev Tracker

;)

Having watched one of his pro-view games, I think it's double-bound to his right-click. He seems to do it so that timers stay up on screen.

Does this account for the fact that every double hit stacks kraken slayer twice?

Yeah well the ruined king game and the Yordle getting moved kind of killed the momentum a bit. Both were originally meant to come out in-between Season Start and this event and be beats in the campaign. COVID kind of messed that up a little but it’s all good

She won’t be released, no. But she will be a part of the event ;)

It’s a traditional mage rather then burst. She will be out later this year but expect to see her cast a heavy shadow over this event

I’m pretty sure it’s out later this week

And so it begins..

Appreciate you for doing your part in fighting against misinformation, this is really well done. I know I get very frustrated often playing against this champ but so many of the things listed in this post are either just poorly backed opinions or just straight up wrong. Your post has some good analysis and as you pointed out next patch, we want to bring him more into jungle and out of lane by doing some changes that nerf his laning and buff his jungling. None of these are explicitly targeting frustration but I think his jungling pattern is far less frustrating than his laning pattern, so I think this might help a decent amount. It makes sense to wait where these changes land before we make any more decisions.

Jumping on top comment for visibility. :)

It's not hitbox related. Cait's hitbox doesn't move during her ult. The issue is vision related.

The platform tower's vision range is 1200 and it only attacks units directly in its vision. But its attack range appears to be 1250. Caitlyn R explicitly gives vision to all units on the enemy team during her R ("link vision", it's very different from regular perception bubbles).

By providing vision via her R, she's effectively letting the laser tower have that last 50 units of range if she's standing exactly in that in-between zone.

It's not that complicated. Lifesteal is represented internally as a decimal - 8% lifesteal is .08, so naturally if you miss a decimal place or typo and put in .80 instead you end up with 80% lifesteal instead of the intended 8%. I've worked as a professional software dev before (though it's not what I do at Riot) and I can tell you that this type of error is quite common, particularly when trying to do fast iteration and push things into a testable environment (which is exactly what happened here).

In League, most of this stuff doesn't get seen by a wide audience though as it never goes to PBE and is fixed before it leaves internal environments. This is one small case where the list was shipped to PBE immediately and so was seen (and was certainly disruptive to PBE games). A parallel here to non-game dev is that you wouldn't see this type of error in other software like web pages, mobile apps, etc., because they don't have publicly-facing non-prod environments of any kind ...

Thank you! I've been working it and will keep doing so. Learning to host is hard haha

That's a good vote!

It was actually that play that inspired the idea of this series too =)

Oh man do you have a clip of this? That sounds AMAZING lol

There's two main problems with Bjerg.

1. He's very busy!
2. He's in a LOT of hype LCS moments lol. Putting him here where the story felt MORE about Turtle's moment made sense to me at least, but Bjerg has SO many big games both wins and losses that we'd love to have him in and even he ever did want to make time, we'd want to pick our episode very carefully because I doubt we'll get many.

Nor do I.

I wish this wasn't so true. But it is.