@Gilt I already mentioned to you how close it was, but I realized today that stupid wolverine randomly shifted target from me to you. If not for that, might have ended differently.
-- Grounded in but one perspective, what we perceive is an exaggeration of the truth.
I love my morningstars for 1v1, but using flails to explode people in group fights is too much fun to pass up. You can get that Pulp faster if you don't switch to flails for assault, by the way.
It used to be, but when I tested a few weeks ago morningstar assault was considerably faster than flail assault. The AB file has said it's based on weapon speed for a lot longer than that was actually the case, but as far as I know it was never supposed to work like razeslash.
EDIT: Retested and back to being the same, so not sure what was going on the other week. I've filed a BUG, hopefully they'll clarify how it's supposed to work and either fix it or update the AB file.
Avoiding that one basically comes down to two things:
Either (1) ruining their timing on the restore. You can do this by shielding on command (so they have to hammer pre behead/JitB, which will give you just enough time to stand/do something). This is much more affective vs shaman: jester has tools that will make doing this very problematic. Note that this usually works the first time, usually not the second.
Or (2): don't let the restore happen. This is the ideal option, because it removes any uncertainty and basically kills the strategy before you get into any real danger. It also let's you worry less about the potential for masked confusion, which if you restore under the fight is done. Your best option there is probably just to tumble on the cripple or spam writhe - whichever you're more comfortable with. Tumble gives you a wider margin for error a lot of the time, but its often suboptimal since it also is a long time you're out of the fight compared to just enough to avoid the restore.
Though, really this strategy is a lot weaker now that queueing is a thing. You can basically replace the old writhe standby with whatever you want, since there's no chance of them slipping the restore between the recovery time and the command action. You just have to realise they'll almost certainly not be in the room when doing it, so don't plan on your offense stopping it.
@Makarios giving combat advice is still kinda cool, even if he's telling people how to counteract my scummy-ness.
I always tell people to either chase the Shaman or to diagnose a ton when they're out of the room, to check for the hidden confusion. Eating stannum (or focusing, as @Atalkez said) + tumbling on the cripple works just as well, too. That way they can't force restore, and you'll be able to just apply to cure the breaks.
I mostly just went for it, cause it was f-ing cold, and I kept messing up my locks. Asria laughed afterwards as well, so it was all good.
701, my man. There are definitely fringe cases, but I think that line is just as informative as knowing a numeric value would be for the purposes of knowing when to bstar a majority of the time.
701, my man. There are definitely fringe cases, but I think that line is just as informative as knowing a numeric value would be for the purposes of knowing when to bstar a majority of the time.
Yeah, but if you actually see 701, you'd grab that btwist instead of wasting the balance to attempt bstar vs 'uhh maybe I got it'.
I dunno, a man can hope!
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
It's safer to keep twisting if they are still down, anyway.
Also a neat trick I picked up a long time ago on my alt when he was a BM (rip Perfect Light) was after you get the timing of when they are going to writhe down, you can withdraw blade/impale/twist to get a bit of extra bleeding in if you know they are going to writhe out/stand up after your next twist but before you recover balance.
That may or may not work anymore. They worked in some kind of fail-safe to keep folks from getting perma Impale/Withdraw/Impale looped. Not 100% sure how it works, but if you re-impale, sometimes they still writhe off when the original writhe would have.
-- Grounded in but one perspective, what we perceive is an exaggeration of the truth.
It's safer to keep twisting if they are still down, anyway.
Also a neat trick I picked up a long time ago on my alt when he was a BM (rip Perfect Light) was after you get the timing of when they are going to writhe down, you can withdraw blade/impale/twist to get a bit of extra bleeding in if you know they are going to writhe out/stand up after your next twist but before you recover balance.
This doesn't work anymore!
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
Yeah, I was like "wtf's going on, smoke elm already". Also, make sure tsc toggle is set to not override your commands, so you can shield with aeon (forces gremlin -> no hound), forgot to do that.
Think I might just go bard versus occie from now on to counter enervate by using solo
Just go Priest so you can live eternally whilst crying at night about your inability to cure prep classes who have shield tattoos (@Jhui, @Exelethril) but be feared by all as an unbeatable super goddess regardless of whether you can actually kill people because, well... you're a Priest!
Comments
https://ada-young.appspot.com/pastebin/14c48ca0
@Gilt I already mentioned to you how close it was, but I realized today that stupid wolverine randomly shifted target from me to you. If not for that, might have ended differently.
Results of disembowel testing | Knight limb counter | GMCP AB files
It used to be, but when I tested a few weeks ago morningstar assault was considerably faster than flail assault. The AB file has said it's based on weapon speed for a lot longer than that was actually the case, but as far as I know it was never supposed to work like razeslash.
EDIT: Retested and back to being the same, so not sure what was going on the other week. I've filed a BUG, hopefully they'll clarify how it's supposed to work and either fix it or update the AB file.
Results of disembowel testing | Knight limb counter | GMCP AB files
I forgot this was a thing, for a while.
https://ada-young.appspot.com/pastebin/99f3ea57
Thank you, @Mizik, for reminding me of it during our spars.
Avoiding that one basically comes down to two things:
Either (1) ruining their timing on the restore. You can do this by shielding on command (so they have to hammer pre behead/JitB, which will give you just enough time to stand/do something). This is much more affective vs shaman: jester has tools that will make doing this very problematic. Note that this usually works the first time, usually not the second.
Or (2): don't let the restore happen. This is the ideal option, because it removes any uncertainty and basically kills the strategy before you get into any real danger. It also let's you worry less about the potential for masked confusion, which if you restore under the fight is done. Your best option there is probably just to tumble on the cripple or spam writhe - whichever you're more comfortable with. Tumble gives you a wider margin for error a lot of the time, but its often suboptimal since it also is a long time you're out of the fight compared to just enough to avoid the restore.
Though, really this strategy is a lot weaker now that queueing is a thing. You can basically replace the old writhe standby with whatever you want, since there's no chance of them slipping the restore between the recovery time and the command action. You just have to realise they'll almost certainly not be in the room when doing it, so don't plan on your offense stopping it.
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
I like to manual focus on the cripple, so the restore doesn't hurt too bad to just tank it.
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
I always tell people to either chase the Shaman or to diagnose a ton when they're out of the room, to check for the hidden confusion. Eating stannum (or focusing, as @Atalkez said) + tumbling on the cripple works just as well, too. That way they can't force restore, and you'll be able to just apply to cure the breaks.
I mostly just went for it, cause it was f-ing cold, and I kept messing up my locks. Asria laughed afterwards as well, so it was all good.
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
I dunno, a man can hope!
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
You hope for that while I hope for less vague BM limb damage.
Also a neat trick I picked up a long time ago on my alt when he was a BM (rip Perfect Light) was after you get the timing of when they are going to writhe down, you can withdraw blade/impale/twist to get a bit of extra bleeding in if you know they are going to writhe out/stand up after your next twist but before you recover balance.
Penwize has cowardly forfeited the challenge to mortal combat issued by Atalkez.
Then again, why am I even using anti-illusion after the nerfs..
[ SnB PvP Guide | Link ]
I'm over here curing out of true locks in aeon, keeping full mana, maintaining offense and shit.
Think I might just go bard versus occie from now on to counter enervate by using solo
[ SnB PvP Guide | Link ]
Or stay SnB and cure aeon better. That works too.