Jump to content

[sql fix][8873] Rune Strike


Auntie Mangos

Recommended Posts

What bug does the patch fix? What features does the patch add?

Allows DK to use Rune strike; allows DK to use Rune strike only after dodge or parry.

For which repository revision was the patch created?

8505

Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread.

http://getmangos.eu/community/viewtopic.php?id=9197

And on russian forum: http://getmangos.org/forum/showthread.php?t=21451

Who has been writing this patch? Please include either forum user names or email addresses.

Lightguard , me(second part)

INSERT INTO spell_learn_spell () VALUES
(56815, 56816, 0);

-- (56816) Rune Strike ()
DELETE FROM `spell_proc_event` WHERE `entry` IN (56816);
INSERT INTO `spell_proc_event` VALUES
(56816, 0x00000000, 0, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000030, 0.000000, 0.000000, 0);

Link to comment
Share on other sites

  • 39 years later...
  • 1 month later...
  • 7 months later...

I'm running revision 10189, i have applyed the fixs mentioned and "rune strike" doesn't work at all, i am wondering if something went wrong, i have tried editing even the table mannually in sqlyog but no success, is it happening only to me or is someoneelse having the same problem?

Thanks in advance

Link to comment
Share on other sites

can you explain in details what it means, dbc you mean the database or the dbc files? is there a way to fix it with a dbc editor? sorry but i've been trying to solve it but no success.

Thanks

Rune Strike was using a supporting spell to proc (spell id 56817). Now the supporting spell is deleted by blizz from the client (is not in game anymore, you cant use it). More details on http://www.wowhead.com/spell=56816.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use