Help with Witch Elf
231 views
Skip to first unread message
nathan...@googlemail.com
Jun 22, 2009, 1:42:37 AM6/22/09
to NerfedButtons
Hey, prior post i asked about Nb toggled pages and i taught myself
some basic Nerfed Buttons but wanting to learn more about it, Basic NB
i set up /nb add 1[Kiss of Agony]st:1:s[Slice]
Looking to set up sequences for the following: -
This one i would like to have in sequence with checks in to see if KOA
is on myself and to see if the target has a blessing, issue i have at
the minute as well is with Agonizing wound it seems to overwrite
slice.
Kiss of Agony[ID:9402]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
Slice[ID:9398]
Next would be: -
Kiss of Death[9407]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
Throat Slitter[ID:9409]
Slice[ID:9398]
If possible with a check in there to allow me not to remove the Kiss
buff i have on since these are based on me been behind my target, also
since i have a third kiss i can use to remove one kiss to replace with
another and with the second sequence if not all skills can be added to
a sequence then breaking it down to: -
Throat Slitter[ID:9409]
Slice[ID:9398]
the above two skills onto a separate hot bar key.
Skills like heart seeker and Server limb i keep separate and use as
required not always off burst mainly dependent on the target.
Mastery Tree if any relevance is Carnage/Trech.
Any additional advice for setting up sequences is appreciated, also
something i have noticed and i think would be great if it hasn't
already been added is to allow sequences to be bound to alphabetical
characters since key bindings are used by most and again i don't know
if this has been added.
some basic Nerfed Buttons but wanting to learn more about it, Basic NB
i set up /nb add 1[Kiss of Agony]st:1:s[Slice]
Looking to set up sequences for the following: -
This one i would like to have in sequence with checks in to see if KOA
is on myself and to see if the target has a blessing, issue i have at
the minute as well is with Agonizing wound it seems to overwrite
slice.
Kiss of Agony[ID:9402]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
Slice[ID:9398]
Next would be: -
Kiss of Death[9407]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
Throat Slitter[ID:9409]
Slice[ID:9398]
If possible with a check in there to allow me not to remove the Kiss
buff i have on since these are based on me been behind my target, also
since i have a third kiss i can use to remove one kiss to replace with
another and with the second sequence if not all skills can be added to
a sequence then breaking it down to: -
Throat Slitter[ID:9409]
Slice[ID:9398]
the above two skills onto a separate hot bar key.
Skills like heart seeker and Server limb i keep separate and use as
required not always off burst mainly dependent on the target.
Mastery Tree if any relevance is Carnage/Trech.
Any additional advice for setting up sequences is appreciated, also
something i have noticed and i think would be great if it hasn't
already been added is to allow sequences to be bound to alphabetical
characters since key bindings are used by most and again i don't know
if this has been added.
Deuce
Jun 22, 2009, 3:03:49 AM6/22/09
to NerfedButtons
NB sequences aren't bound to keys, they're bound to slots on your
hotbar. Your hotbar is only set up to use the number keys by
default. You can change your hotbar buttons to be bound to any key on
your keyboard, essentially, including using shift, alt, and control as
modifiers. You just have to retrain yourself to not think of the
buttons as being attached sequentially to the numbers on your kb.
As far as "sequences" go, the word's a misnomer. NB doesn't actually
create sequences to fire abilities off in a specific order. What it
does is allow you to set up PRIORITY chains by dint of the order you
list abilities in and CHECKS to define when you want those abilities
to be valid. You could set it up to fire off in specific order by
using Virtual Cooldowns that would disallow each ability from queueing
for a set period of time, forcing the chain to move on to the next
ability, but it would be clunky and not adapt well to changing
targets.
I'm not sure quite what you're looking for here as far as your
seperate chains. The only differences are the Kiss and the addition
of Throat Slitter. Are you looking for seperate chains based on
target, switching your Kiss to match the chain? Do you want seperate
chains with seperate Kisses, but NOT switch if you already have one
up? Is one meant to be a chain used from the rear? You could do one
chain, putting target restrictions on the couple abilities that are
different. What, exactly, do Kisses have to do with being behind your
target? Do you only want AW to fire when you're behind your target?
The reason AW is queueing and not allowing Slice to queue is because
you set the priority chain by listing them in that order. With no
checks to give it further directions, the mod is queueing the FIRST
valid ability. You're obviously already using the Stack check so that
you won't use another KoA until it wears off, and Sever Blessing has a
built-in requirement that the target must have a Blessing, so it gets
to AW. AW, by default, can be used any time you're in melee range
with an enemy target to your front, just like Slice. It just works
better from the rear. In other words, there is never a time you can
use Slice but can't use AW. Since AW meets all the requirements, it
will continue to queue and never allow Slice in. Then you can begin
adding requirements through checks to make AW only valid under
specific circumstances, so that it'll move on to Slice when those
checks aren't met.
On Jun 22, 1:42 am, "nathansfe...@googlemail.com"
hotbar. Your hotbar is only set up to use the number keys by
default. You can change your hotbar buttons to be bound to any key on
your keyboard, essentially, including using shift, alt, and control as
modifiers. You just have to retrain yourself to not think of the
buttons as being attached sequentially to the numbers on your kb.
As far as "sequences" go, the word's a misnomer. NB doesn't actually
create sequences to fire abilities off in a specific order. What it
does is allow you to set up PRIORITY chains by dint of the order you
list abilities in and CHECKS to define when you want those abilities
to be valid. You could set it up to fire off in specific order by
using Virtual Cooldowns that would disallow each ability from queueing
for a set period of time, forcing the chain to move on to the next
ability, but it would be clunky and not adapt well to changing
targets.
I'm not sure quite what you're looking for here as far as your
seperate chains. The only differences are the Kiss and the addition
of Throat Slitter. Are you looking for seperate chains based on
target, switching your Kiss to match the chain? Do you want seperate
chains with seperate Kisses, but NOT switch if you already have one
up? Is one meant to be a chain used from the rear? You could do one
chain, putting target restrictions on the couple abilities that are
different. What, exactly, do Kisses have to do with being behind your
target? Do you only want AW to fire when you're behind your target?
The reason AW is queueing and not allowing Slice to queue is because
you set the priority chain by listing them in that order. With no
checks to give it further directions, the mod is queueing the FIRST
valid ability. You're obviously already using the Stack check so that
you won't use another KoA until it wears off, and Sever Blessing has a
built-in requirement that the target must have a Blessing, so it gets
to AW. AW, by default, can be used any time you're in melee range
with an enemy target to your front, just like Slice. It just works
better from the rear. In other words, there is never a time you can
use Slice but can't use AW. Since AW meets all the requirements, it
will continue to queue and never allow Slice in. Then you can begin
adding requirements through checks to make AW only valid under
specific circumstances, so that it'll move on to Slice when those
checks aren't met.
On Jun 22, 1:42 am, "nathansfe...@googlemail.com"
nathan...@googlemail.com
Jun 22, 2009, 4:08:47 AM6/22/09
to NerfedButtons
After reading what you have stated above that NB que's abilities based
on specific requirements and not allowing Slice to fire because AW is
always active then would it be better to structure them over 3 hot bar
slots: -
Kiss of Agony[ID:9402]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
=====================================
Kiss of Death[9407]
Throat Slitter[ID:9409]
=====================================
Kiss of Betrayal[ID:9412]
Sever Limb[ID:9400]
Slice[ID:9398]
=====================================
For the above if i could have the checks on so that they come up when
my target has either the blessing or i parry allowing myself to cast
Sever Limb, and would separating out Slice and AW work much better?
As for the above: -
/nb add #[Kiss of Agony]st:1:s[Sever Blessing](conditional Checks??!)
[Agonizing Wound]
Not sure of the conditional checks for Sever Blessing or Sever Limb
======================================================
/nb add #[Kiss of Death]st:1:s [Throat Slitter]
==========================================
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb] (conditional Checks??!)
[Slice]
=====================================
Another priority chain that i would like to set up is: -
Wracking Pains[ID:9405]
Envenomed Blade[ID:9403]
Pierce Armor[ID:9421]
Above i can limit Wracking pains to one per target, i presume the same
would be for envenomed blade, so something like: -
/nb add #[Wracking Pains]st:1:s[Envenomed Blade]st:3:s[Pierce Armor]
Would this be valid ?
============================================
Hope this is more clear, Thanks
on specific requirements and not allowing Slice to fire because AW is
always active then would it be better to structure them over 3 hot bar
slots: -
Kiss of Agony[ID:9402]
Sever Blessing[ID:9413]
Agonizing Wound [ID:9408]
Kiss of Death[9407]
Throat Slitter[ID:9409]
=====================================
Kiss of Betrayal[ID:9412]
Sever Limb[ID:9400]
Slice[ID:9398]
=====================================
For the above if i could have the checks on so that they come up when
my target has either the blessing or i parry allowing myself to cast
Sever Limb, and would separating out Slice and AW work much better?
As for the above: -
/nb add #[Kiss of Agony]st:1:s[Sever Blessing](conditional Checks??!)
[Agonizing Wound]
Not sure of the conditional checks for Sever Blessing or Sever Limb
======================================================
/nb add #[Kiss of Death]st:1:s [Throat Slitter]
==========================================
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb] (conditional Checks??!)
[Slice]
=====================================
Another priority chain that i would like to set up is: -
Wracking Pains[ID:9405]
Envenomed Blade[ID:9403]
Pierce Armor[ID:9421]
Above i can limit Wracking pains to one per target, i presume the same
would be for envenomed blade, so something like: -
/nb add #[Wracking Pains]st:1:s[Envenomed Blade]st:3:s[Pierce Armor]
Would this be valid ?
============================================
Hope this is more clear, Thanks
Deuce
Jun 22, 2009, 6:29:15 AM6/22/09
to NerfedButtons
All the chains you listed would work. You could make much more
efficient chains and even put all that into one chain, but there's
nothing terribly wrong with those if you're happy with them. That
last one does seem like an odd combination, though.
As long as you're specced for Heart Seeker, it's possible to add a
quasi-positional check to AW using the Ability Enabled check. What
this does is it checks an ability OTHER than the one you're attaching
it to, to see if it passes that abilities BUILT-IN requirements. In
this case, HS has the requirement of "back only," so if you use the AE
check linked to HS, then the ability you're putting the check on will
only work when you're behind your target or have Feinted Positioning
buff.
[Agonizing Wound]ae:9427:+[Slice]
will make AW fire when it will ignore armor and default to Slice the
rest of the time.
On Jun 22, 4:08 am, "nathansfe...@googlemail.com"
efficient chains and even put all that into one chain, but there's
nothing terribly wrong with those if you're happy with them. That
last one does seem like an odd combination, though.
As long as you're specced for Heart Seeker, it's possible to add a
quasi-positional check to AW using the Ability Enabled check. What
this does is it checks an ability OTHER than the one you're attaching
it to, to see if it passes that abilities BUILT-IN requirements. In
this case, HS has the requirement of "back only," so if you use the AE
check linked to HS, then the ability you're putting the check on will
only work when you're behind your target or have Feinted Positioning
buff.
[Agonizing Wound]ae:9427:+[Slice]
will make AW fire when it will ignore armor and default to Slice the
rest of the time.
On Jun 22, 4:08 am, "nathansfe...@googlemail.com"
nathan...@googlemail.com
Jun 22, 2009, 10:45:43 AM6/22/09
to NerfedButtons
/nb add #[Kiss of Agony]st:1:s[Sever Blessing]
======================================================
/nb add #[Kiss of Death]st:1:s [Throat Slitter]
==========================================
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]
ok good to know they work, next problem though
/nb add #[Kiss of Agony]st:1:s[Sever Blessing]:e[Agonizing Wound]
and then i presume that Severe limb would be on myself since the
requirement for me to parry, so we have: -
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
Ok after testing these ingame they appear to work but the only issue i
have now is that when i activate one kiss for example: -
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
so if i have hit the above key the next one will show: -
/nb add #[Kiss of Death]st:1:s [Throat Slitter]
"Rebuff" myself with that kiss before been able to access the rest of
the ability chain, although i am thinking this would work to my
benefit cause its causing me to be using all my attacks rather than
just sticking with one individual kiss at a time, but would be helpful
if i new how to restrict this after i try out the above further in
oRvr.
Also you asked about stating that this appears to be odd
Wracking Pains[ID:9405]
Envenomed Blade[ID:9403]
Pierce Armor[ID:9421]
restriction of these skills to one and 3 per target then firing off PA
since it buffs weapon skill with ther target having an ailment,
although it interests me in how you would do this personally?
i myself would set this up as
/nb add #[Wracking Pains]st:1:s[Envenomed Blade]st:3:s[Pierce Armor]
keys i use to around ten or so, based on the key bindings i use for
myself personally and your comment on HS + FP i have these bound to
specific keys so that i can fire them at will, if some how i manage to
end up in front of my target usually when getting smacked from behind
i hit FP + HS then switch either to behind my target or Shadow Prowler
and escape
Thanks for the help so far, even though i understood some of this
addons features i still found it a bit confusing maybe later at some
point i might find a requirement for the positional checks, ability
cool downs but for now i find the above set up would work perfectly
thylantyr
Jun 22, 2009, 12:13:15 PM6/22/09
to NerfedButtons
This is my Kiss design.
[Kiss of Betrayal];st:1: s;e:9407:1: s:-: p;e:9402:1: s:-: p
The concept is to use a default Kiss, in this case it's KoB
because it's the one I use more often as it returns action points,
IMO very important as the WE class runs out of AP quickly.
The string design is to allow the user to manually override with a
different Kiss without having the mod re-enable a Kiss that you
already applied. This works great. To be honest, I think healing
is overpowered and KoD is not a great ability at high levels,
you might find yourself out of AP and dead in the water. If you
solo gank a healer, you can manually override the default and
apply KoD if you want, but often healers don't fight back and
it becomes an endurance fight, who will run out of AP first? The
Witch Elf or healer? If I have KoB buffed, I get extra AP
and I usually win those fights.
[Kiss of Betrayal];st:1: s;e:9407:1: s:-: p;e:9402:1: s:-: p
The concept is to use a default Kiss, in this case it's KoB
because it's the one I use more often as it returns action points,
IMO very important as the WE class runs out of AP quickly.
The string design is to allow the user to manually override with a
different Kiss without having the mod re-enable a Kiss that you
already applied. This works great. To be honest, I think healing
is overpowered and KoD is not a great ability at high levels,
you might find yourself out of AP and dead in the water. If you
solo gank a healer, you can manually override the default and
apply KoD if you want, but often healers don't fight back and
it becomes an endurance fight, who will run out of AP first? The
Witch Elf or healer? If I have KoB buffed, I get extra AP
and I usually win those fights.
Tony Hoyt
Jun 22, 2009, 12:57:07 PM6/22/09
to nerfed...@googlegroups.com
I use Kiss of Death on any support class, but will go with Kiss of Betrayal for any other class. AP Drain is very nice, but for healers, I need to debuff incoming and outgoing heals. So it's a situation of using the right kisses at the right time. It's not perfect but it's quite functional
[kiss of death]a:supp;st:1:p
[Kiss of Betrayal];st:1:s;e:9407:1:s:-:p;e:9402:1:s:-:p
[kiss of death]a:supp;st:1:p
[Kiss of Betrayal];st:1:s;e:9407:1:s:-:p;e:9402:1:s:-:p
nathan...@googlemail.com
Jun 22, 2009, 7:37:45 PM6/22/09
to NerfedButtons
Ok based on what you have said and based upon how i've designed each
key which part of your code designates the default kiss and prevents
me from over writing it without me over writing it manually
Here is one that i am using as above
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
but based on what you have added to yours if i modify each individual
one to something like: -
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
but based on your kiss chain
/nb add #[Kiss of Betrayal];st:1: s;e:9407:1: s:-: p;e:9402:1: s:-: p
[Sever Limb]:s[Slice]
Thus preventing a kiss to be active if i have another one that is
currently active
Then to add the other hotbar keys into this
/nb add #[Kiss of Agony];st:1: s;e:9407:1: s:-: p;e:9412:1: s:-: p
kiss?
/nb add #[Kiss of Death]st:1: s;e:9402:1: s:-: p;e:9412:1: s:-: p
[Throat Slitter]
Based on these above of which i am about to try out hopefully they
should work and allowing me to over write manually a kiss that i
choose
key which part of your code designates the default kiss and prevents
me from over writing it without me over writing it manually
Here is one that i am using as above
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
but based on what you have added to yours if i modify each individual
one to something like: -
/nb add #[Kiss of Betrayal]st:1:s [Sever Limb]:s[Slice]
but based on your kiss chain
/nb add #[Kiss of Betrayal];st:1: s;e:9407:1: s:-: p;e:9402:1: s:-: p
[Sever Limb]:s[Slice]
Thus preventing a kiss to be active if i have another one that is
currently active
Then to add the other hotbar keys into this
/nb add #[Kiss of Agony];st:1: s;e:9407:1: s:-: p;e:9412:1: s:-: p
[Sever Blessing]:e[Agonizing Wound]
Same applied to the next one with the changes made based on the active
kiss?
/nb add #[Kiss of Death]st:1: s;e:9402:1: s:-: p;e:9412:1: s:-: p
[Throat Slitter]
Based on these above of which i am about to try out hopefully they
should work and allowing me to over write manually a kiss that i
choose
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
Message has been deleted
0 new messages