Sure. Don't do that. As this thread has stated many times, there is no single, all encompassing shot macro that works for any spec in WotLK. Move on or re-roll.
Specifically your problem is that you're trying to fire Black Arrow while it's on CD and the macro will not progress past that point until BA is OFF CD.
I am looking for a basic macro to ease the strain a little I am looking for it to cast auto Shot, Steady Shot, Explosive Shot, And Kill Shot. I have one now that sorta works:
Sure. Don't do that. As this thread has stated many times, there is no single, all encompassing shot macro that works for any spec in WotLK. Move on or re-roll.
Specifically your problem is that you're trying to fire Black Arrow while it's on CD and the macro will not progress past that point until BA is OFF CD.
Read Iru's post above and get out of the mindset that you can have a one button mash macro!
I am looking for a basic macro to ease the strain a little I am looking for it to cast auto Shot, Steady Shot, Explosive Shot, And Kill Shot. I have one now that sorta works:
Is there any way to make this more efficient. I like this setup because it allows me to get off my basic shots while threading in others
What other shots? You have serpent sting and aimed shot. That macro will massacre your DPS. The time of macros being an efficient DPS tool have ended, and should never have started.
Hello all. I am trying to determine if there is a way to set a macro to target a mob that is marked by an in-game mark (eg, skull, x, diamond, whatever). I have tried (eg) /target skull, /target 'skull', etc. but can't find anything that works. Does anyone know if this is possible, and if so what command would work. My thanks in advance for your time.
First, Is there a way with in a macro to tell it to wait for the GCD time period before attempting to cast the next item in the macro?
Second, I see several modifires to macros for the use of ctrl, alt, Shift, and others, this apprears to defeate the purpose of the macro which is to hold a ridgid schedule of output and compile abilities to reduce the amout of keys needed to be hit. Am I incorrect in this?
Third, is there a way to set macros to make "buff/debuff" checks as to wether or not to cast the spell or ability? (i.e. only fire x ability if y is present/missing)
Macros can never "wait". They try to do everything within them at once. That is why you cannot have more than one GCD-inducing ability in a macro -- unless you have conditionals so that the macro isn't trying to do both at once (like it casts one when you hold down shift, and the other if you don't).
The purpose of macros as Blizzard sees it isn't to make it possible for you to mash one key and win the game. That is why they have limited what macros can do. Macros can help make hitting the keys you need to easier or more intuitive to a degree, but that's about it.
And lastly, it actually did used to be possible to detect buffs and debuffs in macros and cast abilities according to that, but they removed that with 2.0 for the above reason. In other words, learn to watch Serpent Sting yourself.
Originally Posted by jimavet
Hello all. I am trying to determine if there is a way to set a macro to target a mob that is marked by an in-game mark (eg, skull, x, diamond, whatever). I have tried (eg) /target skull, /target 'skull', etc. but can't find anything that works. Does anyone know if this is possible, and if so what command would work. My thanks in advance for your time.
It is possible to set a target's icon via a macro, but not to target a target by its icon. Your best bet (if you're having trouble doing it yourself) is depending on someone on a tank list such as the one provided by CTRaid, oRA, or other mods.
It is possible to set a target's icon via a macro, but not to target a target by its icon. Your best bet (if you're having trouble doing it yourself) is depending on someone on a tank list such as the one provided by CTRaid, oRA, or other mods.
I can actually mark very quickly (comes from having 3 80 tank alts, and be very organized ;-) But in some of the Uldaman fights there is can be a ton of mobs up and it would be helpful for people to be able to quickly macro-target a mob that has had a skull-mark placed on it, when the marking person is forced to switch targets quickly after marking the mob with a skull. Oh well - thanks for your input.
I can actually mark very quickly (comes from having 3 80 tank alts, and be very organized ;-) But in some of the Uldaman fights there is can be a ton of mobs up and it would be helpful for people to be able to quickly macro-target a mob that has had a skull-mark placed on it, when the marking person is forced to switch targets quickly after marking the mob with a skull. Oh well - thanks for your input.
Wouldn't this be solved with someone assigned as "Main Assist", so he can target the next mob and everybody gets their target from him.
I know what i do is pull out my rogue buddy and drop him right next to my pet's buttons and from their if there's an add situation such as in the the VoA boss that requires ya move to a specific add and slaughter it with a quickness. In this situation a get a raid warning saying hey dummy switch targets before ya blow up. I simply double click on my rogue friend and then switch to his target. In the event that my rogue buddy has taken a premature dirt nap I have my tanks pulled out next to my bars on the right (i have tanks pulled out for MD). Melee are a great resource for those fast target switches. Abuse the fact that they are in the face of mobs and their for can navigate through a group and onto "the right mob".
Wouldn't this be solved with someone assigned as "Main Assist", so he can target the next mob and everybody gets their target from him.
Example: /assist "Tank Name/Main Assist Name/Focus"
Yes, that works fine... with the only drawback being that the Main Assist person still needs to "find the mob" and then mark it (which can get difficult at times when there is a very large group of mobs running around confusing everything). My original question came from thinking that Deadly Boss Mods (and I presume other mods) can assign marks. Targeting marked mobs would then be easier for people to find the mob or person in question (because the mark was applied by the mod). I routinely use macros to assist focus targets and specific people or creatures... but others in the raid may be less adept at using macros, but more importantly even for me it can take me a while to tab-target the right mob and then mark it. End result - doesn't seem like there is a way to macro targeting of a marked mob/person based on the mark they have, which defeats the whole idea I had come up with in the first place. Moving on to other topics of interest...... ;-P
I'm not sure why this isn't working like it did in TBC, but I'm trying to get a wind serpent to stand next to me and do nothing but cast Lightning Breath at my target. However, when I put the pet on Stay, Passive, and take auto-cast off all their abilities, the pet still goes in and attack after the first Lightning Breath. Anyone know if this is bugged?
As I am not a good macro making person, I was just wondering if this is indeed correct. I have tried it and it seems to work ok.
Comments?
Both macros are the same. Did you make a copy-paste error?
Originally Posted by Sindroth
I'm not sure why this isn't working like it did in TBC, but I'm trying to get a wind serpent to stand next to me and do nothing but cast Lightning Breath at my target. However, when I put the pet on Stay, Passive, and take auto-cast off all their abilities, the pet still goes in and attack after the first Lightning Breath. Anyone know if this is bugged?
Nope, it's not. Telling a pet to use a damaging ability on a target sends it to attack. It's an AI change.
I have gone ahead and tried the macro but I still can not seem to be able to do a modifier to the /petattack command.
It's a simple macro, reads as follows:
/cast Hunter's Mark
/petattack [mod:shift]
I am starting to think that, perhaps either I have the order wrong or something like that, or you just can't modify /petattack.
The order on that looks fine. You're not casting something else bound explicitly to key+shift, are you? Somewhat workaround-ish, but
/cast Hunter's Mark
/stopmacro [nomod:shift]
/petattack
might work. Essentially, unless you're holding shift, it stops before telling the pet to attack (yeah, it the conditional is a bit wierd here, but it should work).
/petattack does not take conditionals, as far as I know, only options. A couple of things will probably do what you want.
This will cast Hunter's Mark and tell your pet to attack with any modifier:
/cast Hunter's Mark
/stopmacro [nomod]
/petattack
Alternatively, if you want the pet to attack only on shift:
/cast Hunter's Mark
/stopmacro [nomod:shift]
/petattack
This will cast Hunter's Mark and tell your pet to attack your target, if your target is an enemy. Will not send pet to attack if you do not have a target, will not produce error messages if targetting a friendly.
/cast Hunter's Mark
/petattack [target=target, exists, harm]
Look, Lactose, we'd rather you didn't eradicate the whole human race.
- Sam & Max
But now, I have to manually weave my Kill shot in. Anyone see the issue with it? I know I'll probably get a warning for asking for help as I have before, but I'd really like to see it working again, and I'm sure some others would enjoy not hearing the noise spam as well (haven't see the sound off in a macro in this thread yet).
I'm not sure that Steady Shot is your problem; I think it's the spamming that's getting you in trouble.
Around 2.4 Blizzard changed macros to be server side rather than client side as they had been and at the same time implemented a short queue on the key presses so that classes who needed to spam an ability were no longer penalised by latency etc. A consequence of this was that people were supposed to no longer need /stopcasting in their macros because the client side execution and related intra macro latency no longer existed.
/stopcasting still works on long duration spells because you haven't filled the queue with additional commands so the /stopcasting is seen as soon as you invoke it. When spamming, you have additional unprocessed actions in the queue ahead of the /stopcasting so you get no result.
This seems a fairly plausible diagnosis actually, since a lot of the problem steady shots seem to "start on their own", several tenths of a second after I last pressed steadyshot, which would indicate the queue being in effect.
The earlier suggestion to just have two /stopcasting before the kill shot worked great though And I only have it on Kill Shot, which I only press when it's definitely usable, so no steadyshots are being cancelled unnecessarily (which they probably would be if I had it on ES as well).
04/29/09, 7:03 AM
And I only have it on Kill Shot, which I only press when it's definitely usable, so no steadyshots are being cancelled unnecessarily (which they probably would be if I had it on ES as well).
Similar Threads
