Warlock Imp Bug, Mis-remembering or Working as Intended?

When I was leveling on the stress test yesterday, I noticed the action of the imp was not acting as I expected when set on Defensive mode. Now given that it’s been a while, it’s entirely possible that I’m mis-remembering how it worked.

The scenario:

-Imp set on defensive mode, with firebolt auto-cast set to on.
-Use Pet attack key to Start Imp attack
-Imp fires off one firebolt but then returns to passive at my side unless the imp or I is hit with an attack.
-If/When the imp or I was took damage then the imp would keep casting, otherwise I had to continue to press my pet attack key to keep him casting.

I do not remember ever having to keep pressing my pet attack key to keep the imp attacking until one of us took damage to keep him casting firebolt.

This was especially annoying in cases where I was trying to separate myself from the imp, have him start the attack to draw the MoB, and then for me to rip aggro off him to have the MoB come after me while I was some distance away to give myself more free casting time on a MoB. What I got Instead was my imp constantly running back to my side after he cast the first firebolt and the only way to keep him from doing that was to keep pressing the pet attack key, or flip him from defensive to aggressive.

This seems that it could be a fairly big issue for dungeons, if the imp doesn’t keep attacking on his own if the lock takes no damage so the player has to keep manually hitting the pet attack command to keep the imp casting. While not positive, I’m almost certain this was not how it worked.

In the brief period I had to try using my Voidwalker, I didn’t see this issue from having him set to Defensive. Once I sent him in to attack, he just kept attacking with no additional input, but then he’s melee so is getting hit almost immediately.

Pets should auto-attack when in defensive and the owner is struck, or when ordered to attack and keep going until they or the target is dead. If the pet is not attacking after you are hit or order the attack there is something going on there and should be reported.

Also noticed there is an LOS issue where the imp will not move into LOS to attack and will only attack if its already in LOS. Could be that’s just how it worked back in the day. I played a Warrior back then so I don’t know for sure.

Sounds like your imp went oom and coincidentally gained enough mana by the time you were attacked.

Unfortunately no,

This was starting the attack at full health/mana for both of us. One firebolt and he’d run back to passive state every time, unless I used the pet attack command again, he or I took damage, or I switched him to agressive.

I noticed this too yesterday. I’d select a mob (Nissa Agamand in this case) who was inside a house then I’d hide around the corner outside and command my Imp to initiate attack. The Imp just stood there and we both looked like idiots.

Yeah sounds odd. Did you report it or did they not have the bug report feature in the stress test?

did you double check that the auto firebolt thing was on? could it be that you were telling it to cast once and not to keep firing it?

I’m really curious if this is just how it worked back in Vanilla.

If there was a Bug report feature I did not see it but I didn’t think there was one. Yesterdays stress test was the first time I’ve ever participated in any type of Stress/PTR/BETA testing so I may have missed it.

I did check that, and it definitely showing that it was on autocast. Unfortunately I’m at work at the moment so I can’t go triple check it again.

It wasn’t as obvious as the last stress test, but if you go to the Help menu in-game there’s an option to report a bug.

I think it’s a bug. The VW will go to its enemy regardless of it being in LOS or not but the imp will only attack if it has LOS with its target.

I have nothing to really add except this:

Is it in his contract?

1 Like

Given his name was Nolrot I didn’t really trust him with anything. I’m rather glad I’m not keeping the stress test server character, I’d be really tempted to delete and re-roll just to get a different name. My VW isn’t much better.

Nah. It’s extremely obvious and starts out in the middle of your screen. You would have definitely noticed.

I imagine they probably didn’t want that for the stress test because they’re not looking for reportable bugs and instead just wanted to test layering and server tech under heavy loads.

I know that in some point in the game’s history (and maybe even in retail now), pet autoattack was disabled or inactive for very low level players (like maybe below level 10).

I believe the idea was/is that brand new players couldn’t be trusted to control their own pet. Or possibly it was to avoid some sort of exploit. You could not make your pet autoattack until you got to a certain level.

Yes, I thought about that.

That’s how it is on retail, or at least it was the last time I leveled a Warlock in retail. The pet attack command doesn’t work at all in that case until level ten, my imp in that case just starts his attacks when I do.

To be honest I couldn’t remember how it was going to work in 1.12 but the pet attack command was there and functional at level 5 when I got the imp. He just wasn’t functioning quite as I expected/“remembered” with having the control available.

How imp, blueberry, etc USED to work was that when they were on defensive, if the warlock (out of combat, not attacking anyone/thing) took damage, or the minion took damage then the minion would attack said attacker. If the warlock (out of combat) attacked a target the minion would also attack the target, if the warlock changed targets, the minion changed targets also.

Never had to put minion on aggressive in order to get it to attack anything. In fact, when you would put minion on aggressive they’d attack everything willynilly.

Never had to use Pet Attack command to make minion attack anything either.