Runeglaive Nasus

CodeGwenStudios··1 votes·724 views

So I was trying out item 3716 Nasus in a custom game to see if I could do ap crits like with Gangplank , and it worked fine except with siphoning strike (Q). What I found was happening with his Q is that instead of reading all magic damage after item 3716 was completed, it would still read 2 physical damage in addition to the rest of the magic damage. The physical damage would then have the critical mark next to it, and receive no damage change while the magic damage portion would receive no change as well. I would really like to see this fixed and to see if this would change how Nasus is played. Thanks and I hope this issue gets resolved soon!

4 Comments

Reaper Soraka1 votes

Siphoning Strike stacks cannot crit. The base damage can crit, so you could see GP's numbers if you built full AD.

CodeGwenStudios1 votes

I have played tank nasus before with triforce which has some crit, and ended up critting for 1500 late game. I also tried building crit before runeglaive and that worked fine and the crit was applied to the entire Q damage.

Reaper Soraka2 votes

Well I'm not sure if this is entirely accurate, since riot doesn't keep the champion pages up to date, but;

Siphoning Strike Cost: 20 Mana Range: Self Nasus strikes his foe, dealing damage and increasing the power of his future Siphoning Strikes if he slays his target. Active: Nasus's next basic attack will deal 30/50/70/90/110 (+100% Attack Damage) (+3) physical damage. Passive: Siphoning Strike permanently gains 3 damage if it kills an enemy unit. This bonus is doubled against Champions, large minions and large monsters.

So if you have like 700 stacks, it would do like 300(Crit base attack)+1400 damage before their armor is taken into account, right? Then your E can lower their armor by like 40, which is a substantial amount against a squishy target.

CodeGwenStudios1 votes

Thanks! And that seems about right. I will have to do more testing with full crit to see if the amount of critical damage changes between Q's more than it should.

More from Report a Bug