[HUNTER] (Pet) Crab ability - Pin

[click]

ENTER A PROPER REPORT DESCRIPTION HERE, AND CHOOSE WHICH COMPONENT YOUR TICKET BELONGS TO IN THE "COMPONENT" FIELD BELOW. FAILURE TO DO SO MEANS TICKET WILL BE CLOSED!
Did not know what's the component - database or what.

Hunter Pet ability, Pin, http://old.wowhead.com/spell=50245#comments , is an immobilization effect, lasting 4 seconds. The only difference between Pin and Web (Spider Pet ability) http://old.wowhead.com/spell=4167 (not counting web lasting 1 second longer), should be this: Web is ranged - can be used from up to 30 yards distance, while Pin is melee - your Pet has to be in melee range with the target to cast it. However, on TrinityCore there is one more difference, which is a bug: PIN IS A CHANNELED SPELL, while Web is working correctly - it's just an instant cast ability. Pin also shouldn't be channeled.
WHY Is THIS IMPORTANT? 2 main reasons:

1. If your pet is JUST in the range of melee, like 5 or 4,5 yards, and/or the target is moving at least at normal speed (later - "fast"), no talks about him using, for example, a speed boost, and your Pet casts Pin, generally this will happen: your Pet will use Pin, means, it's cooldown, it will appear on the target for like 0,1 seconds, but, because the target was almost out of melee range, or moving "fast", Pin will break - the target, after receiving Pin, will be moving for another few splits of a second (same goes to any immobilization effects, because of the lag, probably), and that will be enough to move 0,5 yards more, or 1 yard more, if the target was moving "fast" get out of melee range, and break the Pin. So, if you want to use your Pin and not waste it, you have to Pin a very slow movinf target, or the the Pet has to be, basically, under the target's feet. This isn't happening too often. You'll waste Pin if your Pet isn't extremely close to the target. You cant' Pin a Sprinting or Dashing Target. Or Charging. Well, you can, but Pin will instantly disappear from the target. This is...very annoying.
2. After using Pin, if you want to use Intervene or Roar of Sacrifice ( http://old.wowhead.com/spell=53476 , http://old.wowhead.com/spell=53480 )(In patch 3.3.5a Roar of Sacrifice had a very limited range), your pet has to come to you, breaking the Pin. trust me, this is also awkward.
   Source:
   http://www.youtube.com/watch?v=umetTVtTb2A&feature=related . Watch in full screen so that you can see the Pin debuff later. Freeze it at 3:09, and with pauses, quickly play/pause until the ending of 3:09, just before 3:10 - you can see that Pin debuff has appeared on the Rogue. Just after that until 3:13, you can see the Pet leaving the Rogue and coming back to the Hunter - but the Pin debuff REMAINS. At the end of 3:12, it appears on the top right corner of the Rogues debuffs. At 3:13, it's effect simply ends. It lasted slightly shorter than 4 sec, probably because of the Rogue talent Fleet Footed, which reduces movement impairing effect duration on him, but you can still see that Pin is NOT channeled - if it would be, then the Pet would break it by leaving melee range. And there's a few more places in the same video if you need to, just look for Pin - everywhere the Pet leaves the target after casting it.]
   If you have any questions, write a comment.
   Please, someone, fix this - simply (I hope) make it instant, not channeling...

[click]

Author: imnotyou
More info: http://www.trinitycore.org/t/trinitycore/ticket/452

[click]

Author: wiliusas
Well...the ticket mentioned above could contain false information. You see, it's author could've been thinking that Pin doesn't work on moving and jumping targets, because the target has been moving "fast" or the pet hasn't been VERY close. He might have made a wrong assumption.

[imnotyou]

Pin doesn't work properly. '''If your target is jumping and moving it gives the effect but the player can still move.'''
If your target is standing still or just jumping or tries to move or jump after the crab pins hum, it works.

[steel2p]

This commit has nothing to do with Pin. Ability is still bugged.