RiotRayYonggi

JK our QA testers found it; multiple E’s in quick succession don’t give extra stacks. We will get the bug noted thanks for the report.

I checked this and don’t see anything wrong. Can you clarify?

(Note, we actually won't be doing the champion secondary resource QoL this patch, gonna let it cook a bit more internally):

As of right now, all of these changes are player-only. So in the Xin Zhao case, enemies would not see you charge up to your knockup via this UI. It's meant to help the player, not the opponents.

Definitely something we could/should add. I’ll make a note

To be fair, winrate has to come from somewhere. Not every champion can be >50%. If unpopular/niche champions are >50, and popular champions are 50, who's below 50%? In addition, the total pick-rate of all <50% champions needs to equal the >50% champions. As such, super popular picks being <50% affords the most other champions to be strong/viable.

There is still work left to be done. We have follow-up work slated across most classes for this patch (the one you're reading) and subsequent patches. It just doesn't make sense to try to swing for every class at the same time.

Also, not every class needs itemization changes to fix their issues either. Different classes and systems require different levers and tactics. We patch biweekly and have a lot of content, so give us some time to work through it diligently.

Its important to consider inter-lane play. Sure kayn might not be late-game skewed by all champion standards, but by jungle standards he is. As such, he will drive the win-rate for late-game up relative to the junglers he's against.

To clarify, we could not observe any meaningful difference and we were on 0 ping testing internally.

Not to say we wouldn't do this in the future, but this has been explored by us internally (I personally did an exploration on this around 4 years ago). The conclusion we came to was that even with my team (of diamond+ players) could not observe any meaningful difference in how quickly the game updated. In the VAST majority of cases, players are being limited by their ping and not the server's tickrate. Getting a marginal performance improvement of this type would also bring a number of risks:

• Servers have to work (around) twice as hard, self explanatory.
• We have to make sure nothing bugs out due to this. Solve-able, but costly regardless and may have long-term butterfly effects of bugs and how your champions feel.
• Lower tickrate means more time for the server to resolve "conflicts" and run calculations. This means its less likely to run into bugs/miscalculations with things like stats, and gives the server time to optimize the packets/information it ...

Allow me to clarify:

When she uses passive on champions, she exorcises a spirit from them, which follows her and heals her for a short duration.
The more spirits, the more healing and movement speed she gains.

Please note the Corki midscope is still in active development and you’ll see changes hit PBE frequently. We are still working to ensure he’s a viable bot laner with a niche in the roster, while using the new item adjustments similar to other caster marksmen.

It's similar tuning to Coup De Grace but applies at full HP. This means that it's more likely to trigger in a variety of places, whether that is lane poke, burst from high HP (AOE Mages, Karthus, GP), and siege poke (Xerath, Zoe). If we don't consider Coup De Grace weak, then this likely shouldn't be either.

That's my analysis at least, but we have time to tune it if this ends up untrue.

We intend to address stalling as well with this version.

I’ll make a note for next week to see how difficult it is to just let him ult without condition with Samira R, and whether that’s something we’d want.

We typically just allow Sylas to be OP with new spells and don’t stop designing because of him. It would be really lame for 1 designer to ship a champ that restricts every designer after them.

As for the Samira Sylas thing, my understanding is that Sylas does not get Samira passive, which prevents him from casting R. This is definitely not ideal from the player perspective, but would require us to either move passive logic into R (which means Viego can’t stack it) or special case Sylas, which may be more cost than value.

This was all a bit before I started learning to read/write champion code myself, but my understanding of the cause was:

Most champions had spells/passives/etc that only had to check for “themselves” to trigger logic. So when it was Viego running their logic instead, it would not know what to do.

So in Zyras case, it would spawn a plant, then check “Zyras” passive cooldown before sending another one. Because there was no “Zyra” passive to check, it would just fire off another plant, and repeat until Viego left her body or until some other bug stopped it.

As for the final question, Viego/Sylas/Renata etc all caused us to have new “standards” for how to properly script to not run into the common bugs with them. So new champs should follow these standards and just work, but regardless, our QA teams would test to make sure it works anyway.

You are correct in that Viego and Sylas were both nightmares. Once we “locked” the general mechanics of the ult/kit stealing, we had to play test with the (very slowly growing) list of champions that wouldn’t break the game when interacting. This meant a LOT of playing simple stuff like Jinx until we slowly bug fixed every single interaction.

Did mean some funny moments when a champ labeled “functional but probably bugged somehow” in our champion tracker was played and would break the game somehow. For example, Viego possessing Zyra spawned about 6 thousand plants all around the map in around 5 seconds due to a bug with her passive.

Seeing how that development went, it’s a miracle we untangled all the spaghetti to where they function reasonably as expected on live now.

Finally some good f*cking discussion

Thanks I'll pass this along today

Never ever