[BUG] Sending pet towards enemy player doesn't makes you immune to sap

exythxx commented 2 years ago

1. Current Behavior

1.1. Description

If you send pet to attack enemy players, you can get sapped.

1.2. How to Reproduce

       1. enter arena against rogue
       2. command pet to attack (/petattack, or CTRL+F1)
       3. observe combat state (should be out of combat)
       4. attempt to have rogue cast sap (should be immune)

1.3 Source Material

not atm

2. Expected Behavior

2.1. Description

"When a player sends pet (/petattack) at a visible enemy, the player should be immune to sap but not enter a "combat" state, if pet is recalled (/petfollow, /petpassive) or pet loses target (Feign Death, Vanish, Shadowmeld), player should be immediately sappable"

2.2 Source Material

https://www.youtube.com/watch?v=paskamMBWZ0&ab_channel=WoWVideoArchive 22:08 and 30:51

chanbetatestwow commented 2 years ago

This is also occuring intermittently with Warlock pets

hillerstorm commented 2 years ago

Duplicate of https://github.com/JamminL/wotlk-classic-bugs/issues/58 ? NAB

Evolvee commented 2 years ago

Pet & Combat mechanics are notoriously completely broken on Classic and boost the pet classes extremely.

The fact that they intentionally keep this in the game https://github.com/JamminL/wotlk-classic-bugs/issues/68 speaks volumes. I hope I dont even have to mention the "stealth/invisible" combat state aka "cant sap me" exploit while being able to happily mount up and jump around.

Another great bug/exploit is that you simply NEVER DROP combat if you have a pet. Lets say you are a hunter and you get AOE feared alongside your pet for 10 seconds, nothing touches you, yet after 10 seconds of you and your pet being feared together, you and your pet are both still in a combat state... absolutely ridiculous. Getting sapped as a hunter does not exist on classic. Literally impossible.

That being said, I however also believe it was a complete clusterfuck back then on retail too, namely because if you observe retail videos long enough, you will notice that the mechanics are behaving differently and multiple videos show different things.

Combat itself is not even supposed to be triggered by pets. The way pets interact with combat is that they should merely REFRESH already triggered combat state (if you have a combat, pet autoattack will refresh the combat timer, if you dont have combat, the autoattack doesnt do anything).

https://www.youtube.com/watch?v=czV-xTY6NV0&t=268s Here you can see a felguard charging in and hitting rogues, doesn't trigger combat for the warlock until the warlock casts onto enemy player himself.

https://www.youtube.com/watch?v=D16d5kzadYQ&t=65s Here you can see the hunter sending pet in and not getting a combat until he himself attacks the enemy player, even though his pet already attacked the enemy player before...

https://www.youtube.com/watch?v=szKGijo3kWY&t=1078s Here you can see the felhunter is eating the mages ass for 2 hours and the warlock doesnt get into combat until he himself casts onto the mage...

https://www.youtube.com/watch?v=IJIJLBqSAkY&t=391s Here you can see Drakedog sending his sucubus in, sucubus successfuly charms the rogue and Drakedog isnt in combat.

When it comes to this Part of Exyths report: https://youtu.be/paskamMBWZ0?t=1328 The only reason (most probably) the DK got the combat there (22:08+) is because his pet took damage.

They should just unify the behavior and set the rules exactly, currently its super inconsistent and random/not making any sense.

dariuzsdk commented 2 years ago

The videos above are not relevant in this case, and none of them are even from WotLK. The pet-combat state mechanic functioned differently in retail WotLK than "entering combat". If the pet is set to /petattack and is running toward an enemy player, you are un-sappable. This is not the same as you "entering combat" in the traditional sense - as "entering combat" could be shared with your team via AOE buffs like Bloodlust. The pet-combat state mechanic can be countered via Invisibility, Feign Death, Shadowmeld etc mechanics, because it requires you to always have your pet currently moving toward/attacking an enemy. I am not familiar with the "stealth" combat mounted issue you mentioned, but you cannot utilize the pet-combat state mechanic while mounted, as your pet cannot be attacking someone while you are on your mount, if you are mounted you are always sappable with this mechanic. You may have a different opinion on the topic, but this is how the mechanic functioned in the retail version of the game as stated multiple times by Jigs in the video. He even specifies not sending the pet on targets who can go invisible for this reason. This was common knowledge and persisted through the entirety of WotLK retail as a mechanic, and should be fixed to work as such.

JamminL commented 2 years ago

The videos above are not relevant in this case, and none of them are even from WotLK. The pet-combat state mechanic functioned differently in retail WotLK than "entering combat". If the pet is set to /petattack and is running toward an enemy player, you are un-sappable. This is not the same as you "entering combat" in the traditional sense - as "entering combat" could be shared with your team via AOE buffs like Bloodlust. The pet-combat state mechanic can be countered via Invisibility, Feign Death, Shadowmeld etc mechanics, because it requires you to always have your pet currently moving toward/attacking an enemy. I am not familiar with the "stealth" combat mounted issue you mentioned, but you cannot utilize the pet-combat state mechanic while mounted, as your pet cannot be attacking someone while you are on your mount, if you are mounted you are always sappable with this mechanic. You may have a different opinion on the topic, but this is how the mechanic functioned in the retail version of the game as stated multiple times by Jigs in the video. He even specifies not sending the pet on targets who can go invisible for this reason. This was common knowledge and persisted through the entirety of WotLK retail as a mechanic, and should be fixed to work as such.

Everything evolve said is correct for wotlk though.

Pet attack does not give owner combat, only refreshes
Attacking a pet will give owner combat
Buffing a pet in combat will give owner combat
/petattack will not give owner combat but make him unsappable

He's just explaining the full pet/combat mechanic to add to this bug report, "I hope I dont even have to mention the "stealth/invisible" combat state aka "cant sap me" exploit while being able to happily mount up and jump around."

Maybe the confusion here is that he mentioned mounted up, which can't happen in woltk

dariuzsdk commented 2 years ago

For some simple clarifications as this mechanic tends to get a bit confusing for those unfamiliar with how it works and how it differs from the "combat" state and previous posts on this topic;

When a player sends pet (/petattack) at a visible enemy, the player should be immune to sap but not enter the traditional "combat" state.

If the pet is recalled (/petfollow, /petpassive) or pet loses its target (Feign Death, Vanish, Shadowmeld), the pet owner should be immediately sappable.

This /petattack unsappable state cannot be shared with team via AOE buffs like the traditional "combat" state would, and has no 5 second timer after to "drop" combat.

raethkcj commented 2 years ago

Supposedly fixed according to Nov. 8th Patch Notes: https://us.forums.blizzard.com/en/wow/t/wrath-of-the-lich-king-classic-hotfixes-updated-november-8/1323891

Heroclassx commented 6 months ago

So currently on Cataclysm beta this seems to not work anymore. Couldn't find anything in patch notes regarding a change in this mechanic. It seemed to work on the release of beta (sending pet giving you a "stealth combat" and being unable to get sapped.

Yesterday I got sapped while my pet was sent to attack the enemy healer tho. I did a quick recording in a duel on dk/hunter trying to reporduce and was able to get sapped while sending my pet to attack a npc in elwynn forest.

https://streamable.com/z6md2h

ClassicWoWCommunity / cata-classic-bugs