Macro help please
Not exactly sure if this is what you want, but try this.
/bind LSHIFT "powexec_name_web_envelope $$ team $name is Grounded!!"
This may not work with the chat part secondary. If it doesn't work, try reversing the actions like this.
/bind LSHIFT "team $name is Grounded!! $$ powexec_name_web_envelope"
The basic idea is that whoever you have as your target will have their name displayed in place of the "$name". It should fire off the Web Envelop and if it's successful, the target will be "grounded". However, there is no way that I know of to make it only say "grounded" if it hits, so make sure it hits in combat.
Comic and Hero/Villain Culture
Saturday January 29th, 2005 (12:37 PM) ~ Monday August 9th, 2010
Those Who Lived It Will Remember Long after your Ban Hammer Crumbles and the servers flicker dead.
We Will Remember This One Moment In Time! ~ Shadow Ravenwolf
Quote:
the order of those commands should not matter, but you have an extra undercore in there. The command should be: powexec_name "Web Envelope", and it's recommended to quote your chat text as well, which would make the new command line:
/bind LSHIFT "powexec_name_web_envelope $$ team $name is Grounded!!"
This may not work with the chat part secondary. If it doesn't work, try reversing the actions like this. /bind LSHIFT "team $name is Grounded!! $$ powexec_name_web_envelope" |
/bind LSHIFT "powexec_name "Web Envelope"$$team "$name is Grounded!!""
Yes, the nested quotes work when used correctly, but I do admit they are not actually necessary. It's just an old programming habit of mine. lol
A "cleaner" command that still works is:
/bind LSHIFT "powexec_name Web Envelope$$team $name is Grounded!!"
Quote:
Its executing the web envelope and saying player is grounded. But the player it says is grounded is me. Its targeting me as $target.
the order of those commands should not matter, but you have an extra undercore in there. The command should be: powexec_name "Web Envelope", and it's recommended to quote your chat text as well, which would make the new command line:
/bind LSHIFT "powexec_name "Web Envelope"$$team "$name is Grounded!!"" Yes, the nested quotes work when used correctly, but I do admit they are not actually necessary. It's just an old programming habit of mine. lol A "cleaner" command that still works is: /bind LSHIFT "powexec_name Web Envelope$$team $name is Grounded!!" |
Quote:
Underscores don't matter in commands. IIRC, they don't even count towards the character limit.
the order of those commands should not matter, but you have an extra undercore in there. The command should be: powexec_name "Web Envelope", and it's recommended to quote your chat text as well, which would make the new command line:
/bind LSHIFT "powexec_name "Web Envelope"$$team "$name is Grounded!!"" Yes, the nested quotes work when used correctly, but I do admit they are not actually necessary. It's just an old programming habit of mine. lol A "cleaner" command that still works is: /bind LSHIFT "powexec_name Web Envelope$$team $name is Grounded!!" |
p_o_wex_e_cnam_e works just as powexec_name does, and so will pow_exec_name, powexecname, etc.
But it is useful to have them, in order to help with legibility for trouble shooting.
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Quote:
Underscores are for readability only. I personally use powexecname. p_o_w_e_x_e_c_n_a_m_e would also work.
the order of those commands should not matter, but you have an extra undercore in there. The command should be: powexec_name "Web Envelope", and it's recommended to quote your chat text as well, which would make the new command line:
/bind LSHIFT "powexec_name "Web Envelope"$$team "$name is Grounded!!"" Yes, the nested quotes work when used correctly, but I do admit they are not actually necessary. It's just an old programming habit of mine. lol A "cleaner" command that still works is: /bind LSHIFT "powexec_name Web Envelope$$team $name is Grounded!!" |
@Roderick
True, but the post he was talking about had an underscore in the POWER NAME. Therefore, it was incorrect.
It was posted as powexec_name_web_envelope
when that portion should have been powexec_name "web envelope".
As you indicated, it could also have been pow_exec_name or powexecname, etc.
It was posted as powexec_name_web_envelope
when that portion should have been powexec_name "web envelope".
As you indicated, it could also have been pow_exec_name or powexecname, etc.
Paragon City Search And Rescue
The Mentor Project
*pulls back from scope, loads new bullet, gets back into scope for next headshot* :P
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Quote:
Your right, my bad.
True, but the post he was talking about had an underscore in the POWER NAME. Therefore, it was incorrect.
It was posted as powexec_name_web_envelope when that portion should have been powexec_name "web envelope". As you indicated, it could also have been pow_exec_name or powexecname, etc. |
Orc&Pie No.53230 There is an orc, and somehow, he got a pie. And you are hungry.
www.repeat-offenders.net
Negaduck: I see you found the crumb. I knew you'd never notice the huge flag.
Quote:
Yeah, sorry...
Its executing the web envelope and saying player is grounded. But the player it says is grounded is me. Its targeting me as $target.
|
I was tired and working on a few binds myself last night.
Of course, with you being targeted for Grounding, it makes sense that I happen to be a shapeshifting villain in PI with the bind that I used $target on when I needed to use $name.
Comic and Hero/Villain Culture
Saturday January 29th, 2005 (12:37 PM) ~ Monday August 9th, 2010
Those Who Lived It Will Remember Long after your Ban Hammer Crumbles and the servers flicker dead.
We Will Remember This One Moment In Time! ~ Shadow Ravenwolf
Quote:
Nobody disputed that. I was fixing the fact that there were underscores through the entire command string, with no space between the command and the power.
Underscores are for readability only. I personally use powexecname. p_o_w_e_x_e_c_n_a_m_e would also work.
|
In fact, the power_name itself could have been listed as Web_Envelope instead, and it would still work just fine... but in the case of powers, the underscore can only replace the spaces, and not be inserted randomly. Either way, you still need to have the space after the command itself.
Quote:
Its executing the web envelope and saying player is grounded. But the player it says is grounded is me. Its targeting me as $target.
|
Quote:
Yeah, I somehow missed both the real erroneous underscore, and the other post saying the same thin I did.
Nobody disputed that. I was fixing the fact that there were underscores through the entire command string, with no space between the command and the power.
In fact, the power_name itself could have been listed as Web_Envelope instead, and it would still work just fine... but in the case of powers, the underscore can only replace the spaces, and not be inserted randomly. Either way, you still need to have the space after the command itself. |
Oops.
@Roderick
Im not so good with the macros. I need my left side shift key to do two actions. First villain side patron power web envelope. Second team chat targeting bind for pvp. Ie target player X saying something like "Player X is grounded".
Hope that makes sense and hope someone can help.