(175Kb)

Updated: 02-07-18 03:43 PM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Shadows of Argus (7.3.0)
Updated:	02-07-18 03:43 PM
Created:	unknown
Downloads:	5,527
Favorites:	15
MD5:

Parry Assist

Version: 1.5.8

by: Selina [More]

This addon evaluates the combat log and looks for attacks which were parried. What it does once a parry is detected depends on the mode(s) which are activated at the time. In logging mode it will write information on what attack got parried and who made the attack in the standard chat tab. In tank mode it will warn the offender and inform him that he just caused some parry haste on you. (Assuming you actually are the tank that is, tank mode does nothing if you aren't tanking the mob).

Per default only parries by boss mobs are reported as the effect of parry haste on trash should be neglible. You can however change this behaviour by activating trash mode.

The motivation for this addon came from numerous wipes on bosses like Supremus caused by overzealous melee dps who didn't position themselves correctly and consequently causing wipes due the increased boss dps from parry haste effects.

Type:
/pa to open the configuration dialog.
/pa help or /pa info for a small list of commands
/pa show to open the reporting frame
/pa reset to reset the reporting frame to default values

Next on my TODO list:
- Nothing -

I'm out of ideas right now so unless someone comes up with a suggestion on what might be added, don't expect any updates (other than fixes) for a while.

A more complete changelog can be found in changelog.txt within the archive.
V1.0.0 Initial Release

V1.1.0
A basic DPS mode has been added which warns DPSers if they cause a parry on a (boss) mob.

V1.1.1
Warnings are now more configurable and configuration in general has been cleaned up a bit.

V1.2.0 -
Almost fully localized for enUS/enGB/deDE (only some debug messages were left untouched)

V1.2.2 -
Added a few more colour choices and fixed a problem with english locales. Now defaulting to enUS.

V1.2.3 -
Fixed a few small errors and cleaned up configuration dialogs some more.

V1.2.4 -
Made colours much more customizable. This required a change in the SavedVariables file. A simple fix is in place, but if you get errors, please delete your ParryAssist.lua in your Saved Variables folder. I'm sincerely sorry for this bad planning on my part.

V1.2.5 - Added an option for a warning message to be displayed prominently in the middle of your screen if you get parried in DPS mode

V1.3.0 -
Added an exclusion list and means to manage it. Units on the exclusion list won't be reported if their attacks get parried.
Added a switch for a "Silent mode". If activated most changes to the configuration won't be reported in the chat frame.

V1.3.1 -
Added support for LibSink. Warning messages can now be sent to any LibSink-supported "sink". Thanks to Sano @ WoWinterface for the good suggestion

V1.4.0 -
Added a custom message frame which can recieve all those notifications and basically provide a scrollable log of all reported parries. The content of the frame does not persist through gaming sessiosn as non of it's content is saved nor does it look pretty, but it gets the job done. I might improve looks and functionality in a future release. (Type /pa show to open this frame)

V1.4.1 -
Improved precision of the timestamps in the reporting window.

V1.4.2 -
Moved settings for the exclusion list management to an extra tab.
Localized the reporting frame

V1.4.3 -
Added a few commandline options and rearranged the reporting frame a bit.

V1.4.4 - Reporting frame is now resizeable

V1.4.5 - Updated the embedded Ace3 libs and confirmed compatibility with WoW 3.0

V1.4.7 - Updated all embedded libs (ace3 as well as LibSink) and bumbed up the interface version for 3.1.x

V1.4.8 - Updated all embedded libs (ace3 as well as LibSink) and bumbed up the interface version for 3.3.x

V1.4.9 -
Fixed a problem that I introduced without noticing during one of those updates to the embedded libraries. Obviously messed up a path and didn't notice it because another addon loaded the lib in question correctly.

V1.5.0 -
Updated for WoW 4.0

V1.5.1 -
Updated vor WoW 4.1

V1.5.2 -
Updated for 4.2.0

V1.5.3 -
Updated for 4.3.0 (toc and embedded libs)

V1.5.4 -
Updated for 5.0.5

V1.5.5 -
Updated for 5.4.2

V1.5.6 -
Updated for 6.2.3

V1.5.7 -
Fixed small issue from last update

V.1.5.8 -
Updated for 7.3.5

Comment Options

10-14-10, 12:34 PM
Agata A Murloc Raider Forum posts: 7 File comments: 42 Uploads: 0	Thank you for the detailed information! http://www.worldofraids.com/wow-blue...nk-thread.html Code: Our plan is to revert parry back to 100% avoidance and remove the concept of swing speed increase for any creature (players could still do it). So parryhaste is disabled by default now and my suggestion was nonsense. Excuse you for bothering.

10-14-10, 08:55 AM

Selina

A Deviate Faerie Dragon

Forum posts: 10

File comments: 14

Uploads: 2

Originally posted by Agata
Have to check, if http://wow.curse.com/downloads/wow-a...arryhaste.aspx is 4.0.1 compatible - if not, some inspiration:

- Only activate the messages on bosses which have confirmed parryhaste being enabled bei blizzard. For example a WotLK list:
http://maintankadin.failsafedesign.c...rb_v=viewtopic

- Maybe some integrated algorithm to check if new bosses in cataclysm have it enabled or not?

It would reduce the spam significally.

Thank you for your interest!

Parry's are a bad thing for DPS even if they don't cause parry haste, because each parried attack does no (or less with 4.0.1 ?) damage.

But I agree that this is a good suggestion for the tank mode as a tank shouldn't warn people about parries if they can't cause haste.

I will see if I can implement it into my addon.

Thank you for the suggestion.

10-14-10, 07:48 AM
Agata A Murloc Raider Forum posts: 7 File comments: 42 Uploads: 0	Have to check, if http://wow.curse.com/downloads/wow-a...arryhaste.aspx is 4.0.1 compatible - if not, some inspiration: - Only activate the messages on bosses which have confirmed parryhaste being enabled bei blizzard. For example a WotLK list: http://maintankadin.failsafedesign.c...rb_v=viewtopic - Maybe some integrated algorithm to check if new bosses in cataclysm have it enabled or not? It would reduce the spam significally. Thank you for your interest!

10-14-10, 07:30 AM
Selina A Deviate Faerie Dragon Forum posts: 10 File comments: 14 Uploads: 2	Cataclysm / WoW 4.0 The addon should now work properly with WoW 4.0.1 and Cataclysm. If you find any bugs please let me know as I only had time for some basic testing. Edit: There seem to be several issues with the reporting frame. Will look into it as soon as I find the time. Last edited by Selina : 10-14-10 at 07:58 AM.

09-22-08, 07:56 AM
Selina A Deviate Faerie Dragon Forum posts: 10 File comments: 14 Uploads: 2	Wrath of the Lich King / WoW 3.0 I've performed some basic testing and the addon should be ready for the next major version of WoW. If someone runs across a problem while using this mod in the WoW beta or on the 3.02 PTRs please let me know so that I can look into the matter. Thanks in advance.

08-25-08, 03:14 PM

Selina

A Deviate Faerie Dragon

Forum posts: 10

File comments: 14

Uploads: 2

Re: Nice Work

Originally posted by Sano
Nice mod, it has been a big help in heightening our melee DPS's parry awareness. Have you considered using LibSink for the warning messages instead of your custom frame?

To be honest I didn't do all that much planing so far. This is my first mod and it just evolved out of my own needs and suggestions from a few raid members, that have been using it.

I'm currently working on implementing one such suggestion. (A list of units to exclude from parry checks, like the main tank). Once I've finished that I'll gladly take your suggestion and look at LibSink and see if I can use it instead of my custom frame.

08-25-08, 10:59 AM
Sano A Defias Bandit Forum posts: 3 File comments: 29 Uploads: 4	Nice Work Nice mod, it has been a big help in heightening our melee DPS's parry awareness. Have you considered using LibSink for the warning messages instead of your custom frame?

Report this File

Category Jump: