netherspite / cc-buglist

CoreCraft NexT bug tracker
0 stars 3 forks source link

[CLOSED] Sending your pet in attack dont make you immune to sap #246

Closed netherspite closed 6 years ago

netherspite commented 6 years ago

Issue by Winns
Friday Jan 23, 2015 at 16:40 GMT
Originally opened as https://github.com/ccshiro/cc-buglist/issues/246


Sending you pen in attack should make you immune to sap. gif from corecraft

How its work Command your pet to attack target, while pet is still running to target but do not reach him yet you should be immune to sap, also you wont get "in combat" marker until pet start attack target.

This was one of the core warlock/hunter move against rogue teams, so dont rate this as a bug that should not exist, game was balanced around this.

Based on my own experience as an active warlock arena player of s7,s8,s9. Also found some threads about this - http://www.arenajunkies.com/topic/118924-combat-bug-with-pet/ http://www.arenajunkies.com/topic/154952-pet-combat-sap-bug/ http://www.arenajunkies.com/topic/72876-pet-combat-bug/ http://www.arenajunkies.com/topic/103477-3v3-warlock-sap-bug/#entry1375040 Cataclysm: Pet attack makes the game see you as in combat, meaning you are unsappable even if your pet never struck the target.

netherspite commented 6 years ago

Comment by braide
Friday Jan 23, 2015 at 20:17 GMT


No, you're not immune to sap when you send your pet to attack. In TBC your immune when you gain combat, and you only gain combat when the pet actually lands an attack or spell. That is how it was s1,s2,s3,s4. The threads you have shown are from 2009 (which is WOTLK). And your experience is from s7 and foward, which again is not TBC.

netherspite commented 6 years ago

Comment by Winns
Friday Jan 23, 2015 at 22:35 GMT


I did not find any confirmation that this mechanic was changed in WOTLK, found only this comment "..it was discovered in TBC". Gonna check warlock arena videos later.

netherspite commented 6 years ago

Comment by MorbidMike
Saturday Jan 24, 2015 at 14:47 GMT


braide is right. I remember actually sending my pet out to Devour Magic on Mages to prevent getting sapped. Simply sending it to attack would not do the trick.

netherspite commented 6 years ago

Comment by solowt
Saturday Jan 24, 2015 at 18:19 GMT


Braide is correct. In TBC you could get into combat with your pet but it involved your pet actually taking damage, dealing damage, or casting a spell on an enemy player.

netherspite commented 6 years ago

Comment by KuroiKensai
Sunday Jan 25, 2015 at 19:54 GMT


Author is wrong. You are immune to sap only when you are in combat and when your pet is just running - you are not in combat and not immune. If author dont have videos from official 2.4.3 server proofing this of course. Even at the link he provided man clearly states: "it puts them IN COMBAT and they can't be sapped". Even if such thing really existed - this is obviously bug and abuse.

netherspite commented 6 years ago

Comment by SuddenDeath
Sunday Jan 25, 2015 at 23:02 GMT


I know that this existed pretty much through the entire wrath of the lich king because it was the most important thing when playing beastcleave for an enhancement shaman, get wolfs out and send them to attack and you would never get sapped since it put you in combat instantly. I assume it was the same with hunter/warlock pets.

I'm not sure if it was a bug or not though since it was quite a well known thing.

That being said, I remember no such thing from TBC. But I might be wrong.

netherspite commented 6 years ago

Comment by solowt
Sunday Jan 25, 2015 at 23:24 GMT


People sent in pets to get in combat in TBC. But the pets actually had to reach the enemy or cast a spell on them.

netherspite commented 6 years ago

Comment by Devilblessed
Wednesday Jan 28, 2015 at 10:58 GMT


When you send your pet to attack you're not immune to sap. You are immune to sap when you ENTER combat just like all the other classes, and you enter combat when your pet reaches the enemy and attacks.

netherspite commented 6 years ago

Comment by SuddenDeath
Wednesday Jan 28, 2015 at 16:33 GMT


Proof: http://webmup.com/Bt5RD/ (look at his water on the actionbar)

This report is invalid.

netherspite commented 6 years ago

Comment by Stoney21
Wednesday Jan 28, 2015 at 18:43 GMT


It's full of shit report. You get combat if you make an action with your pet on somebody AND ONLY THEN. No action = no combat. You can't get in combat by simply sending your pet to attack someone, you played too much on Smoldershit.

netherspite commented 6 years ago

Comment by Winns
Wednesday Jan 28, 2015 at 19:25 GMT


SuddenDeath video start when warlock already sapped, do you have a full video ? "look at his water on the actionbar" - what do you mean by that ?

Stoney21 dont need to post here If you're incompetent in pvp mechanics.

This report here is to get a truth about tbc combat mechanic, I have provided my facts that this move existed through whole wotlk, i want to see some facts or at least personal tbc experience against or for this statement relatively to tbc.

netherspite commented 6 years ago

Comment by SuddenDeath
Wednesday Jan 28, 2015 at 19:58 GMT


Winns by water I mean this:

When it becomes unusable it is a sign of entering combat. Which did not happen until the felhunter actually casted spell lock on the mage.

netherspite commented 6 years ago

Comment by Winns
Wednesday Jan 28, 2015 at 20:18 GMT


Ok i see, but combat state is displayed at player portrait (level) you dont need water for this. This "unsappable" move work a bit different.

How it work Command your pet to attack target, while pet is still running to target but do not reach him yet you should be immune to sap, also you wont get "in combat" marker until pet start attack target.

You wont get "in combat" marker until pet start attack, but you are already immune to sap when he is just run to target.

netherspite commented 6 years ago

Comment by solowt
Wednesday Jan 28, 2015 at 20:29 GMT


Are you high? Being in combat is what makes you immune to sap. There's no separate mechanic to make you immune to sap but not in combat.

I don't know (or care) if this changed in wotlk+. This is how it worked in vanilla and TBC.

netherspite commented 6 years ago

Comment by somnu
Thursday Jan 29, 2015 at 04:02 GMT


I actually remember what OP says and it was clearly happening in TBC, (warlocks somehow got into combat by just putting the pet to attack my ally who was 100% out of los of pet or lock) but I never bothered to understand how it worked back then. I just raged when they did it cause it was clearly an abuse of an already overpowered class and I'm happy it won't be implemented on corecraft. In wotlk it was fixed and didn't happen anymore, and the only way to get in combat was to actually make the pet cast devour magic or attack on a target. Also it wasn't a separate mechanic that made you immune to sap, it just said "target is in combat". Source: I played rogue all throughout TBC and WOTLK.

netherspite commented 6 years ago

Comment by vexxedd
Saturday Jan 31, 2015 at 11:18 GMT


I actually remember what OP says and it was clearly happening in TBC, (warlocks somehow got into combat by just putting the pet to attack my ally who was 100% out of los of pet or lock) but I never bothered to understand how it worked back then.

Yes, but it was a bug. Back then, (guess it was 2008) there was some tournament (blizzcon?). Do you remember Inflame/Neilyo/Serennia lock/rogue/druid team? They also switch to some war/war/pala in random games. There was also funny video about Neilyo teaching some guy how to wrestling. Back to the point. Inflame was abusing that shit in whole tournament. Basically what you do was something like this: command pet to attack / rain of fire / healthfunell ur pet and you got combat. But was fixed shortly after, so not the point. You cant get immune to sap/get combat unless your pet attack/spell lock/devour enemy player. Period.

netherspite commented 6 years ago

Comment by Stoney21
Sunday Feb 01, 2015 at 13:41 GMT


You are fucking retarded and you should kill yourself if you think you should get in combat by simply sending a pet on someone and befor it even HITS anything. That way you could target any rogue/druid as soon as arena starts and send your pet on them so they can't stealth. IT WOULDN'T MAKE ANY SENSE SO GET A BRAIN BEFOR REPORTING ANYTHING.

netherspite commented 6 years ago

Comment by ghost
Wednesday Feb 04, 2015 at 11:19 GMT


The sensible behaviour is for pet hostile actions to put owner in combat, 'pet attack' shouldn't count regardless of the state of TBC and when it was fixed by blizzard.

Someone might argue that this will tip the pvp balance away from pet teams. Well it's not game-changing bug that someone 100% needs to abuse in order to win. If they relied on abusing such bug then why would we care?

Yes, bugs existed back in TBC, does that mean CC should implement them all? Think not

netherspite commented 6 years ago

Comment by somnu
Wednesday Feb 04, 2015 at 18:02 GMT


I think vexxedd nailed it, and yes - it was a bug of course it was. "Fixing" stuff like this would be like purposely reintroducing exploits into the game, which isn't blizzlike, it's just dumb.

netherspite commented 6 years ago

Comment by jezbelle
Thursday Feb 05, 2015 at 09:11 GMT


Hold up. Just so you guys know- the icon of the water in the picture is for WATER OF THE STARS. Works a little differently than regular water in arena possibly. Maybe not. I just wanted to throw that out there.

netherspite commented 6 years ago

Comment by solowt
Friday Feb 06, 2015 at 02:19 GMT


Star's Tears work the same as normal water except normal water (except mage water) can't be used in arenas.

netherspite commented 6 years ago

Comment by solowt
Saturday Feb 07, 2015 at 02:49 GMT


All of those posts are from early wrath.

netherspite commented 6 years ago

Comment by Brumeux
Wednesday Feb 11, 2015 at 12:05 GMT


Why are you guys bashing on him ? It's not a bug that use to happen on retail server. I have no idea about tbc but it has been like that whole wotlk. Do you think it would have stayed this way that long if it was a bug ? No, it was clearly intentional. It wasn't an abuse nor anything, anyway most locks didnt know that. And just to clarify: NO it wouldn't put you in combat until the pet actually reaches the target or casts a spell. So @Stoney21 stop the caps abuse and YOU get a brain. Rogues/droods would be able to stealth, they wouldn't be in combat. Only thing is that the lock would be IMMUNE to sap.

netherspite commented 6 years ago

Comment by exltus
Wednesday Feb 18, 2015 at 11:57 GMT


here is video, that is showing warlock sending his pet and you can clearly see, that he is not getting combat for almost 5 secs. Pet even casted Devour Magic, that was reflected and even it did not put warlock in combat. So this issue is fully INVALID

netherspite commented 6 years ago

Comment by lawzftw
Thursday Feb 19, 2015 at 14:34 GMT


Because you never understood PvP mechanics doesn't mean those mechanics don't exist.

I know for sure how it worked during WoTLK (on retail), and I'm going to explain it :

I tested it when on retail wotlk, which is the problem (wotlk). But I saw too much nonsense in this thread, and it can still be useful in a way (at least ppl who tell bullshit like "looool noobs if lock isn't in combat he can be sapped!1! even during wotlk").

The only "proof" you can find to say this mechanism didn't exist during TBC is finding a video with a warlock sending his pet, and still getting sapped. It shouldn't be that hard, considering they often send pet to gain combat, right ? Btw don't forget rogues could "bug" pet (even on retail) with distract, so if the pet stops moving mid map, and lock gets sapped, it doesn't count.

netherspite commented 6 years ago

Comment by Philosophers
Friday Feb 20, 2015 at 10:19 GMT


I saw this topic and (as a hunter) I need to comment.

First of all: @lawzftw "The only "proof" you can find to say this mechanism didn't exist during TBC is finding a video with a warlock sending his pet, and still getting sapped."

You have to proof you're right, not others have to proof you're wrong. Not true until proven true. Like not guilty until proven guilty.

I played as a hunter on retail during TBC: I do recall that I was using Wind Serpent as a pet in the arenas just because of it's 20yd range ligtning breath catching combat, to not only rely on trap+flare, cause it was imperfect for skilled rogues. + It can end enemy drinking earlier. I also recall that I dropped Wind Serpent since release of wotlk (I am not sure why, but changes: that could be it). I am pretty sure that hunter pet works same as warlock pet.

I am not sure what it was like that on wotlk, but this expansion did big changes to almost every in-game mechanincs, so anything with "on wotlk" is not proving anything.

netherspite commented 6 years ago

Comment by lawzftw
Friday Feb 20, 2015 at 14:34 GMT


@Philosophers This is not the way it should be done for such a project. The aim is not to prove someone guilty, it is to get the best scripts for this server, balance wise as well. And this contributes to balance (it contributed to balance A LOT during wotlk at least). So if you truly believe in this server's aim, you shouldn't get that reasoning. This is not a trial. Not at all.

However, I've tried to find some evidence about that "mechanism" and I found a lot of tlk posts, even quite early tlk, but no tbc posts, so it sounds like it didn't work that way in 2.4.3. But a video proof would be the best (couldn't find any video about that :/)

netherspite commented 6 years ago

Comment by Philosophers
Friday Feb 20, 2015 at 19:35 GMT


@lawzftw That was metaphor. You have to prove that something is right before it can be changed. Before someone has actual proof there is nothing to discuss.

I am still sure that in TBC pets with ranged attacks were so useful because of that combat catching.

netherspite commented 6 years ago

Comment by exltus
Tuesday Feb 24, 2015 at 17:30 GMT


Hmmm... I think, that I have answer to this topic. I crawled whole web and didn´t find nothing about this issue before WOTLK release. If you put time time restrictions in your google search and you will search for "unsapable" you will get 0 results from 2004 to november 2008, but if you will do same thing in date range from 2009 till now you will get a ton of results. Here are some examples (note, that are from 3.1.0 and higher patch) 1 2 3 etc. So it looks, that this change comes with WOTLK, that means, that is INVALID

netherspite commented 6 years ago

Comment by ccshiro
Tuesday Feb 24, 2015 at 21:50 GMT


@exltus that is a good way of going about it. I will leave this as needs research for a bit longer, in case someone feels like they want to make a counter-point, otherwise I will consider that determining and invalidate this issue.