I'm trying to put some text quotes while doing combat. I've done it successfully, but the game always recognizes the release of a button as another input (negative edge) and says the quote when the move ends. This is especially noticeable during maintains. Is there any way to control it so that the quote is only said at the beginning?
While I'm asking, is there any way to put a timer pause between commands? That could be useful for things like dramatic pauses and replies.
I read somewhere that all main commands must be the first command. That determines the on/off modifier, while the rest just happen. So I need it to be first
If you don't use the + notation, I don't think you get the double event. This does have the side effect of turning everything into a click power, though.
No, it's actually kinda useful for maintains, the power just stays on until its duration expires or it gets canceled in some other way. The basic way it works is:
"PowerTrayExec 1 n": will attempt to fully charge a charged power, or maintain a maintained power until the end of its duration. Will be canceled by anything that normally cancels something like that.
"PowerTrayExec 1 n $$ PowerTrayExec 0 n": will attempt to tap a charged or maintained power.
I'm trying to put some text quotes while doing combat. I've done it successfully, but the game always recognizes the release of a button as another input (negative edge) and says the quote when the move ends. This is especially noticeable during maintains. Is there any way to control it so that the quote is only said at the beginning?
While I'm asking, is there any way to put a timer pause between commands? That could be useful for things like dramatic pauses and replies.
OP, if you put +down1 at the beginning of the "command" part of a bind, it indicates it should be executed when the button is depressed. If you put +up1 it means to execute when the button is released.
Keep in mind that due to weird timing issues, both don't always execute when you press then release the key.
/bind <button1> +down1 <power tray icon1> $$ local firing at target
/bind <button1> +up1 <powertray icon1> $$ local reloading
I will activate a maintain, saying "firing at target" when I press it, and then say "reloading" when I let go. right?
I think you'd have to put both arguments into the same string in order for it to work, something like:
/bind button1 "+down1$$+powertrayexec 1$$local Firing at target!$$+up1$$local Reloading!"
Just one note about putting chat text into a bind - don't put it on a key you will be using a lot, as people around you will get very annoyed very quickly. If it's on a seldom used button, or if you're gonna do it while soloing, that's fine.
/bind <button1> +down1 <power tray icon1> $$ local firing at target
/bind <button1> +up1 <powertray icon1> $$ local reloading
I will activate a maintain, saying "firing at target" when I press it, and then say "reloading" when I let go. right?
No, it will cause you to fly upwards every time you hit button1 and say "reloading". up1 and down1 are just movement commands (or possibly null commands, there are a couple).
Just one note about putting chat text into a bind - don't put it on a key you will be using a lot, as people around you will get very annoyed very quickly. If it's on a seldom used button, or if you're gonna do it while soloing, that's fine.
That's the main reason I want to do it. Double quoting is quite annoying.
So, I'm stuck with turning maintains into toggles. Not so bad. I would have liked separate control for button press and negative edge input.
That's the main reason I want to do it. Double quoting is quite annoying.
So, I'm stuck with turning maintains into toggles. Not so bad. I would have liked separate control for button press and negative edge input.
I don't think you're understanding what I said about +down1 and +up1. They have to be in the same bind command, but the first makes part of the bind execute when you press the key down, and the second makes the other part of the bind execute when you release the key. They have nothing to do with movement.
Let's say I had shadow embrace in power slot 2
If I did:
/bind f "+down1$$+powertrayexec 1"
It would make pressing F down activate and maintain shadow embrace for as long as I held down the F key.
i just assumed the other poster that said up1 was the elevation/jump modifier and not the button press modifier was correct. I'll test it out then.
I think "up" or "down" are the commands for movement, but "+up1" and "+down1" are the button press commands. I use +down1 in many of my binds - it allows me to use a maintain power in a bind by making me hold down the button, then having the maintain stop if I let go of it.
Comments
example key "talkey thing$$ power thing"
"PowerTrayExec 1 n": will attempt to fully charge a charged power, or maintain a maintained power until the end of its duration. Will be canceled by anything that normally cancels something like that.
"PowerTrayExec 1 n $$ PowerTrayExec 0 n": will attempt to tap a charged or maintained power.
OP, if you put +down1 at the beginning of the "command" part of a bind, it indicates it should be executed when the button is depressed. If you put +up1 it means to execute when the button is released.
Keep in mind that due to weird timing issues, both don't always execute when you press then release the key.
/bind <button1> +down1 <power tray icon1> $$ local firing at target
/bind <button1> +up1 <powertray icon1> $$ local reloading
I will activate a maintain, saying "firing at target" when I press it, and then say "reloading" when I let go. right?
I think you'd have to put both arguments into the same string in order for it to work, something like:
/bind button1 "+down1$$+powertrayexec 1$$local Firing at target!$$+up1$$local Reloading!"
Just one note about putting chat text into a bind - don't put it on a key you will be using a lot, as people around you will get very annoyed very quickly. If it's on a seldom used button, or if you're gonna do it while soloing, that's fine.
That's the main reason I want to do it. Double quoting is quite annoying.
So, I'm stuck with turning maintains into toggles. Not so bad. I would have liked separate control for button press and negative edge input.
I don't think you're understanding what I said about +down1 and +up1. They have to be in the same bind command, but the first makes part of the bind execute when you press the key down, and the second makes the other part of the bind execute when you release the key. They have nothing to do with movement.
Let's say I had shadow embrace in power slot 2
If I did:
/bind f "+down1$$+powertrayexec 1"
It would make pressing F down activate and maintain shadow embrace for as long as I held down the F key.
I think "up" or "down" are the commands for movement, but "+up1" and "+down1" are the button press commands. I use +down1 in many of my binds - it allows me to use a maintain power in a bind by making me hold down the button, then having the maintain stop if I let go of it.
+down1$$+PowerTrayExec $$ (insert quote)) works the same as a quote with maintain. It says the quote upon button press and during negative edge.
+down1 $$ +PowerTrayExec $$ (insert quote) works the same as the quote with the maintain as well. Quote is given at button press and negative edge
+PowerTrayExec 1 1 $$ (insert quote) turns it into a toggle, says quote at beggining only.
Seems I can't get the up1 and down1 to work.
Let's say I have celestial conduit in tray Alt1, and I want to cast the power on myself as long as I hold down the F key. The bind I typically use is:
/bind f "+down1$$targetself$$+powertrayexec 7"
If I didn't include the +down1 it would try to fully maintain the power, instead of only doing so as long as I had the key depressed.
Hmm.. that is very interesting. Y'know, I have been using +down1 for so long, that I probably just didn't realize. Thanks for filling me in!
As an aside, are there commands that allow a bind to differentiate between when the key is pressed down, and when it is released?
Thanks again!