bind question...


all_hell

 

Posted

Is it possible to bind my 'x' key to do the following:

1st press of 'x': select teammate 1
2nd press of 'x': select teammate 2
3rd press of 'x': select teammate 3

and so, but it would come back to teammate 1 once it reaches the end of the team. And ideally it would somehow skip me, so for instance in the following team:

Joe
Bob
me
Marcy
June

it would do this:

1st press of 'x': select Joe
2nd press of 'x': select Bob
3rd press of 'x': select Marcy
4th press of 'x': select June
5th press of 'x': select Joe
6th press of 'x': select Bob

and so on


 

Posted

Yes, this is possible, but you need to do it as a rotating bind. This is somewhat more complex than a regular bind.

You need to open your City of Heroes directory on your computer and create eight text files, we'll call them Team1.txt thru Team8.txt and for the sake of the example we'll use the X key as the bind key. Substitute whatever you want for X.

Quote:
Open Team1.txt and type this:

X bindloadfile Team2.txt$$teamselect 1

Open Team2.txt and type this:

X bindloadfile Team3.txt$$teamselect 2

And so on and so forth until you get to Team8.txt, which should have this:

X bindloadfile Team1.txt$$teamselect 8

This creates a loop, as you can see. Then you just have to get the loop going by typing this in-game:

Quote:
/bindloadfile Team1.txt
This does not, however, skip you. Skipping you would only be possible if you teamed exclusively with the same people, as you could then set up the rotating bind to roll through their character names and not include your own. In the example above, if you always team with Marcy, Bob, Joe and June, you could set up targeting binds using the targetcustomnext command rather than the teamselect command, allowing you to target them by name.

Alternatively, you could skip yourself by leaving out the teamselect 1 command and always leading the team to assure you were always in the first position, but this could easily get to be more trouble than its worth (since even as leader, if you select someone else's mission you're not longer in position #1. It is probably simpler and more useful just to make the bind to target all eight spots and accept that you'll have to double-tap to get past yourself.


With great power comes great RTFM -- Lady Sadako
Iscariot's Guide to the Tri-Form Warshade, version 2.1
I'm sorry that math > your paranoid delusions, but them's the breaks -- Nethergoat
P.E.R.C. Rep for Liberty server

 

Posted

I totally know what you are going for here, because I was looking for the same thing at one time.

I did try the rotating bind, but as was mentioned, it does not automatically skip yourself. I know it would seem that since you technically *can't* select yourself the bind would just roll to the next file, but it doesn't.

The only thing that sorta works is "target_custom_next teammate". I have it bound to "Q". It will roll through the teammates, but not necessarily in the list order (1,2,3...). It is positional... it will select the next teammate nearest to you and work it's way to the teammate farthest from you. But it WILL go through the entire team roster.

.


Quote:
Don�t say things.
What you are stands over you the while, and thunders so that I cannot hear what you say to the contrary. - R.W. Emerson
The BIG consolidated LIST for BASE LUV
YUMMY Low-Hanging Fruit for BASE LUV

 

Posted

give yourself a reset bind to reset you to whatever spot in th sequence you want.

I use multiple binds so I can select teamates by number whenever I like.


 

Posted

Quote:
Originally Posted by Impish Kat View Post
The only thing that sorta works is "target_custom_next teammate". I have it bound to "Q". It will roll through the teammates, but not necessarily in the list order (1,2,3...). It is positional... it will select the next teammate nearest to you and work it's way to the teammate farthest from you. But it WILL go through the entire team roster.
Not only will it not go in order, but it wont guarantee to get all team members before starting over either. It kinda depends on if they are standing still or not. If you are doing it during combat and people are moving around, it's more than possible that Player6 will move closer to you and Player5 (while targeted) is moving farther away, resulting in Player6 being skipped until you "cycle" through again.

Also, that command requires the player to be in view, meaning if Player3 is standing behind you (off your screen), or behind a corner or object, they will be skipped as well, whereas the "teamselect #" commands will select the teammate regardless of their location (within the zone), allowing you to /face them or /follow closer to them if desired.


 

Posted

Quote:
Originally Posted by Master-Blade View Post
Not only will it not go in order, but it wont guarantee to get all team members before starting over either. It kinda depends on if they are standing still or not. If you are doing it during combat and people are moving around, it's more than possible that Player6 will move closer to you and Player5 (while targeted) is moving farther away, resulting in Player6 being skipped until you "cycle" through again.
hmmmm... I hadn't really noticed that, myself. Pro'lly because I tend to buff when the team is standing relatively still, and I'm usually set back a bit.

I agree though, that it has not been my ideal solution. I would *much* rather cycle through the roster in order (which I use the default shift + # to do).

.


Quote:
Don�t say things.
What you are stands over you the while, and thunders so that I cannot hear what you say to the contrary. - R.W. Emerson
The BIG consolidated LIST for BASE LUV
YUMMY Low-Hanging Fruit for BASE LUV

 

Posted

Quote:
Originally Posted by Impish Kat View Post
hmmmm... I hadn't really noticed that, myself. Pro'lly because I tend to buff when the team is standing relatively still, and I'm usually set back a bit.

I agree though, that it has not been my ideal solution. I would *much* rather cycle through the roster in order.

.
All of the "target next" (and "target prev") commands work the same way. It will select the next target based on the distance all visible valid targets are away from you. Whichever is "next" distance-wise after your current target will be chosen.

On a side note, this is also why some people think /target_enemy_next is broken. They don't always account for the fact that when you are still targeting a dead body from the last mob and move down the hallway, hitting /target_enemy_next might target a foe that is 2 mobs away instead of the ones directly in front of you... because distance-wise, that's what's "next". That's why it's good to clear your target or have target_enemy_near on a key to reset the distance as well.