/petpassive and /petdefensive work but /petaggressive doesn’t. Clear discrepancy. Clearly a bug.
3 Likes
wowwiki shows the pet commands, and /petaggressive as well as /petstay appear to have been removed.
The following should all work:
/petattack
/petfollow
/petmoveto
/petassist
/petdefensive
/petpassive
What patch were they removed?
It works. Are you mistaking the way it functions with the way retail assist functions? The pet will basically just agro like any aggressive mob would onto enemies that are within its agro radius.
I’m sitting here on a hunter typing in the above macros. aggressive does not work. the others change accordingly.
Seriously, why even lie about this.
1 Like
Oh your talking about the actual macro command? The toggle on the pet bar is what I was referring to, which does function.
I see sometime in 2011 pet aggressive stance was removed from the game entirely and replaced with some assist thing. The Wiki referred to posted the removal of /petaggressive in 2013, likely after the change in 2011. WoW classic is based on a patch from 2006. Is there any indication that /petaggressive should not be functioning?
2 Likes
Can confirm the command /petaggressive isn’t functioning and /petpassive /petdefensive are.
If you consider “The client is based on a fork of the 7.3.5 Legion client - seems this was updated to a fork of 8.0” to be an indication, then yes.
Sooo…it’s broken and thus a bug because their starting point was based on a time after 1.12 and the change was never reverted you’re saying?
2 Likes
Nope. That is not what I’m saying. I won’t quote myself though, as my comments are not very far above, and are still clearly visible.
EDIT: Just to be clear here, because you seem to be looking for some sort of confirmation that something which is clearly, and obviously not a bug is agreed upon by others as being a bug. The macro system is the same as modern Retail WoW, and not the macro system from Vanilla.
Whether you like that or not, or whether I like that or not isn’t of particular interest. We have the system that we have. Feel free to file a bug report. Feel free to even include that “Elite said” in that bug report, but that’s not what I’m saying. I do not believe this to be a bug. I believe this to be working as intended.
If they’re using retail’s macro system, then that’s definitely a change. Also, if /petaggressive was removed specifically because it doesnt exist in retail, that also doesn’t make any sense to include that removal in a version of the game that still has pet aggressive stance. This is why you don’t cherry pick things to keep and port over from retail.
2 Likes
Oh yeah, you won’t get any disagreement from me on that. In fact, I think it is the single biggest change, and a massively game-breaking change, that I am shocked people are not incredibly noisy about on the forums.
However, other that this very calm and simple post asking about it here by you, I haven’t heard anything about it really.
People are plenty noisy on the forums about hunter bugs, just not this one. I think it’s safe to say the problem that spell batching is causing with putting traps up after feign death is clearly the focus of hunter complaints at the moment. If Bliz doesn’t fix that, I honestly don’t believe it matters what else is broken about hunters, and trust me there is a long laundry list. I don’t think it’s commonplace for people to macro putting pets on aggressive anyway. But I agree this is definitely a bug. If it’s something that was changed for a future expansion and not reverted back to how it was in classic, it’s most definitely considered a bug. Similar to the discombobulator ray not dismounting people anymore.
1 Like
I’d be more inclined to say it’s more then likely an oversight. Not something that is working as intended so it should be included into the macro system.
If we were going with your logic macroing any ability that existed in vanilla but no longer exists in retail should also not work with the classic macro system, which isn’t the case.
I agree unfortunately there is so many bugs a lot are getting lost in the noise. With the speed at which these bugs are being dealt with I have little hope of these smaller bugs getting any attention.
I’m not suggesting that nothing whatsoever that worked in Vanilla works in the modern Retail macro system, if that is what you are saying. There is definitely some overlap, however there are also a lot of differences.
Here’s a video, specifically for hunters to convert macros used in Vanilla to Classic, for your viewing pleasure:
Certainly. However, how much noise has been made about the entire macro system being that of Retail WoW, and not that of Vanilla WoW?
While using the modern macro system is definitely not a bug, it is an enormous change, and not many people are saying much, from what I’ve seen. It’s surprising to me that what I see as a major change isn’t seen as such by many. Perhaps a lot of the noisy people just don’t or haven’t made macros.
Personally, I’m not unhappy either way, and am not “making noise” about it either. If I had to choose, I’d go with #nochanges and use the original macro system, but Blizzard didn’t knock on my door and ask me personally to consult for the launch of Classic, to nobody’s surprise, I’m sure 
Can’t figure out if this is a troll or not. I tested petaggressive A LOT in beta. It is my favorite stance when dueling rogues. I also have used this on live and it is WAI.
When testing this in dueling scenarios, In both beta and live Classic, I Shadow Melded and put pet into Prowl with the pet’s stance set to aggressive. The vast majority of the time my pet would sense/detect the stealhed player and attack even before I could see the player. The only time this didn’t work is when a speed ability was activated by the stealthed player.
It is pointless to argue semantics, but since you insist; Clearly they have re-implemented some pet macros that they had otherwise removed from retail to now work again the way they did in vanilla. Them remembering to re-implement only 2 out of the 3 macros from vanilla, while being an oversight, is considered a bug simply because one not working. Now, please go away.
1 Like