[7889][FIX] Mutilate

[Auntie Mangos]

This patch would fix the bug that mutilate still requires the caster to be behind the target.

rev. 7226

Bug thread: http://getmangos.eu/community/viewtopic.php?id=5996

patch: http://paste2.org/p/142193

[spotinsh]

thank u. Hope it will be added in next revs asap

DEVS???

[pugacov]

still works only from behind

[kallan]

still works only from behind

well rogues love it from behind:Ph34r::Ph34r:

[Lightguard]

I'll chek it on a newer rev. but it worked for me...

[spotinsh]

still not fixed.

[KAPATEJIb]

http://mangos.ru/showthread.php?t=17228

[Lightguard]

Well, i don't speak enough russian for that, but i searched trough the russian forum too, and it wasn't there that time. Anyway, it doesn't matter where's the patch from, just put it in the core if it's working ASAP.

[Sephiroth1983]

There should be some flag to say if requires to be behind the target in my view... need more research and we don't have to deal with this each client change.

Check the difference in dbc files between the 2 client versions, I'm sure you can find something. If nothing, then is like you suggest with your patches...

[most wanted]

Bump, patch is really needed for rogues:(

[spotinsh]

They don't care

[bogie]

funny thing on offi:

i had the "can only be used from behind" message once with mutilate as well which was rather confusing ;D

[Lightguard]

The patchnotes confirm that you don't have to be behind your target.

[VladimirMangos]

m_spellInfo->AttributesEx3 != 0x01010400

Not best way for check. Maybe it can be checked in same way as current exopecption by spelle family name/flags pair?

[Lightguard]

The main problem with the familyflags is that we're talking about 20 spells, as Mutilate triggers 2 other spells each of them different every rank, and all requires you to be behind the target, and of course they have different FamilyFlags otherwise it would be too easy.

[Sorken]

This is the way to go: http://paste2.org/p/151732

[Sephiroth1983]

This is the way to go: http://paste2.org/p/151732

Yeah, the same has been done for Pounce.

Hope is in svn soon because Mutilate rogues without this fix are too nerfed in 3.0.9.

[Lightguard]

Yeah, it would be great to have it cimmitted:)

[spotinsh]

what's new about fixing mutilate facing?

[Sephiroth1983]

Date_____________Change

2009-01-21 12:34:16 unknown_211 changed from '16778240' to '16843776'

2009-01-21 12:34:16 unknown_170 changed from '0' to '2097152'

these are the changes offy did on the spell in that date

http://wow.allakhazam.com/db/spellhistory.html?wspell=1329

maybe one of them is facing flag changed?

[Tassader2]

these are the changes offy did on the spell in that date

maybe one of them is facing flag changed?

I think it is

2008-10-15 00:04:53 unknown_141 changed from '16711916' to '16712172'

because that's when the description changed

2008-10-15 00:04:53 description changed from 'Instantly attacks with both weapons for an additional $5374s1 with each weapon. Damage is increased by 50% against Poisoned targets. Must be behind the target. Awards 2 combo points.' to 'Instantly attacks with both weapons for an additional $5374s1 with each weapon. Damage is increased by 50% against Poisoned targets. Awards 2 combo points.'

[spotinsh]

nah, that was about poisoned damage.

2008-10-15 00:04:53 unknown_141 changed from '16711916' to '16712172'

this one is about facing.

[Haltorn]

bump please kthxbye

[_1nsan1ty_]

* edit * removed sorry

[_1nsan1ty_]

-            //Exclusion for Pounce: Facing Limitation was removed in 2.0.1, but it still uses the same, old Ex-Flags
-            if( m_spellInfo->SpellFamilyName != SPELLFAMILY_DRUID || m_spellInfo->SpellFamilyFlags != 0x0000000000020000LL )

+            //Exclusion for Pounce and Mutilate: Facing Limitation was removed in 2.0.1 and 3.0.3, but they still use the same, old Ex-Flags

+            if((m_spellInfo->SpellFamilyName != SPELLFAMILY_DRUID || m_spellInfo->SpellFamilyFlags != 0x0000000000020000LL) && !(m_spellInfo->SpellFamilyName == SPELLFAMILY_ROGUE && m_spellInfo->SpellFamilyFlags == 0x0020000000000000LL))

Confirmed working in 7591