Quote:
A frequent reason for a correctly typed bind to not work in-game is that the quotations in the bind that are copied into the game chat function are in Windows format, instead of plain text format. |
Originally Posted by Steel_Shaman
I've been setting up several binds for my warshade and found one that isn't working at all. I've looked it over and don't see anything wrong with it. I was hoping that someone knew a way to get it to function. The bind is:
/bind t "target_custom_next cyst$$target_custom_next quantum$$target_custom_next void$$target_enemy_next" My goal is to have it auto-target any quantum/void/cyst in a spawn, and if there is none there just target a regular enemy. Well, I've confirmed numerous times the bind simply doesn't work. I'm in game looking at a Galaxy Quantum right now and the bind just skips right over him. Any ideas for getting the keybind to behave itself? Thanks in advance for any tips! |
One of the possible cures is straightforward. Save your bind files as plain text files. Open them in a text editor (not MS Word), then copy & paste out of them into the game chat function. That way, you'll avoid Windows formatting issues, such as with quotation marks.
There may be more elegant solutions that others know about and that are more efficient. But, this is what I do and it will definitely prevent Windows formatting issues from messing up your binds.
Quote:
I'll give it a shot. Thanks!
|
Originally Posted by ShoeTattoo
A frequent reason for a correctly typed bind to not work in-game is that the quotations in the bind that are copied into the game chat function are in Windows format, instead of plain text format.
One of the possible cures is straightforward. Save your bind files as plain text files. Open them in a text editor (not MS Word), then copy & paste out of them into the game chat function. That way, you'll avoid Windows formatting issues, such as with quotation marks. There may be more elegant solutions that others know about and that are more efficient. But, this is what I do and it will definitely prevent Windows formatting issues from messing up your binds. |
Well I tried creating the bind in notepad, and just typing it out directly in the game. Neither one works. In fact, the behavior I'm seeing is the exact opposite of what is intended. The bind will let me cycle through targets with no issue at all, but it will not target a quantum/void, etc. It just skips right over them every time as if they are not there. Any ideas what could be causing that?
Your bind is backwards. The bind checks from right to left so you need your quantum/void binds to the right side.
Try something like this:
/bind t "target_enemy_next$$target_custom_next cyst$$target_custom_next quantum$$target_custom_next void"
If you want to avoid targeting dead quantums and voids try this:
/bind t "target_enemy_next$$target_custom_next enemy alive cyst$$target_custom_next enemy alive quantum$$target_custom_next enemy alive void"
Best regards,
Tommy Truestar
Quote:
Ah thank you! I didn't even think about that.
|
Originally Posted by Tommy_Truestar
Your bind is backwards. The bind checks from right to left so you need your quantum/void binds to the right side.
Try something like this: /bind t "target_enemy_next$$target_custom_next cyst$$target_custom_next quantum$$target_custom_next void" If you want to avoid targeting dead quantums and voids try this: /bind t "target_enemy_next$$target_custom_next enemy alive cyst$$target_custom_next enemy alive quantum$$target_custom_next enemy alive void" |
I've been setting up several binds for my warshade and found one that isn't working at all. I've looked it over and don't see anything wrong with it. I was hoping that someone knew a way to get it to function. The bind is:
/bind t "target_custom_next cyst$$target_custom_next quantum$$target_custom_next void$$target_enemy_next"
My goal is to have it auto-target any quantum/void/cyst in a spawn, and if there is none there just target a regular enemy. Well, I've confirmed numerous times the bind simply doesn't work. I'm in game looking at a Galaxy Quantum right now and the bind just skips right over him. Any ideas for getting the keybind to behave itself?
Thanks in advance for any tips!