I think I should have restored instead of tumbled, but what else should I do in this situation?
Pre restore, tumble earlier, restore then mind game with mending applications after you dodge the first vivisect. Aerek, Xer, Hasar, and Tirac off the top of my head had amazing vivisect mind games after they properly cured the first vivisect. Since if you're 2L1A (two leg one arm) prepped then there's a second chance to be vivisected if you don't cure the second wave of epteth right.
1) remember to restore after the second break 2) NEVER apply restoration when: you're not being impaled AND your rebounding is down AND you're not on equilibrium (and thus can't restore).
I think I should have restored instead of tumbled, but what else should I do in this situation?
I don't get why your system thought your right arm was damaged as well when he broke the left? That's something that could throw off any curing logic you built, even if you built it right.
-- Grounded in but one perspective, what we perceive is an exaggeration of the truth.
I think I should have restored instead of tumbled, but what else should I do in this situation?
I don't get why your system thought your right arm was damaged as well when he broke the left? That's something that could throw off any curing logic you built, even if you built it right.
I'm not sure either. I noticed it, too. I've just chalked it up to a bug, and hope to find it again so I have a little more knowledge about it.
My RESTORE alias pauses system and smokes rebound. Then when they break #3 I apply a single mending (apply mending, doesn't show limb healed, usually not highlighted) and we both just sit there while either I get eq or rebounding comes up. Then restore again on the 4th DSL if necessary.
Most of the time, you don't actually have to "smoke rebound", unless you already have it off keepup by default for limb counting purposes. So the window which rebounding pops up is pretty random and unpredictable within the rebounding time frame.
You can just do the standard restore on EQ/don't apply resto while off EQ/just apply mending and never get vivi'd. I like the idea of forcing restore on 3rd break with an off-hand epseth apply with (leg -> arm -> arm) into riftlock with a heavy venom stack, since they'll be prone and just eating DSLs for awhile.
I like the idea of forcing restore on 3rd break with an off-hand epseth apply with (leg -> arm -> arm) into riftlock with a heavy venom stack, since they'll be prone and just eating DSLs for awhile.
Didn't do the math or think it through though.
Easy enough to force the restore if they do it automatically, but maybe not if they do it manually (unless they panic). If you can't vivisect me after the second doubleslash, I don't really need to restore at all; I can just wait for my leg to finish curing a tiny bit after the third doubleslash, apply mending twice, then stand up and fly out.
No need to eat bloodroot for paralysis if you're prone with damaged/mangled legs, either, so may be hard to get sufficient affliction momentum to get a riftlock (though most people likely don't ignore paralysis/push other afflictions ahead of it on prone + damaged/mangled legs).
Bleak misses you with his dirk by a hair. Striking like a snake, Bleak follows the first attack with another. You feel a tightening sensation grow in your lungs. 4643h, 5315m, 21295e, 24695w cekdb-1k Willibrord, an undersized black raven wounds you with a glancing cut. Your mind feels suddenly vacant as Revius, the black raven levels its gaze at you. 4571h, 5315m, 21305e, 24695w cekdb-1k (-72h) What do you want to eat? 4571h, 5315m, 21305e, 24695w cekdb-1k 4571h, 5315m, 21305e, 24695w cekdb-1k You remove 1 aurum, bringing the total in the Rift to 1387. 4571h, 5315m, 21305e, 24695w cekdb-1k You eat an aurum flake. Your bronchial tubes open up and your asthma is cured. 4571h, 5315m, 21305e, 24695w cekdb- You have recovered balance on all limbs. [System]: Running queued eqbal command: QUEUEALIAS You quickly prick Bleak with your dirk. [Curare + Vernalius] Striking like a snake, you prick Bleak a second time with your dirk. Horror overcomes Bleak's face as his body stiffens into paralysis. 4571h, 5315m, 21295e, 24695w cekdb- You may check someone for afflictions once again. 4571h, 5315m, 21295e, 24695w cekdb- [Bleak ATE BLOODROOT] 4571h, 5315m, 21295e, 24695w cekdb- Bleak misses you with his dirk by a hair. Striking like a snake, Bleak follows the first attack with another. You feel a tightening sensation grow in your lungs.
This is why you need to swap curare positions when clumsy.
Why swap rather than just always envenoming curare second? Seems simpler.
I meant I have curare hitting first. Envenom second is my default and I swap it to first if clumsy. It got really confusing to code because of the single weapon double venom thing.
If your first stab misses, you still want curare envenomed second, assuming you want curare to be the venom that hits, because the venom isn't used up when you miss, so whatever is envenomed second and ordinarily hits first is what will hit second if first misses, no?
Yes. Basically always want to be doing DSTAB X CURARE. In that case, curare will be first. If you hit rebounding, you'll get paralysis only. If you miss the first stab, they'll get paralysis only (because missing shouldn't use up the venom). If neither, they get both (paralysis first, then whatever aff X gives).
(It sure would be more intuitive if command order corresponded to the order they hit in...)
I like the idea of forcing restore on 3rd break with an off-hand epseth apply with (leg -> arm -> arm) into riftlock with a heavy venom stack, since they'll be prone and just eating DSLs for awhile.
Didn't do the math or think it through though.
Easy enough to force the restore if they do it automatically, but maybe not if they do it manually (unless they panic). If you can't vivisect me after the second doubleslash, I don't really need to restore at all; I can just wait for my leg to finish curing a tiny bit after the third doubleslash, apply mending twice, then stand up and fly out.
No need to eat bloodroot for paralysis if you're prone with damaged/mangled legs, either, so may be hard to get sufficient affliction momentum to get a riftlock (though most people likely don't ignore paralysis/push other afflictions ahead of it on prone + damaged/mangled legs).
Yah, I guess it boils down to whether someone auto-restores or not. Come to think of it.. having a trigger that lowers para prio on prone + damaged/mangled legs, then swaps back is a really good idea.
I think a focus lock before breaks might be necessary to offset the aff momentum loss from double delph/1 epseth (though maggots do help lots).
Good points @ envenoming. The input on the command should probably reflect hit order to avoid this confusion, though. Just had to write it out to see where I was wrong
Good points @ envenoming. The input on the command should probably reflect hit order to avoid this confusion, though. Just had to write it out to see where I was wrong
I don't see why it's so difficult. Consider it like layers. The top layer (applied last) has to come off first.
How did all you speed knights pre-envenom rapiers?
Tharos, the Announcer of Delos shouts, "It's near the end of the egghunt and I still haven't figured out how to pronounce Clean-dat-hoo."
It's the tracking of order vs the syntax that is dissonant. Pre envenoming two separate weapons makes a lot of sense with your logic because you're just taking the top layer from each.
It's not difficult, it's just inconsistent with other modern in-line envenoming options. Modern combat doesn't often apply things in layers anymore, it usually takes advantage of the in-line envenoming feature to apply as you attack, which was implemented for player convenience and new-player friendliness:
DSL Knight: DSL TARGET VENOM1 VENOM2, with venom1 applied to the left sword (hits first) and venom2 on the right sword. (hits second)
SNB Knight: COMBO TARGET VENOM1 SHIELDTECH, with venom1 hitting before the shield does.
In all of these cases, venom1 hits before venom2; it's designed that way. Serpent is just suddenly an outlier, where DSTAB TARGET VENOM1 VENOM2 hits with the second venom first. Yes, the envenoming mechanics are the same as they always have been, and yes, all that's needed is to flip the order you send them, but that's not really the point. The point is that a consistent system used by all venom/aff-using classes is now inconsistent in regard to one class, and when the whole point of in-line envenoming is to make things easier and more intuitive for new/old players to pick up and fight with, that kinda defeats its own purpose.
No one is saying it's "too hard". Seasoned combatants are just saying, "Hey, this feature implemented for our convenience would be more convenient if it understood envenoming mechanics and applied them in the logical order, so that it behaved like every other class that uses this same feature."
-- Grounded in but one perspective, what we perceive is an exaggeration of the truth.
Bah, too late to edit (BSOD whilst editing). All of the examples above are mechanically different to applying two venoms to a single weapon. Indeed. in many cases, not even venom related.
Tharos, the Announcer of Delos shouts, "It's near the end of the egghunt and I still haven't figured out how to pronounce Clean-dat-hoo."
Comments
1) remember to restore after the second break
2) NEVER apply restoration when: you're not being impaled AND your rebounding is down AND you're not on equilibrium (and thus can't restore).
You can just do the standard restore on EQ/don't apply resto while off EQ/just apply mending and never get vivi'd. I like the idea of forcing restore on 3rd break with an off-hand epseth apply with (leg -> arm -> arm) into riftlock with a heavy venom stack, since they'll be prone and just eating DSLs for awhile.
Didn't do the math or think it through though.
[ SnB PvP Guide | Link ]
No need to eat bloodroot for paralysis if you're prone with damaged/mangled legs, either, so may be hard to get sufficient affliction momentum to get a riftlock (though most people likely don't ignore paralysis/push other afflictions ahead of it on prone + damaged/mangled legs).
Results of disembowel testing | Knight limb counter | GMCP AB files
(It sure would be more intuitive if command order corresponded to the order they hit in...)
Results of disembowel testing | Knight limb counter | GMCP AB files
I think a focus lock before breaks might be necessary to offset the aff momentum loss from double delph/1 epseth (though maggots do help lots).
[ SnB PvP Guide | Link ]
How did all you speed knights pre-envenom rapiers?
- DSL Knight: DSL TARGET VENOM1 VENOM2, with venom1 applied to the left sword (hits first) and venom2 on the right sword. (hits second)
- SNB Knight: COMBO TARGET VENOM1 SHIELDTECH, with venom1 hitting before the shield does.
- Old Serpent: DSTAB TARGET VENOM1 VENOM2
- Apostate: DEADEYES TARGET AFFLICTION1 AFFLICTION2
- Alchemist: TRUEWRACK TARGET AFFLICTION1 AFFLICTION2
- Sylvan: SYNCHRONISE AFFLICTION1 AFFLICTION2 TARGET
- Shaman: JINX AFFLICTION1 AFFLICTION2 TARGET
In all of these cases, venom1 hits before venom2; it's designed that way. Serpent is just suddenly an outlier, where DSTAB TARGET VENOM1 VENOM2 hits with the second venom first. Yes, the envenoming mechanics are the same as they always have been, and yes, all that's needed is to flip the order you send them, but that's not really the point. The point is that a consistent system used by all venom/aff-using classes is now inconsistent in regard to one class, and when the whole point of in-line envenoming is to make things easier and more intuitive for new/old players to pick up and fight with, that kinda defeats its own purpose.No one is saying it's "too hard". Seasoned combatants are just saying, "Hey, this feature implemented for our convenience would be more convenient if it understood envenoming mechanics and applied them in the logical order, so that it behaved like every other class that uses this same feature."
Before two towering mountains (road).
[north - Leviticus (1)]
Results of disembowel testing | Knight limb counter | GMCP AB files
Results of disembowel testing | Knight limb counter | GMCP AB files