PTR 2.4.2: Focused Testing on Hunter UI/Kill Command

Hortus is looking for our help on the Public Test Realm!

We would like to request some focused testing on a bug that we believe to be fixed in 2.4.2

Using a macro with several instant cast spells can break targeting and the Escape key.

This is most often reported as happening with hunter kill command macros.

Please test your macros and report here if you encounter any of these UI lock-ups.

And please keep in mind (from further down the same thread):

Unless you are reporting test results from the PTR, there is no need to post here. We realize this bug is detrimental to people, which is why we’re trying to make sure it is fixed.

25 Comments

  1. joshua - April 28th, 2008 @ 9:07 pm UTC

    That is great news! Well, it looks to be great news anyway.

  2. shibumi - April 28th, 2008 @ 9:16 pm UTC

    not being much of a macro person, what kind of macro would you build for the kill command?

  3. Rainrider - April 28th, 2008 @ 9:35 pm UTC

    This is what I use

    #showtooltip
    /target [noharm] [dead] [noexists] pettarget
    /cast [target=pettarget] Kill Command

    It presents another bug too: using the macro ‘Kill Command’ gets cast even when the pet is not in melee range so it doesn’t land a hit and does no damage to it’s target. I still haven’t transfered my char to ptr, so I cannot confirm whether this is fixed.

  4. Rikaku - April 28th, 2008 @ 10:35 pm UTC

    I’m glad they finally made some comment about this. I use macros primarily in raiding, but I have been experincing this alot, and it causes ALOT of problems at times. I shall definitely go make a post. Thanks for the news Mania!

  5. shibumi - April 28th, 2008 @ 11:05 pm UTC

    thanks Rain – I suppose I should dig into macro life, it would probably hone my experience.

  6. marzix - April 28th, 2008 @ 11:09 pm UTC

    i do not use any macros. however, i had the problem of my kill command being “used” but not being used and it froze up. i could still arcane shot, steady, and those skills, but i wasnt auto-shooting until i got another kill command to activate and pet used it. then i was working fine.

  7. Kurasu - April 29th, 2008 @ 2:50 am UTC

    I’m with Marzix on this one: I don’t use many macros, and those I have been using don’t use actual attacks (a target/Hunter’s Mark for locating things is the main one). But I have ‘broken’ the escape key multiple times while doing my shot rotation and kill command, and it seems to ‘break’ the auto-shot at the same time this happens, locking auto-shot out and only allowing me to manually use attacks.

    I just add this in for the people who are on the PTR and might want to test spamming some attacks manually. And who might want to check and see if the ‘autofire locking up’ is linked with the escape key the way it so often is/was with me.

  8. sandralover - April 29th, 2008 @ 2:55 am UTC

    I did wonder if there was a bug but i only recently started using a macro and for me it stuck completely so i could not fire at all , ( at least i think i tried all my shots ? ) in the end i had to log to clear it, so i hope it is fixed …

  9. Kestrel - April 29th, 2008 @ 8:57 am UTC

    WoW…I can’t recall ever encountering this bug; or if I did, I certainly didn’t tie it to KC or Autoshot. Here are 2 macros I use, copied from my macro file:


    #showtooltip
    /castsequence Steady Shot, !Auto Shot, Arcane Shot
    /castrandom [target=pettarget,exists] Kill Command


    #showtooltip Kill Command
    /cast Kill Command
    /startattack

    While KC is in my rotation macro, I generally try to use the second macro as soon as I crit and KC is available, using the second macro. (Supposedly, the /startattack line is no longer needed, but I have had no problems with leaving it in.)

    I don’t have a character on the PTR (and I’m going to be traveling home from Illinois to South Dakota for the next 14 hours) so if someone wants to give either or both of my macros a shot (err…sorry about that :p), go for it!

  10. Zalthor - April 29th, 2008 @ 9:00 am UTC

    Wow, I thought it was just a glitch in my addons or something when that shooting problem happened (only thing I could think to blame it on). Im glad im not the only one. The only macro I have been using was Misdirection helper. It creates a Macro that replaces normal MD for you to click so you never have to click off your current target to throw MD on the tank.

  11. Sarayana - April 29th, 2008 @ 9:35 am UTC

    Zalthor, what is that macro? I’ve heard of it before, but not sure how it’s scripted.

    In general I don’t use macros and I find my 1:1 rotation with KC when I crit works well, no problems there. I also like having the option of throwing in stings depending on the target. However, I keep hearing about the 3:2 rotation being super useful but needing a macro?

    Obviously there are sometimes issues with macros, but it seems most raiding hunters prefer to use them, so perhaps you can share why and which?

    Thanks!!

  12. Zalthor - April 29th, 2008 @ 9:51 am UTC

    Sarayana, Im not sure how the macro is written, but MD helper is an addon i downloaded from Curse.com that puts a box on your screen. You either put your pets name in the box (for solo questing) or put the tanks name in the box and it automatically creates a MD button. Then when you click the new macro, itll automatically throw MD on the tank or your pet without having to click off your current target.

  13. Eric - April 29th, 2008 @ 10:40 am UTC

    These are the “norm” macros for kill command tied in with steady shot:

    1:1::
    #showtooltip
    /cast [target=pettarget] Kill Command
    /castsequence Steady Shot, !Auto Shot

    3:2::
    #showtooltip
    /cast !Auto Shot
    /cast [target=pettarget] Kill Command
    /cast Steady Shot

    And yes, they currently break randomly. I hope it’s fixed. :)

  14. Eric - April 29th, 2008 @ 10:41 am UTC

    Oops, I forgot to add in there the “exists” claus.
    /cast [target=pettarget, exists] Kill Command
    for both of them.

  15. Seidouyumi - April 29th, 2008 @ 12:10 pm UTC

    And people wonder why I don’t have macros. They’re scary.

  16. Kerub - April 29th, 2008 @ 1:33 pm UTC

    this 1:1 macro i use all the time when it gets stuck you have to use kill command on another target to get unstuck, before you can feed your pet, or do most anything else

  17. Vulpinor & Canopener - April 29th, 2008 @ 10:17 pm UTC

    Hey Mania,

    I know you’re asking for ptr testing but I’ve seen this same bug on my live server. I’ve been noticing that sometimes my kill command seems to get stuck on. I’m unable to feed Canopener or loot items. I also can’t feed my poor pet (who’s been with me since level 10) which caused me no small amount of distress. If this does happen, it gets reset when I exit the game and log in again. Hope that can help people who find themselves with a hungry pet.

    Vulpinor and Canopener

  18. Xota - April 30th, 2008 @ 6:48 am UTC

    Well yes, it does happen on Live Realms, but Hortus wants people to test it on the Public TEST Realsm, because they’re trying to fix it there. Also, most people have no addons on PTR.

    I’m not sure I entirely understand the big deal of the 3:2 macro, if it means you’re supposed to just hammer it and hope it only clips about one third of your autoshots? If that’s the case I’d rather just pay attention and get 1:1ish by not hammering, since my attack speed is fairly fast anyways.

    That being said, I use pretty much the same macro (with kill command attempting before every steady shot) on both live and test realm. It jams on live, but on test realm it seems to be working. I’ve even had the whole Crit->activate KC->target dies before KC procs happen, and without the jam. Very hopeful its actually working.

  19. Pike - April 30th, 2008 @ 10:48 am UTC

    Hmm. I get these bugs without using a macro, so it kind of worries me that they’re focusing on macros. But hopefully they’ve fixed it anyway!

  20. Xota - April 30th, 2008 @ 5:48 pm UTC

    As it has been stated, it happens most frequently with macros, so its most easily reproduced with macros, so its easiest to figure out what is wrong while using macros. But it should fix the problem with everyone.

    Seriously, if you are having this problem, copy a toon over to the PTR and try to reproduce it. Use macros, don’t use macros, just try to get it to happen and note the conditions under which you got KC to jam. Otherwise you’re not part of the solution.

  21. Palladiamors - April 30th, 2008 @ 6:21 pm UTC

    I don’t use macros, addons, nothing aside from the main game itself, and I have never encountered this, even when manually firing off things like a mad man. Could the problem be an addon, or are we positive its in the threading some where? Considering the seeming wide spreadness of it, I’d wager its in the threading, but does that make it a macro problem, or something in the system? We’ll take the system route for now, since people have commented that even non-macro they see this. Can anyone remember if this problem happened immediately, or after several times of using the macro? Is it prolonged usage, or is it just a fluke that occasionally causes the system to crap on itself? Is kill command what causes it to freeze, or is it just the macro rotation itself?

    Sarayana, its far from impossible or even hard to do a 3:2 manually. The only time I could see it being a pain would be during rapid fire, and then its just because you really have to be on the ball. Its a matter of timing, and if you know what to look or ‘feel’ for, rythm. 1:1s bug me, sorry everyone who uses that particular rotation. I just don’t feel like your maximizing your DPS output. Its not that hard to thread in arcane, multi, and steady with kill command as long as your paying attention. The only ‘problem’ is mana, and viper helps with that, if you don’t mind the loss in DPS. I know a lot of people do, but if losing what, ten or so DPS lets me keep pelting things with shots and KCs, then thats good by me. Though on longer boss fights I do have to keep potions around. Just my two cents.

  22. Allisera - May 1st, 2008 @ 8:28 pm UTC

    I tend to link abilities and trinkets to my shots, in macros, such that I don’t have to worry about keeping them up, and can instead focus on my shot ratio. I had to take Kill Command out because of this bug – not because Macros were the sole cause, but rather, because including it in a macro was more likely to trigger it.

    Personally, I use a 1:1 ratio, with 1 arcane shot and 2 steady shots. I came to the conclusion that this was the most efficient for me after several bouts of testing with a damage meter. Yes, with a much higher (ie slower) speed, you will have more time to weave in that multi-shot or sting. However, the extra damage done comes at the expense of other damage. In approximately 6 seconds, I’m getting 3 autoshots, 2 steady shots, and 1 arcane shot. Contrast this to what an average 3:2 ratio would get – effectively 2 autoshots, 2 steady shots, and 1 arcane shot. Now, if you’re at a slower speed, that’s what’s best for you, because you won’t be able to get in 3 autoshots in 6 seconds. It depends on spec and gear.

  23. Elaith - May 1st, 2008 @ 11:56 pm UTC

    I dont use macro’s either… and this kill command bug is my bane!
    when it gets stuck there goes my autoshot and dps.
    The quckest way to “fix” it is to run into melee range and spam wingclip until i get another crit, enabling the killcommand which then allows me to use and clear it.
    Im BM and i use the std auto-steady 1:1 rotation.

  24. Never - May 7th, 2008 @ 10:12 am UTC

    and here i thought i was the only one with this happening since no other hunter in my guild gets it. i have found that when the autoshot/esc key freeze up thing happens (which also doesnt let me feed my pet either oddly enough) if i run up to the next mob being attacked and kill it melee everything usually goes back to normal once the mob dies.

  25. Yoshii - May 9th, 2008 @ 7:28 am UTC

    THis is the macro i use

    #showtooltip Steady Shot
    /script UIErrorsFrame:Hide()
    /castsequence reset=3 Steady Shot, !Auto Shot
    /cast [exists,target=pettarget] Kill Command
    /script UIErrorsFrame:Clear(); UIErrorsFrame:Show(

    i have had that problem many many times. and i thought it was my computer screwing up.

    but yes my escape key would “break” and my auto-shot would epic fail, only allowing me to manually cast spells/

    glad to see Blizzard finally wants to fix this

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Note: This post is over 2 years old. You may want to check later in this blog to see if there is new information relevant to your comment.