@RiotRepertoir - Lux's Passive Should Not Proc Thunderlord's

NinjaGuy69·Feb 8, 2016·5 votes·634 views

Essentially, the tl;dr of this thread is the title. Lux's passive is called that for a reason: it's a passive ability. It's unreasonable that it counts as an individual spell and this is what's pushed Lux into overpowered territory; it's the reason her win rate is so high right now. It's unfair to lose a third of your health at level 1 to an E -> auto -> Illumination proc -> Thunderlord's combo.

Also, for those of you can't resist making the wise guy comment "just dodge her spells man", that's cool. But guess what? Eventually, she's gonna land a Q or an E and you're going to have a bad time. And if she lands a Q at level 6? Godspeed.

Thoughts, Repertoir?

13 Comments

Dominick DestineFeb 8, 20163 votes

Sona 's passive and Q-bonus do not count as extra hits.

It doesn't make sense that Lux does.

Aeolian MelodiesFeb 9, 20161 votes

[{quoted}](name=Dominick Destine,realm=NA,application-id=3ErqAdtq,discussion-id=kiYVxHez,comment-id=0002,timestamp=2016-02-08T20:13:48.795+0000)

's passive and Q-bonus do not count as extra hits.

It doesn't make sense that does.

Illumination is an ability. Q's empowered AA is a buff.

Dominick DestineFeb 9, 20162 votes

[{quoted}](name=Aeolian Melodies,realm=NA,application-id=3ErqAdtq,discussion-id=kiYVxHez,comment-id=00020000,timestamp=2016-02-09T01:25:02.118+0000)

Illumination is an ability.

Incorrect.

It is a debuff that is triggered by autoattacks. It is not an ability in-and-of itself.

VerxintFeb 8, 20162 votes

IMO Thunderlord needs a change to be more consistent about what can and can't proc it, and a lot of these easy procs should be removed.

I personally think autos shouldn't apply it, and the same damage source shouldn't be able to apply it twice. Make it actually the 3 spell combo, not just extra damage

Lord AzırFeb 8, 20161 votes

[{quoted}](name=Little Mac is OP,realm=NA,application-id=3ErqAdtq,discussion-id=kiYVxHez,comment-id=0000,timestamp=2016-02-08T19:31:35.763+0000)

IMO Thunderlord needs a change to be more consistent about what can and can't proc it, and a lot of these easy procs should be removed.

I personally think autos shouldn't apply it, and the same damage source shouldn't be able to apply it twice. Make it actually the 3 spell combo, not just extra damage

So what about mages with long cooldowns in the early game? Are they just forced to use deathfire touch?

VerxintFeb 8, 20161 votes

Then allow one auto to count.

I just don't think the intended mechanic was for someone to auto you twice and thow a single spell to win a trade.

NinjaGuy69Feb 8, 20161 votes

So what about mages with long cooldowns in the early game? Are they just forced to use deathfire touch?

They could still take Thunderlord's if they changed it to a stacking mechanic that required you to land 3 spells and the target of the third spell would receive the bonus damage. You can almost always find a solution to the problem if you think creatively, but at the same time, you have to realize that you won't be able to make everyone happy all of the time. Certain items and masteries are always going to synergize better with one class of champions over another.

Lord AzırFeb 9, 20161 votes

{quoted}

They could still take Thunderlord's if they changed it to a stacking mechanic that required you to land 3 spells and the target of the third spell would receive the bonus damage. You can almost always find a solution to the problem if you think creatively, but at the same time, you have to realize that you won't be able to make everyone happy all of the time. Certain items and masteries are always going to synergize better with one class of champions over another.

It was stated that they want all the other masteries to be just as strong as thunderlords. We are at the point at least where its not 9/10 players using it every game so at least thats a start. Might just be a bit more buffing to do.

NinjaGuy69Feb 8, 20161 votes

IMO Thunderlord needs a change to be more consistent about what can and can't proc it, and a lot of these easy procs should be removed.

I personally think autos shouldn't apply it, and the same damage source shouldn't be able to apply it twice. Make it actually the 3 spell combo, not just extra damage

I agree. Thunderlord's should be reworked to be more consistent with the bursty playstyle that it encourages. The balance team should remove the ability to proc it with autos and compensate it by increasing the damage it deals, reducing its cooldown or potentially a combination of the two previous options.

Zero Skill TankFeb 8, 20161 votes

Also, for those of you can't resist making the wise guy comment "just dodge her spells man", that's cool. But guess what? Eventually, she's gonna land a Q or an E and you're going to have a bad time.

Many champions can't dodge her E. She needs to miss it.

Aeolian MelodiesFeb 9, 20161 votes

Thunderlord procs after 3 AAs, abilities, or any combination of the above. Illumination is an ability of its own. So let's say Lux does you the classic E into AA poke.

E (1) Auto attack (2) Illumination (3)

So unless for some reason you want Illumination to be an AA increase instead of an ability - and you'd need a more valid argument than "but muh HP when she uses TLD", since that would remove the ability to proc it via ult.

NinjaGuy69Feb 9, 20161 votes

So unless for some reason you want Illumination to be an AA increase instead of an ability - and you'd need a more valid argument than "but muh HP when she uses TLD", since that would remove the ability to proc it via ult.

I'm well aware of how Lux's passive works. My comment was her E + auto + passive proc being unfair at level 1. Lux isn't even a good champion, but the fact that she can abuse Thunderlord's at level 1 shows you how inconsistent the spaghetti code is. Like I said earlier, if you think creatively you can solve the problem. Thunderlord's can be recoded to proc differently and Lux can keep her ult + passive proc. Riot has the tools to do this so you don't have to say "but muh ult", they just have to implement them.

Aeolian MelodiesFeb 9, 20161 votes

{quoted}

I'm well aware of how Lux's passive works. My comment was her E + auto + passive proc being unfair at level 1. Lux isn't even a good champion, but the fact that she can abuse Thunderlord's at level 1 shows you how inconsistent the spaghetti code is. Like I said earlier, if you think creatively you can solve the problem. Thunderlord's can be recoded to proc differently and Lux can keep her ult + passive proc. Riot has the tools to do this so you don't have to say "but muh ult", they just have to implement them.

There is no "inconsistent spaghetti code" in this though. It is working as intended because Illumination is an ability. There is no reason why it should not be its own damage instance for the purpose of TLD. Champions with DoT abilities such as Brand or Morgana can abuse TLD even harder, and will continue to do so until a "each spell can only count once" clause. As far as Lux is concerned, if she really wanted to use TLD, then AA-E-AA isn't exactly hard to pull off (or Q-AA-AA).