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"