I see a lot of rageblade/gunblade builds still. Yes, Jax is very much still viable when played by the right person. You can't go in all gung-ho like an idiot and hope for dodge anymore, but you have a greater control over the dodge aspect since the rework. I find him much more enjoyable now because I never got those amazing 20-dodge in a row procs before the rework anyway. ^_^ Go eat babies with Jax!
Actually, I think he's borderline OP.
In top lane, he's difficult to gank, and once he reaches 6 his damage becomes nearly impossible to deal with (I do about 300-400 burst damage after resists every 5 or 6 seconds).
His only problem is getting his stacks up in teamfights, so the usual heavy CC and/or heavy burst puts him down hard, but he still gets tanky as hell with Atmogs + ult.
In top lane, he's difficult to gank, and once he reaches 6 his damage becomes nearly impossible to deal with (I do about 300-400 burst damage after resists every 5 or 6 seconds).
His only problem is getting his stacks up in teamfights, so the usual heavy CC and/or heavy burst puts him down hard, but he still gets tanky as hell with Atmogs + ult.
Well Jax has 2 faces that are ****ing annoying:
• Solo top Jax:
He is easy to counter in lane but with his combo W+E will steal your life in little parts, when he reaches level 6 it's a really hard 1v1 and it's really hard gank a skilled Jax's player.
• Jungle Jax:
He can get counter in the jungle by champions with a high counterjunling skill like Nunu & Willump, Udyr or Shyvana, but his Stun can jump in can result in a waste of your Flash or a kill so he's pretty OP in this case.
• Solo top Jax:
He is easy to counter in lane but with his combo W+E will steal your life in little parts, when he reaches level 6 it's a really hard 1v1 and it's really hard gank a skilled Jax's player.
• Jungle Jax:
He can get counter in the jungle by champions with a high counterjunling skill like Nunu & Willump, Udyr or Shyvana, but his Stun can jump in can result in a waste of your Flash or a kill so he's pretty OP in this case.
You need to log in before commenting.
<Member>