League of Legends

League of Legends Dev Tracker




05 Nov

Comment

Originally posted by Last0

Once I couldn’t play in EU LCS anymore (after the first 2 weeks of 2016 spring split, due to visa issues caused presumably by some NA behind-the-scenes actions)

Still incredibly shitty how Reginald allegedly abused the situation to his advantage but f**ked over everyone else when Bjergsen got the right Visa, that 2016 UOL was legit looking promising at the beginning of the year.

Happy to know Diamond is in a better place now despite how rough the last couple of years were for him.

I'm still salty about it tbh

Diamondprox was a pleasure to work with and such an inspiring human

Comment

Originally posted by DanielDKXD

Here is how it looked ingame, it has been removed now.

https://twitter.com/LiLippLol/status/1454500838576214020

I don't see why this needs to go when gragas E-Flash is still in the game.

We intentionally removed that before releasing Rell because of how low counterplay it was to force the enemy to preemptively flash, similar to what you see with Gragas E. We had the benefit of the champion not being released with a precedent yet, unlike Graggy, and like you see with Cait it's a big deal when we take something away from a champ that's had it for a while. So these are just bugfixes to Rell and Galio.

Comment

Congrats!

Comment

Originally posted by SkeletonJakk

56 doesn't seem too bad for a day1

Its a bit above our comfort level. This is also the last patch of the season so we would rather not ruin the end of season climb with secret OP builds being discovered in the final week or two.

Comment

Originally posted by Reshir

55% win rate is pretty high for 1 day into patch. Nerfs make sense

Important to note that Xayah was 57% nearing 58 and Vi was nearing 56%


04 Nov

Comment

Originally posted by CertifiedCoffeeDrunk

So it was an animation bug all along?

Not exactly. All gameplay decisions like when to auto-attack are made on the server and animation is only on the client. In this case Caitlyn auto attack logic is very old and written before our modern features could support it properly - imagine in 2011 eating a bowl of mums spaghetti using only two bread knives and miraculously succeeding.

Comment

Originally posted by poggersinthechatttt

Missed opportunity to make it a maid cafe with the hottest of Zaun’s champs, like Urgot.

This could have gone along with the new Cafe Cuties skin line lol

Comment

Originally posted by Farlston

Thanks for the reply! Yeah that's brutal. So is it purely based on either obscene win rates or extremely egregious bugs? Or is it also to do with ease of fixing the issue?

We tend to hotfix for either absurd winrates or egregious bugs yeah.

There was a bug this patch that yuumi could be permanently invisible if she jumped off of an ally who was eaten by TK that had to be hotfixed for example.

Comment

Originally posted by Moomookus_

reasonable but what about camille

While I understand the Camille frustration (and personally am frustrated playing vs her) she's not the same degree of powerful right now.

She's the kind of character we would address in a normal patch (though likely not next patch since that's preseason and not a balance patch)

Comment

Originally posted by Farlston

I'd love to know Riot's logic behind when they hotfix Vs when they wait for a patch. It seems so inconsistent...

Lethality Xayah and Vi were both breaking 55% winrates (with Xayah outperforming Vi).

These characters were pretty wildly out of line and waiting another patch would've caused a lot of messed up games, especially at the end of the ranked season.

Comment

Originally posted by ChroodlesG

List the steps that occurred before the bug happened:

​1. Pick Seraphine ult on Teemo in the Ultimate Spellbook mode

  1. Flash, use Seraphine ultimate

  2. Attempt to auto attack during the Seraphine ult

Expected Result: Auto attack goes off, being able to auto attack for the rest of the game

Actual Result: Unable to auto attack for the rest of the game, even after dying, disconnecting/reconnecting from the game, and dying with guardian angel.

There were a few ults that could break Teemo's auto. All of which should be addressed with today's PBE release.

Comment

Originally posted by mattcapons

When the smite is used 5 times and the jungle item disappears the burn on monsters doesn't work anymore

This should be addressed with today's PBE release. :)

Comment

Originally posted by Jephya

Please enable First Strike!

This Keystone is one of the more game impacting Keystones due to it affecting a champions income, yet this is the only Keystone we aren't going to be able to the get a full 4 week testing cycle on...

We're working on getting First Strike enabled on PBE. Running into some unexpected roadblocks that are making it a bit tricky. >_< Will have it working as soon as we can!