Book of Heroes

Why I hate playing my Shadow Warrior now · page 2

Bosses (all the way up to raid LoB) almost never take a swing at my SW so Riposte is 99% useless in that case. Mobs might be if I threw a ton of points into dodge but if I did that, I would be taking gem slots away from haste, crit and magic (or melee if you are a melee SW), why would I do such a silly thing????

If you did a dodge build, it might be useful, but then again, you would be in for some really long battles and would have to spend another 3 points on Maneuver. Even if you optimize a build just for Riposte, it would kick in nowhere as often as Snapcast.

I love that SW has 3 skills that I see no reason to use plus some others that work great with 1 point. That leaves my only debate as a hybrid SW (that leans towards poison) about whether Caltrops, Urgency or Crit Eye is the odd skill out. FYI: Crit Eye is at the moment but it is a pretty close call in my book.
Any single enemy always ends up as chum; that's hardly the point. Anyway, if you don't want to save about 1.2s, on average, against those mobs that won't go down to a simple acid3 pcloud3, I guess that's your business. :)

As for leaving out Caltrops... well, I guess the same applies.
I hate to admit it but SW got a lot weaker. There is no point of me burning gs to race against WM or justicar even with blessing of haste. what happened to balancing out the characters? My 20k might SW can kill mod and bosses easily but if I try to get MVP and race again justicar or WM even the one with lower might than mine I cant surpass them. please don't tell me I need to change the rotation of my attack or build my SW around dodge or full magic or full melee I try it all. simply SW kill way too slow so I see no point of me wasting my money on my cripple SW. yes I still have fun with my SW but I'm not going to burn gs or buying elixirs when I see zero chance of winning.
TCG_japster wrote:The real issue, if any, seems to be about animation display that delays real time. That needs fixing, but not so much of the SW class in general, IMO.

Now that my SW is working better, I can see what you mean. Every attack can generate at least two effects (damage or stun and poison), each requiring its own animation pop up. Every DoT hit slows things down. I've had a single button press generate five separate effects, and they each have an animation pop up that I have to sit through like the ads during a football game.

btw, can an assassinate kills generate a second assassinate hit? I thought I saw that once but not since I've been watchign for it, so maybe it was just my imagination If it does happen I'd expect to have seen it more.

I can think of two ways that Venan could easily improve matters on the slow animations.

First have an option to turn the pop ups off (e.g. I don't need to see the word poisoned to pop up, I can see it from the effect icon). I don't even really need to see the damage/crit pop up, I can tell how I'm doing from the enemy's health bar. I don't need to see the Stun pop up, as the enemy's timer bar displays that information for me.

Second, check monsters for death before status effects. I don't need to know if a monster is poisoned, bleeding, burning, stunned or slowed if it's already dead.

Little_Mike

Site AdminSun Jan 27, 2013 9:58 am
Thanks for all your suggestions, we will be looking into ways to streamlining combat at least by 1.6. Unfortunately, it still may feel a little clunky in 1.5.3, but it is definitely on our list of things to look into.
As for double assassinate: When fighting a mob trio and killing two of three on a single attack, it is possible for each kill to generate an assassinate hit on the remaining target.
Marney wrote:Any single enemy always ends up as chum; that's hardly the point. Anyway, if you don't want to save about 1.2s, on average, against those mobs that won't go down to a simple acid3 pcloud3, I guess that's your business. :)

That math does not work. It depends if they even take a swing at you, then you have to multiple by your dodge percentage and then by the percentage that it procs. No way you are saving 1.2s on average and are you really so slow that your actions take 1.2s? I don't have any SW actions that take so long. I think .75s is my longest (no haste elixir involved). Oh yeah, that doesn't even take into action that the action you are taking wasn't going to kill them anyway before they hit you again.

BTW, the mobs are not going down with a simple acid3 pcloud3, you are better off in 1.5 doing pcloud3 then acid3 because the pcloud DOT kicks in quicker and wipes them out.
FT_NikoNarf wrote:As for double assassinate: When fighting a mob trio and killing two of three on a single attack, it is possible for each kill to generate an assassinate hit on the remaining target.


Thanks NikoNarf, that must be what I saw.

What I thought I saw was a kill on target 1 generating an assassinate on target 2 which killed it, generating an assassinate on target 3, which killed it. Probably the assassinate popped twice on the third monster, the other two having died on the same blow.
Bbbb wrote:That math does not work. It depends if they even take a swing at you, then you have to multiple by your dodge percentage and then by the percentage that it procs. No way you are saving 1.2s on average
You're confusing averages. I said, on average against mobs that don't go down easily to acid3 pcloud3 (ie, mobs that do take a swing at you; obviously, against mobs that never take a swing at you, Riposte won't save you any time at all, duh). That is not the average per fight including mobs that don't get to act. Apples and oranges.
Bbbb wrote:and are you really so slow that your actions take 1.2s? I don't have any SW actions that take so long. I think .75s is my longest (no haste elixir involved)
Same, pcloud is 0.75 at 39.06% Haste (3572). No elixir. With Dodge at 43.27% (+15% from Maneuver) I can easily count on at least two ripostes in any fight over 3s long (multiple behemoths or resist-bugged mobs in the Flame Cavern). Maybe you get so much more damage and crit out of ignoring Dodge that you never let anything move, but I don't see how that math would work either, given the diminishing returns curves.
Bbbb wrote:Oh yeah, that doesn't even take into action that the action you are taking wasn't going to kill them anyway before they hit you again.
Say what?
Bbbb wrote:BTW, the mobs are not going down with a simple acid3 pcloud3, you are better off in 1.5 doing pcloud3 then acid3 because the pcloud DOT kicks in quicker and wipes them out.
Yeah, no. In my experience pcloud3 works better as a finisher.

(edited for a misplaced decimal point)
Musketeer wrote:Probably the assassinate popped twice on the third monster, the other two having died on the same blow.
Right. An assassinate kill can't itself trigger another assassinate proc.