|v2.23 +1 More release||290.25 KB||Oct 24, 2013||5.4.0||17,112||Download|
|v2.22 +1 More release||289.68 KB||Jun 24, 2013||5.3.0||8,356||Download|
|v2.21 +1 More release||289.63 KB||Mar 6, 2013||5.2.0||9,673||Download|
|v2.20 +1 More release||289.46 KB||Dec 16, 2012||5.1.0||10,195||Download|
|v2.17 +1 More release||289.08 KB||Dec 2, 2012||5.1.0||6,469||Download|
|v2.16 +1 More release||288.77 KB||Sep 5, 2012||5.0.4||14,623||Download|
|v2.15 +1 More release||288.44 KB||Nov 30, 2011||4.3.0||53,734||Download|
|v2.14 +1 More release||288.31 KB||Jun 29, 2011||4.2.0||25,000||Download|
|v2.13 +1 More release||287.83 KB||Apr 27, 2011||4.1.0||19,238||Download|
|v2.12 +1 More release||287.64 KB||Apr 9, 2011||4.0.6||12,192||Download|
|r5 +1 More beta||229.06 KB||Aug 28, 2012||5.0.4||295||Download|
|r24 +1 More alpha||230.35 KB||Oct 24, 2013||5.4.0||22||Download|
|r23 +1 More alpha||230.33 KB||Oct 24, 2013||5.4.0||12||Download|
|r22 +1 More alpha||230.30 KB||Oct 24, 2013||5.4.0||19||Download|
|r21 +1 More alpha||229.93 KB||Jun 24, 2013||5.3.0||8||Download|
|r20 +1 More alpha||229.91 KB||Jun 24, 2013||5.3.0||14||Download|
|r19 +1 More alpha||229.77 KB||Mar 18, 2013||5.2.0||147||Download|
|r18 +1 More alpha||229.74 KB||Mar 6, 2013||5.2.0||20||Download|
|r17 +1 More alpha||229.72 KB||Mar 6, 2013||5.2.0||16||Download|
|r16 +1 More alpha||229.56 KB||Dec 16, 2012||5.1.0||18||Download|
|r15 +1 More alpha||229.53 KB||Dec 16, 2012||5.1.0||34||Download|
|r14 +1 More alpha||229.51 KB||Dec 16, 2012||5.1.0||16||Download|
|r13 +1 More alpha||229.49 KB||Dec 16, 2012||5.1.0||15||Download|
|r12 +1 More alpha||229.47 KB||Dec 16, 2012||5.1.0||12||Download|
|r11 +1 More alpha||229.44 KB||Dec 16, 2012||5.1.0||14||Download|
|r10 +1 More alpha||228.97 KB||Dec 2, 2012||5.1.0||11||Download|
|r8 +1 More alpha||228.53 KB||Sep 5, 2012||5.0.4||11||Download|
|r7 +1 More alpha||228.51 KB||Sep 5, 2012||5.0.4||8||Download|
|r6 +1 More alpha||229.19 KB||Aug 30, 2012||5.0.4||160||Download|
|r4 +1 More alpha||228.35 KB||Nov 30, 2011||4.3.0||29||Download|
|r1 +1 More alpha||228.02 KB||Jun 29, 2011||4.2.0||25||Download|
|r0 +1 More alpha||227.99 KB||Jun 29, 2011||4.2.0||26||Download|
|r62 +1 More alpha||227.73 KB||Apr 27, 2011||4.1.0||37||Download|
|r61 +1 More alpha||227.70 KB||Apr 27, 2011||4.1.0||65||Download|
|r60 +1 More alpha||227.68 KB||Apr 27, 2011||4.1.0||24||Download|
|r58 +1 More alpha||227.58 KB||Apr 9, 2011||4.0.6||23||Download|
|r56 +1 More alpha||227.59 KB||Jan 29, 2011||4.0.3a||46||Download|
|r55 +1 More alpha||227.56 KB||Jan 29, 2011||4.0.3a||28||Download|
|r54 +1 More alpha||227.53 KB||Jan 29, 2011||4.0.3a||19||Download|
|r53 +1 More alpha||227.46 KB||Jan 28, 2011||4.0.3a||31||Download|
|r51 +1 More alpha||224.88 KB||Dec 23, 2010||4.0.3a||17||Download|
|r50 +1 More alpha||224.77 KB||Dec 13, 2010||4.0.3a||53||Download|
|r48 +1 More alpha||223.95 KB||Nov 11, 2010||4.0.1||28||Download|
|r47 +1 More alpha||223.93 KB||Nov 10, 2010||4.0.1||34||Download|
|r46 +1 More alpha||223.92 KB||Nov 10, 2010||4.0.1||24||Download|
|r45 +1 More alpha||223.73 KB||Nov 2, 2010||4.0.1||47||Download|
|r44 +1 More alpha||223.50 KB||Nov 2, 2010||4.0.1||28||Download|
|r42 +1 More alpha||223.43 KB||Oct 24, 2010||4.0.1||27||Download|
|r41 +1 More alpha||223.33 KB||Oct 22, 2010||4.0.1||31||Download|
|r39 +1 More alpha||222.80 KB||Oct 15, 2010||4.0.1||20||Download|
|r38 +1 More alpha||222.77 KB||Oct 14, 2010||4.0.1||31||Download|
|r36 +1 More alpha||222.85 KB||Oct 14, 2010||4.0.1||32||Download|
|r35 +1 More alpha||222.92 KB||Oct 14, 2010||4.0.1||33||Download|
|r34 +1 More alpha||217.40 KB||Oct 14, 2010||4.0.1||29||Download|
|r33 +1 More alpha||217.34 KB||Oct 14, 2010||4.0.1||36||Download|
|r31 +1 More alpha||222.81 KB||Oct 12, 2010||4.0.1||52||Download|
|r30 +1 More alpha||222.64 KB||Oct 4, 2010||4.0.1 +1||1,247||Download|
|r29 +1 More alpha||222.59 KB||Sep 30, 2010||4.0.1 +1||31||Download|
|r27 +1 More alpha||222.53 KB||Sep 26, 2010||3.3.5||1,005||Download|
|r25 +1 More alpha||222.07 KB||Aug 3, 2010||3.3.5||62||Download|
|r23 +1 More alpha||221.95 KB||Jul 27, 2010||3.3.5||41||Download|
|r22 +1 More alpha||221.25 KB||Jul 27, 2010||3.3.5||38||Download|
|r21 +1 More alpha||221.06 KB||Jul 22, 2010||3.3.5||130||Download|
|r19 +1 More alpha||209.91 KB||Jul 2, 2010||3.3.5||41||Download|
|r18 alpha||210.29 KB||Jun 19, 2010||3.3.5||53||Download|
|r16 alpha||210.36 KB||Jun 17, 2010||3.3.5||201||Download|
|r14 alpha||210.22 KB||Jun 14, 2010||3.3.5||51||Download|
|r12 alpha||210.21 KB||Jun 14, 2010||3.3.5||70||Download|
|r10 alpha||210.18 KB||Jun 14, 2010||3.3.5||682||Download|
|r9 alpha||210.31 KB||May 24, 2010||3.3.5||40||Download|
|r8 alpha||210.25 KB||May 24, 2010||3.3.5||78||Download|
MFClip – All-in-one shadow priest addon
As of patch 6.0, I finally decided to stop updating MFClip. Current gameplay does not fit MFClip. For an alternative, please consider my other addon, Gnosis (Castbars and Timers)
MFClip originally started as a mere Mind Flay clipping warner (hence its name) telling the user when unintentional clips of Mind Flay were ocurring. Clipping Mind Flays as such isn't as important as it had been in earlier and perhaps easier times. Still, to min/max it is important to know if unintentional clipping happens.
In its current state, MFClip features a full blown single target dot timer with cooldown bars for Mind Blast and Shadow Word:Death and an additional castbar (which shows spell ticks). The dot timer bars show the user when it's best to recast any of the three dots (Cataclysm: recast before dots actually fall of to guarantee 100% uptime).
At the end of the fight (and also shown on the bars during the fight if not deactivated) MFClip presents the user with information about dot uptime, spell casting efficiency and how well cooldowns of MB and SW:D had been used.
MFClip warns about unintentional Mind Flay clips (clipping shortly before next Mind Flay tick). MFClip warns by playing a configurable Sound and/or displaying Mind Flay damage data via common combat text addons (currently supported: SCT/MSBT/Parrot/Blizzard Floating Combat Text).
Clipping Mind Flay shortly after the second tick to cast Mind Blast/DP/VT increases your damage output. Unintentional clips shortly before a tick decrease your damage output, including the third and final tick. MFClip's goal is to help you to learn when to cast while channeling Mind Flay and to ensure you are doing it right. As a side note, zero unintentional clips (to much idle time between tick and new cast) decrease your dps as well as regular unintentional clips do, playing somewhat aggressive helps your dps. Also, it is recommended to filter out Mind Flay with your combat text (if available) and use MFClip combat text output (if available for your combat text addon). If you are using [nochanneling] macros there is no need to use MFClip ([nochanneling] leads to less dps).
Installing a cast bar addon with a customized cast bar skin that shows when Mind Flay ticks is strongly recommended. I recommend my castbar addon Gnosis which features tick displaying and clipping detection: http://wow.curse.com/downloads/wow-addons/details/gnosis.aspx
From Version 1.0 onwards MFClip features its own Castbar. This is integrated into MFClip's LiveBars. LiveBars consist of a castbar with latency support für Mind Flay & Mind Sear ticks, a cooldown bar for Mind Blast and dot timers for VT, DP, SW:P. Those bars also display efficiency data for casting/dot uptime/cooldown usage and show the DPS of the different damage sources.
Version 1.2 introduces focus target cast buttons called LiveButtons. Those are part of LiveBars and can be configured in the LiveBars tab.
Remark: MFClip's dot uptime calculations begin the moment the dot is cast onto the unit the first time. Uptime calculations end when a unit dies (not when the fight ends). Uptime calculations take dot clipping into account.
Shadow Orb and Empowered Shadow tracking
MFClip v2.10 offers full support for Shadow Orbs and Empowered Shadow. Tracking is integrated into the Mind Blast cooldown bar, which will change its background color depending on following states (all colors can be edited in the configuration menu):
Light green: Cast Mind Blast asap (three Orbs active, but no Emp. Shadow)
Bright White: Three Orbs waiting to be consumed
Green: Cast Mind Blast asap (one or more Orbs active, no Emp. Shadow)
Yellow: Cast Mind Blast soon (Empowered Shadow buff gone in 3s or less)
Red: Don't cast Mind Blast or dots now (no Orbs or Emp. Shadow)
Default: Stick to your default "rotation"
These states offer basic information about Shadow Orbs and Emp. Shadow. Make sure you understand current theorycraft behind Shadow Orbs and Empowered Shadow to choose the best action depending on your current situation.
Video: MFClip v1.0 Intro Video
Basic introduction video showing MFClip's basic features and the newly revamped LiveBars.
If the above video is blocked in your country try this link: http://www.youtube.com/watch?v=OlDxm9lrk0E
Video: MFClip vs. the Mistery of Nochanneling
Video: casting & statistic output
Video showing MFClip's statistics output (v0.6+). Audio featuring the typical MFClip clipping sound. Addons: MSBT, Quartz+Quartz_LatencyMF2 and a single Macaroon bar. See Video: Live Bars for bars displaying statistics during combat.
The slash command for MFClip is /mfclip.
- /mfclip enable
- enables/disables MFClip
- /mfclip config
- calls configuration gui (using Blizzards addon config interface)
- /mfclip configlb
- calls configuration gui for LiveBars (using Blizzards addon config interface)
- /mfclip reset
- resets configuration data
Configuration Options (GUI)
- Enable Addon
- enable/disable MFClip
- Show combat data
- toggles showing Mind Flay damage, casting and clipping statistics at the end of the current fight (30s fights minimum)
- Clipping warning [ms]
- if the caster clips Mind Flay the given time (in ms) before a tick should occur an unintentional clip is recorded (lag dependent, play around with that setting)
- Wait for Combat Log [ms]
- time (in ms) MFClip waits for combat log data after the Mind Flay tick should have occured (lag dependent, play around with that setting); after given time has elapsed without a tick Mind Flay cast data is generated and output if selected
- Auto Adjust Wait for Combat Log
- adjusts wait for combat log on high haste situations
- Play Sound
- play sound (Sound File) when unintentional clip is recorded
- Generate Combat Text
- generate combat text output for selected combat text (Select Combat Text), combines Mind Flay ticks into Mind Flay cast, also showing unintentional clips
- Out of/In combat config
- LiveBars configuration string executed when leaving/entering combat. Following commands are accepted.
- enables/disables LiveBars
- hides/shows castbar while not casting
- creates castbar/MB cooldown bar/dottimer; command order gives order how LiveBars will be shown from top to bottom
- enables LiveButtons
- LiveButtons configuration string
- shows LiveButtons in combat only
- creates buttons for focus target casting of Mind Flay/Mind Sear/Mind Blast/VT/DP/SW:P/SW:D/Shackle Undead
- creates LiveButton bar as one row, if not specified as one column
Remark: Anchors of both LiveBars and LiveButtons are only shown when LiveBars are enabled with on command (or omitted on/off command).
Configuration in english only, but works for all languages.
Q: Sometimes MFClip reports an unintentional clip even though I'm sure I didn't clip Mind Flay at all.
A: MFClip depends on combat log information about Mind Flay ticks. Usually combat log events are delayed by several hundred millisecond, in bad cases even more than one second. Mind Flay ticks occur regularly on server side usually much less than a second apart (denpending on gear). If the expected time a tick should occur and the time the tick is reported are too far apart MFClip will report an unintentional clip even though that might not the case.
This is where the values Clipping warning [ms] and Wait for Combat Log [ms] come in.
Clipping warning [ms]: If you start a new action x ms (default is 300ms) before a tick should occur, and no tick actually does in time, MFClip will detect unintentional clipping (even though that might not be the case with extreme combat log delay)
Wait for Combat Log [ms] is the time MFClip will wait for the combat log to return tick information after Mind Flay should have ticked and no new Mind Flay cast was started. 1000ms is the default value and this should be ok in every situation. Still, the combat log screws up sometimes and there is not really much anyone can do about it. If you channel one Mind Flay after another MFClip will wait less time than specified by this value depending on your current haste value.
From my own tests combat log delay will not vary much between MF2 and MF3, therefore unintentional clipping should be detected well for both (or not well for both if your combat log delays are too high).
Q: MFClip shows a castbar and I don't want that!
A: Remove the "cast" command from the LiveBars configuration strings (on the LiveBars gui page).