I've had vanish failing on mobs when I was pulled out of stealth instantly, by either melee swings or spells. I can imagine that you could have been hit by a dot tick, causing your vanish to fail before the threat table was updated.
I doubt this is a bug or even unintentional. When you buy a 264 with a 251 and the token, I'd guess that the original 251 item is forgotten completely (*), including anything unique about it (enchants, gems, and, in this case, its not-yet-expired refund timer). When you refund the 264, you're getting a new 251 back, not the same one you turned in. It won't have a refund timer anymore since it's a newly created item which wasn't freshly bought.
This has actually been the case with the tokens from previous tiers also. It's not a new issue with tier 10, and as such I'd think it's unlikely to be changed.
If you purchase the older tier set tokens with badges (T7 hands/chest, T7.5 legs/shoulders, T8.5 head/chest), redeemed the token for a piece of tier armor, then decided you actually wanted to use the badges back, you'd have the same problem.
You can redeem the armor for the token, but the token can not then be exchanged for the badges.
The explanation above does sound like the correct reasoning.
I was wondering if anyone else had this problem. After being bone spiked and freed on Lord Marrowgar, my toon stops auto-attacking. Vanish usually fixes this though. Has anyone else noted similar behavior?
I was wondering if anyone else had this problem. After being bone spiked and freed on Lord Marrowgar, my toon stops auto-attacking. Vanish usually fixes this though. Has anyone else noted similar behavior?
I have had this happen. I had the same thing happen back in Ulduar, when I would get Slag Potted. An easier fix is to simply deselect the boss while spiked or potted, and just resume attacking afterwards.
I was wondering if anyone else had this problem. After being bone spiked and freed on Lord Marrowgar, my toon stops auto-attacking. Vanish usually fixes this though. Has anyone else noted similar behavior?
ye, it was also the same on Ignis Slag pots. All you have to do to fix it from my experience is drop target and retarget again and auto attacks should work.
Last night during ICC25, I noticed my character was not auto-attacking. If I hit mutilate or envenom, it would do that specific ability, but would not auto-attack. My guild thought I was retarded, and thought that my macro was incorrect. I have however, used the standard macro that most rogues use, and have had that same macro for, well, since vanilla. I relogged, and the same thing happened a few times throughout the night. So I figured, I probably had a mod that was causing me to stop auto-attacking. One thing I did notice, was that my character would still be in the normal battle stance when you turn on auto-attack. It just would not attack with white attacks.
Today, playing from my laptop, which has 0 mods on it, I noticed the same problem while doing the daily 5man Heroic. This time it was while I was combat and using my Sinister Strike macro I have also had for years. Again, the character was in battle stance ready to attack, and just simply did nothing till I could use Sinister Strike again.
I have googled this dilemma, as well as searched the forums to no avail. My question is, has anyone had this occur? If so, is it a fix on the user end or do we need to report it on the bug forums?
*edit* It appears someone else above me had the same issue. However mine was not just on Marrowgar, and like another user posted, I had to drop target, and retarget the mob to autoattack again. Gonna check over the Bug forum one more time on the official website, and then make a post.
I don't understand what you use those macros for. If you're not aleady autoattacking, casting SS or Mutilate turns on your auto-attack automatically. Am I missing something terribly obvious here?
I don't understand what you use those macros for. If you're not aleady autoattacking, casting SS or Mutilate turns on your auto-attack automatically. Am I missing something terribly obvious here?
It doesn't if you don't have enough energy to perform the ability.
The startattack macros trigger your autoattack even when you don't have the energy to do your CP builder. The one thing I'm not sure on, looking at your macros, is the order. Have you tried switching lines two and three?
The startattack macros trigger your autoattack even when you don't have the energy to do your CP builder. The one thing I'm not sure on, looking at your macros, is the order. Have you tried switching lines two and three?
Yeah, in those macros, they will fail and stop at SS/Mut if you don't have enough energy, negating the whole purpose. I do not think the macros are your problem, I think it has more to do with auto-attack not re-engaging properly after stuns and similar mechanics that force you to stop attacking. De-targeting forces an auto-attack rest it would seem.
The startattack macros trigger your autoattack even when you don't have the energy to do your CP builder. The one thing I'm not sure on, looking at your macros, is the order. Have you tried switching lines two and three?
These macros let you bind the Auto-attack ability and your primary combo point builder to one button. The benefit is that on fights like say Professor Putricide, when you switch to the oozes, if you don't have enough energy built up for a mutilate or a sinister strike, this will engage your auto-attack. If you only use the ability itself (SS/Mut), then you may not start auto-attacking until you have the energy to actually cast the spell which triggers SS/Mut/Whatever. Basically these macros allow you to have maximum up time without getting stuck without auto-attack on occasionally due to energy starving.
The macro actually works even if I am out of energy for a Mutilate or Sinister Strike, it still triggers the Auto Attack and has for a long time previously. I will also switch the /startattack command position just for the sake of argument.
Yeah, in those macros, they will fail and stop at SS/Mut if you don't have enough energy, negating the whole purpose. I do not think the macros are your problem, I think it has more to do with auto-attack not re-engaging properly after stuns and similar mechanics that force you to stop attacking. De-targeting forces an auto-attack rest it would seem.
It seems to me that it would be considered a bugged mechanic if you can no longer auto attack after being a target of an ability without physically removing said target and reapplying it as your target.
It seems to me that it would be considered a bugged mechanic if you can no longer auto attack after being a target of an ability without physically removing said target and reapplying it as your target.
For the record, I've had this occur several times on marrowgar after being spiked. I've just gotten in the habit of clearing and retargeting him after being spiked. I use a similar macro so it may even be related to trying to /startattack while stunned/incapacitated/whatever?
Yes, this has been occuring since Ignis back in ulduar. Whenever he chose me as the pot and removed me from physically attacking him, my auto-attack would stop even after I was freed from the pot. The only fix that i know of is you have to deselect your target and then select him again and it will start auto-attacking once again. It's buggy as hell and it's annoying.
Now that I think about it this is probably what was causing me problems getting my white hits to work when we first started doing Kologarn. I eventually fixed it by just switching targets and running around a bit when I wasn't white hitting until I started swinging again.
Last night during ICC25, I noticed my character was not auto-attacking. If I hit mutilate or envenom, it would do that specific ability, but would not auto-attack. My guild thought I was retarded, and thought that my macro was incorrect. I have however, used the standard macro that most rogues use, and have had that same macro for, well, since vanilla. I relogged, and the same thing happened a few times throughout the night. So I figured, I probably had a mod that was causing me to stop auto-attacking. One thing I did notice, was that my character would still be in the normal battle stance when you turn on auto-attack. It just would not attack with white attacks.
Today, playing from my laptop, which has 0 mods on it, I noticed the same problem while doing the daily 5man Heroic. This time it was while I was combat and using my Sinister Strike macro I have also had for years. Again, the character was in battle stance ready to attack, and just simply did nothing till I could use Sinister Strike again.
I have googled this dilemma, as well as searched the forums to no avail. My question is, has anyone had this occur? If so, is it a fix on the user end or do we need to report it on the bug forums?
*edit* It appears someone else above me had the same issue. However mine was not just on Marrowgar, and like another user posted, I had to drop target, and retarget the mob to autoattack again. Gonna check over the Bug forum one more time on the official website, and then make a post.
Seems like those macros are backwards. You have to put the /startattack before the /cast.
I don't know if this is rogue-specific, but I was having issues attacking on Putricide last night. Not just autoattack, but attacking at all, I'd have Putricide targetted, I'd be in range (in frustration I'd be inside his actual model just to be sure), and hit SS and nothing would happen. Deselect him, retarget, right click on him, hit SS, and nothing, no auto attacks and no SS attack. Not even a warning message for out of range or anything. Killing spree would work, and I'd be able to attack for a while, but then I'd switch targets and wouldn't be able to attack at all again. I'd had no problems on trash just before him.
The only difference was I had used one of the new Perfume/Cologne items from the holiday event. They give 75 AP that stacks with everything. However, it seems they caused me to bug out and not be able to attack at all. It might be related to the 3% crit buff you get if there is a cologne and perfume in the raid, I recall having a heart above my head at the time.
Does anyone else have experience with this bug? There were several raid members using these items, and other complained of issues with attacking, and we most of us stopped using them.
Oh yes, the perfume/cologne seems to screw melee out of being able to attack. One"fix" I found was to click off the perfume, attack, then reapply. Simply do not Vanish or stop auto-attacking, because it will bug you out again.
One thing I noticed last night and sunday night, was on Sindrigosa, after pulling the last dragon trash, you get feared. After that fear was finished, I could not auto attack. It said "you cannot attack while fleeing". the only way i found to fix this was ... Le sigh.. to stand in front of the trash, and get cleaved so that I could die, then get rezzed. If i didn't die, it would not reset
One thing I noticed last night and sunday night, was on Sindrigosa, after pulling the last dragon trash, you get feared. After that fear was finished, I could not auto attack. It said "you cannot attack while fleeing". the only way i found to fix this was ... Le sigh.. to stand in front of the trash, and get cleaved so that I could die, then get rezzed. If i didn't die, it would not reset
Tried vanish? Has worked for me in other similiar situations
Until now two times my Tricks-Cooldown bugged. There was no cooldown-timer on my tricks spell and trying to use the spell wow prompted "This spell isn't ready yet.". All of this while hitting an mob and building up aggro.
The first time was in TotGC10 sometime in or after fighting the faction champions. I don't know when exactly. I realized i couldn't use tricks after pulling the twin Valkyrs and realizing I'm just over the tank.
Second time was yesterday fighting the trash in ICC. We just killed a Valkyr and were going to pull the first trash visiting the dragon woman. Tricks defiitely worked on the Valkyr and didn't work the Pull after.
Both times I already had the T10 2Piece Bonus.
Anyone encountered this error or even better has an Idea how to evade it? Trash or TotGC is not such a biggie but I don't want to screw up a hardmode-Try because of this.
Edit: I forgot to mention: Relog fixed this problem for me (Character Screen). I can't remember if I died in TotGC but I think I survived the Bug and relogged after the Kill.
So if this doesn't have to do anything with T10 (refering to the poster below) maybe it has something to do with the Tricks-Glyph. Any combat rogues (with/without the glyph) also got this?
Until now two times my Tricks-Cooldown bugged. There was no cooldown-timer on my tricks spell and trying to use the spell wow prompted "This spell isn't ready yet.". All of this while hitting an mob and building up aggro.
The first time was in TotGC10 sometime in or after fighting the faction champions. I don't know when exactly. I realized i couldn't use tricks after pulling the twin Valkyrs and realizing I'm just over the tank.
Second time was yesterday fighting the trash in ICC. We just killed a Valkyr and were going to pull the first trash visiting the dragon woman. Tricks defiitely worked on the Valkyr and didn't work the Pull after.
Both times I already had the T10 2Piece Bonus.
Anyone encountered this error or even better has an Idea how to evade it? Trash or TotGC is not such a biggie but I don't want to screw up a hardmode-Try because of this.
No idea how to avoid this, but dying fixed it for me. I have only seen this happen to me once since 3.3.2 was released, notably in the Frostwing Halls (realized it was bugged about half way through Valithria trash). I was also muti specced with tott glyphed at the time, running with the 2pc T10 bonus as well. Not sure how much any of this is related, but it's a start.
01/29/10, 11:21 AM
Similar Threads
