Return of Reckoning

are you actually kidding me? and SH mobility is fine right? whos gonna catch them now? moronic.

no pounce cooldown was ridiculous..

Clearly people are, and have been, upset by pounce since the game was made. The ability to catch or engage a target from so far away and have no cool down is just game breaking cheese. Watching a SH pounce away from a WL pouncing after him looks like a looney toons cartoon. Pounce should be removed from both sides. Pounce + a knockback is even more ridiculous. Objectives in scenarios look like a trampoline there are so many knock backs these days.

never mind

Bregon wrote: ↑Sat Sep 08, 2018 1:29 pm are you actually kidding me? and SH mobility is fine right? whos gonna catch them now? moronic.

On the bright side, SH's might survive more than a split second according to prominent advice chat SH's. xD

Bregon wrote: ↑Sat Sep 08, 2018 1:29 pm are you actually kidding me? and SH mobility is fine right? whos gonna catch them now? moronic.

Pull, pounce, ranged M1, speed training. If you've been spamming pounce then you're doing it wrong.

When you could spam pounce you didn`t have a pull ,and speed training is also irrelevant for loner spec.

Comment was in regards to 'whos gonna catch them now?', i.e. there are methods to catch them.

lefze wrote: ↑Sat Sep 08, 2018 1:04 pm

dansari wrote: ↑Sat Sep 08, 2018 12:01 pm

tazdingo wrote: ↑Sat Sep 08, 2018 10:47 am
oh that sounds cool. is loner anywhere near on par with mara in wb with the recent changes?

No. Survivability is lower due to monstro proc and damage is surprisingly low even with spirit damage (BW pressure is like.. 3-5x better, for a rough comparison).

It's better now. Pre-mitigation numbers are on par with Mara with both in moraledrain spec. I suspect post-mitigation will be significantly lower and with more variance due to no equivalent of 50% armorpen tactic.

Meh.. "better" but imo not worth a wb slot still.

Please note that there seem to be an issue with some assets not loading properly in the client that appears after patching this once. Closing the game and patcher and letting it patch again solves this issue.