bind/target question

Hey, I'm looking for a way to bind a key to do these three things:

target nearest dead pet
follow
powexecname soul extraction

The only part I'm not totally familiar with is the targeting commands. Can I get a hand?

---

Where to now?
Check out all my guides and fiction pieces on my blog.
The MFing Warshade | The Last Rule of Tanking | The Got Dam Mastermind
Everything Dark Armor | The Softcap
don'T attempt to read tHis mEssaGe, And believe Me, it is not a codE.

http://wiki.cohtitan.com/wiki/Target...Slash_Command)

target_custom_next defeated mypet

The only problem I'm seeing is placement of the follow and whether or not it will enact on your current target, or wait to follow the new target. The powexec would also have to be queued after the target is selected as well. I guess only way to know is to try different combinations and see how reliable they work out.

There are some tricks that might allow you to select the new target on key-press, and then follow on key-release, which might help reliability with the slight delay.

Some people use it for SB'ing the team. I can't think of it off the top of my head. I do have a character with the binds, but I am not logged in to be able to /bindsave and check it out for you at the moment.

---

Thanks for the help, and the link.

[ QUOTE ]
There are some tricks that might allow you to select the new target on key-press, and then follow on key-release, which might help reliability with the slight delay.

[/ QUOTE ]

I'm going to have to look this up. I can't imagine the possibilities this would allow.

---

Where to now?
Check out all my guides and fiction pieces on my blog.
The MFing Warshade | The Last Rule of Tanking | The Got Dam Mastermind
Everything Dark Armor | The Softcap
don'T attempt to read tHis mEssaGe, And believe Me, it is not a codE.

[ QUOTE ]
Thanks for the help, and the link.

[ QUOTE ]
There are some tricks that might allow you to select the new target on key-press, and then follow on key-release, which might help reliability with the slight delay.

[/ QUOTE ]

I'm going to have to look this up. I can't imagine the possibilities this would allow.

[/ QUOTE ] I hope somebody chimes in with something that points in the right direction. It wouldn't be for several hours before I will be able to check on this and get back to you.

I originally got the commands from the forums, and we had some debates/discussions over how well they worked and how necessary they were. I'm sure the threads have long since been purged.. but the people involved are still around...

---

This works for toggles, so it may also work for targeting. The problem would be making sure the commands executed in the correct order. Otherwise you may find yourself following your previous target before the new target command is issued.

Anyway, this works:

/bind a "+down$$powexectoggleon Deflection$$powexectoggleon battle agility"

This turns on Battle Agility when I press "a" and then turns on Deflection when I release it. The "+down" basically makes the bound key look for pressing and releasing as two separate actions You use "+down" because you don't want to start running or jumping when you press the key. +down will make you drop if you are flying though.

So you could try:

/bind a "+down$$follow$$target_custom_next defeated mypet"
or
/bind a "+down$$target_custom_next defeated mypet$$follow"

Play around with it and see?

---

[SIZE=1][COLOR=Yellow][U]Virtue Heroes (Serenity's Children):[/U] [B]@Eek a Mouse, The Devil's Mark, Outlaw Sniper, Gas-Soaked Rag Man, Amazon Prime, Friday's Child, Hot Blooded,[/B][B]Flower of the Moon[/B], [B]Rouge Demon Hunter[/B], Stimulated Emission, Animatronic Wench, [B]Lennie Small[/B]
[U]Virtue Villains (Serenity's Orphans):[/U][/COLOR][/SIZE][SIZE=1][COLOR=Yellow] [/COLOR][/SIZE] [SIZE=1][COLOR=Yellow] [B]Eek a Rat[/B], [B]Bomb Blondeshell[/B], Babe Brute, Jeanne Dark, Fallen Angle[/COLOR][/SIZE]

"+down" doesn't necessarily make the bound key "look" for pressing and releasing as two separate actions...

What happens is the execution of "+down" is a movement which continues as the key is being pressed. As soon as you release, it stops executing, and continues to the next command in the bind. You could also use "+up", "+forward", "+back", "+left", or "+right", but like you said.. "+down" is the least bothersome as most people are already near the ground when they want use binds like this. Running off would be annoying. lol

Also, you forgot powexecname soul extraction.

My guess is...
/bind a "+down$$target_custom_next defeated mypet$$follow$$powecexname Soul Extraction"
...should set the target upon key-press, then follow and queue the power on key-release... then the power will execute when you are close enough.

Let us know how it goes.

---

/bind Y "+down$$target_custom_next defeated mypet$$follow$$powexecname Soul Extraction"

I'm giving this a try. I'll edit the post as soon as I know.

Verdict: Follow doesn't work. I'm guessing because +down is a conflicting movement vector? Either way, it targets the pet and hits the power immediately, and I just realized the power has a 60 ft range, so I don't really need to follow anyway. Thanks for the help everyone.

Final used command: /bind Y "targetcustomnext defeated mypet$$powexecname soul extraction"

It's a lot simpler than I was making it out to be.

---

Where to now?
Check out all my guides and fiction pieces on my blog.
The MFing Warshade | The Last Rule of Tanking | The Got Dam Mastermind
Everything Dark Armor | The Softcap
don'T attempt to read tHis mEssaGe, And believe Me, it is not a codE.

I was under the impression that binds executed from right to left. Has that changed?

---

[ QUOTE ]
I was under the impression that binds executed from right to left. Has that changed?

[/ QUOTE ] As far as I can tell, it's always been left to right.

The only exception is between powexec commands.. it activates the last power in the chain, and queues the second to last, making it look like it's being read right to left. Other commands are processed left to right anyway.

Somebody had a good explanation as to why it does it that way, but I forgot what it was. lol

---

[ QUOTE ]
[ QUOTE ]
I was under the impression that binds executed from right to left. Has that changed?

[/ QUOTE ] As far as I can tell, it's always been left to right.

[/ QUOTE ]This is right.

[ QUOTE ]
The only exception is between powexec commands.. it activates the last power in the chain, and queues the second to last, making it look like it's being read right to left. Other commands are processed left to right anyway.

[/ QUOTE ]This is wrong. Powexecname still opperates left-to-right, the misconception comes in because powexecname doesn't immediately execute the power... there's still the delay (either the server/client wait some time to start it, or the bind waits), meaning the second instance of powexecname will completely replace the first! This will continue on until the bind is finished, so that only the LAST instance of powexecname matters (also, the second to last is not queued!). Powers will only be 'queued' (with the red circle) by powexecname under the same circumstances as they'd be queued if you manually clicked on a power's icon.

If you want to try to visualize how powexecname works, you can reproduce the same behavior using the normal 1-0 binds. Find a grey con enemy, and have an attack in '1' and '2'... press 1 and IMMEDIATELY press '2' after, and if you're quick enough, only 2 will activate (I just did this myself to confirm that it did indeed work this way). This is basically what the binds are doing (it's possible that if you DID have zero latency to the server, using a bind MIGHT cause the first powexecname to execute instead... but without using something like wireshark we (players) can't really know that for sure).

---

[ QUOTE ]
[ QUOTE ]
The only exception is between powexec commands.. it activates the last power in the chain, and queues the second to last, making it look like it's being read right to left. Other commands are processed left to right anyway.

[/ QUOTE ]This is wrong. Powexecname still opperates left-to-right, the misconception comes in because powexecname doesn't immediately execute the power...

[/ QUOTE ] That's actually what I meant. My only fault was I didn't explain WHY it activates the last power in the chain. I was too busy trying to rationalize why the second to last power also get's queued, but that's because I was thinking ahead to the idea of using the "Powexec_Auto" command to queue the next to last power.

Also, using Toggles will activate more than one power at the end of the chain as well.

Thanks for clearing it up.

---

BOW DOWN BEFORE ME!

---

[ QUOTE ]
BOW DOWN BEFORE ME!

[/ QUOTE ] Hey, I was still right, I just didn't convey it completely. lol

*Bows anyway.

---

[ QUOTE ]
[ QUOTE ]
BOW DOWN BEFORE ME!

[/ QUOTE ] Hey, I was still right, I just didn't convey it completely. lol

*Bows anyway.

[/ QUOTE ]*bows down before both of you*

Thank you, oh masters of binding!

---

[ QUOTE ]
Also, you forgot powexecname soul extraction.

[/ QUOTE ]

I didn't forget it. I realized that the OP would want to wait to activate it until he actually got in range of the pet

---

[SIZE=1][COLOR=Yellow][U]Virtue Heroes (Serenity's Children):[/U] [B]@Eek a Mouse, The Devil's Mark, Outlaw Sniper, Gas-Soaked Rag Man, Amazon Prime, Friday's Child, Hot Blooded,[/B][B]Flower of the Moon[/B], [B]Rouge Demon Hunter[/B], Stimulated Emission, Animatronic Wench, [B]Lennie Small[/B]
[U]Virtue Villains (Serenity's Orphans):[/U][/COLOR][/SIZE][SIZE=1][COLOR=Yellow] [/COLOR][/SIZE] [SIZE=1][COLOR=Yellow] [B]Eek a Rat[/B], [B]Bomb Blondeshell[/B], Babe Brute, Jeanne Dark, Fallen Angle[/COLOR][/SIZE]

[ QUOTE ]
[ QUOTE ]
Also, you forgot powexecname soul extraction.

[/ QUOTE ]

I didn't forget it. I realized that the OP would want to wait to activate it until he actually got in range of the pet

[/ QUOTE ]If it's not in range, it'd simply queue the power... meaning it'd automatically activate once in range, when seemed to be the what the OP wanted (until he realized that the range of the power was long enough that he really wouldn't need the follow most always).

---

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Also, you forgot powexecname soul extraction.

[/ QUOTE ]

I didn't forget it. I realized that the OP would want to wait to activate it until he actually got in range of the pet

[/ QUOTE ]If it's not in range, it'd simply queue the power... meaning it'd automatically activate once in range, when seemed to be the what the OP wanted (until he realized that the range of the power was long enough that he really wouldn't need the follow most always).

[/ QUOTE ] This. TY.

---

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Also, you forgot powexecname soul extraction.

[/ QUOTE ]

I didn't forget it. I realized that the OP would want to wait to activate it until he actually got in range of the pet

[/ QUOTE ]If it's not in range, it'd simply queue the power... meaning it'd automatically activate once in range, when seemed to be the what the OP wanted (until he realized that the range of the power was long enough that he really wouldn't need the follow most always).

[/ QUOTE ] This. TY.

[/ QUOTE ]

My new alt.


And I prefer my 'TY's delivered in the form of bows. And ritual sacrifices. And no more orphans, please. I've already filled up on them.

---