Nasus needs some tweaks...
As someone who thoroughly hates how a champion can be tanky, yet can smash your skull in with one click of a button, I've found a way to make Nasus have to take more risks for high rewards.
In no way should he be able to walk up to the Nexus, tank an entire team of five, and die, just to respawn and teleport back in to do it again.
Since the circlejerk group who always complains that Nasus is not just his Q and W, or that Jinx's win rate (54%) is clearly an indication that she is balanced, will probably downvote me, I want to at least get my point across.
A mega tank who uses two spells to win the game, and gets to keep his infinite number of stacks is just not fair.
You can shut him down in lane, but it will not matter if he leaves his team to free farm in the mid-late game, and will still gain those stacks back to beat your face in.
SO HERES AN EASY WAY TO FIX THAT. THIS WILL GIVE THE ENEMY TEAM WAYS TO BEAT NASUS WITHOUT HAVING TO WAIT FOR HIM TO SPLIT TOP, THEN FIVE-MAN GANGUP ON HIM JUST TO BRING HIM DOWN.
**ACTIVE: Nasus empowers his next basic attack within the next 10 seconds to deal bonus physical damage. BONUS DAMAGE: 30 / 50 / 70 / 90 / 110 (+total stacks of Siphoning Strike) If the ability deals a killing blow, Nasus gains 3 stacks of Siphoning Strike (doubled for killing champions, large minions and large monsters). If Nasus has accumulated over 200 stacks, on death he will lose 50 of them, but he cannot fall below 200 stacks. **
Why would this change be good?
Because now you wouldn't have to camp Nasus early game so much, and build your whole team around stunning him, and wasting resources on him because in the mid game if your team shuts him down, he won't be the hyper carry he shouldn't be.
It wouldn't be worth camping top while your bot lane gets smashed. Its a win-win situation where Nasus could get a lot of early game stacks, but your team can shut him down in the later game.
tl:dr, Nasus is too strong and needs a bit of a knockdown. If we want to achieve this, read the bold, italicized statement above to fix it.
