Decursive
Decursive for World of Warcraft
Decursive is a cleansing mod intended to make affliction removal easy, effective and fun for all the classes having this ability.
Documentation:
NOTE: Type /DECURSIVE to open the configuration panel. Decursive's options are not directly available in the "Interface" panel due to ongoing tainting issues Blizzard is not willing to fix.
Decursive usage - Micro Unit Frames documentation - Decursive Macro documentation - Frequently Asked Questions - commands
Decursive key benefits
Ease of use:
- Decursive supports all classes with cleansing abilities and configures itself automatically, it works straight out of the box, no configuration is required.
- Intuitive interface and detailed options, Decursive is suitable for simple usage and power users.
Control what and who you want to dispel:
- Easily Filter out afflictions you don't want to cure or that are useless to remove by class (some are pre-configured). (Such as afflictions affecting mana on non-mana classes, etc...).
- Choose between what you can dispel (magic, curses, poison, diseases, charms) choosing their priority. (this allows you to share the cleansing work with other players effectively)
- Prioritize or exclude members. (keep players, classes, or raid groups in a specific order to cleanse them in order of importance)
Manage Mind controlled units:
- If you are a Mage, a Druid or a Shaman you can Polymorph/Cyclone/Hex mind-controlled players.
- In any case Decursive will allow you to target mind controlled units easily.
- Decursive supports magic charming affect removal for Shamans (Purge and Hex), Priests (Dispel Magic), Hunters (Tranquilizing Shot), and Warlocks (Fellhunter and Doomguards spells).
Don't waste time:
- Your cleansing spell Cooldown is displayed to maximize your dispel speed.
- An automatic blacklist will prevent you from loosing time on players who can't be dispelled. (player 'out of line of sight' for example).
- Decursive choose a logical cleansing order depending on your current position in the raid. (preventing dispel concurrence between players and thus 'nothing to dispel' messages)
React faster:
- Visual and/or auditive alerts when someone needs your attention and can be dispelled.
- Special sound alert when Unstable Affliction is detected and you're about to dispel it.
- Visual and auditive alert when your dispel attempts are resisted or fail.
Integration in any interface:
- Decursive is designed to save screen real estate and to be forgotten when not needed.
- Many options allow you to customize Decursive appearance and interface behavior.
- All Decursive alert colors can be modified making it suitable for color-blind people.
Highly optimized and effective coding:
- Decursive was developed with memory and CPU usage in mind, installing Decursive won't affect your frame rate even in the worst battle conditions.
- Bug free: bugs are not tolerated in Decursive.
In brief, what you get with Decursive is effectiveness, a player using Decursive will always dispel faster than other players.
See also:
- Decursive usage
- Micro Unit Frames documentation
- Decursive Macro documentation
- Frequently Asked Questions try this before asking any question
- commands
Interesting articles and videos about Decursive's usage:
- 2010-11-20 (Updated in 2011-06-11)
A complete Decursive guide by @darista: daritos.apotheosis-now.com/?p=24
- 2009-07-15
Article: www.hotsdots.com/2009/07/improving-the-interface-using-addons-7-decursive-cleansing-and-dispelling/
- 2010-02-20:
Video: WarcraftScience's Decursive tutorial
For other videos about Decursive, see the YouTube playlist.
Decursive is dedicated to the memory of Bertrand Sense known as Glorfindal on the European server Les Sentinelles. He was the raid leader of my guild (Horizon)
For suggestions, feature request, or bug report, use the ticket system provided by WoWAce.com.
Development versions of Decursive are available at this URI: https://www.2072productions.com/to/decursive_dev ; note that development versions may be unstable. Unless you want to help testing unstable code you should download the versions considered stable below.
Do not forget to rate Decursive!
Bitcoin donation address: 1LEHZuPsiHN4hM3H3Gru5xKmDgCj867eFX
Were the MUFs or other Decursive frames displayed?
'Decursive: Could not process event: init uncomplete!'
Tried a few things, but the only way I seem to be able to shift it is by disabling Decursive, not what I really want to do :(
I've not updated or changed anything to do with Decursive lately, and am using the lastest version.
^V
does the tooltip (the one that is displayed when you over a MUF) gives you the available spells and their mouse click shortcuts?
http://static.curseforge.net/uploads/18/316/823/Decursive-2.3.1_beta_4.zip
I cant copy chat so i did a few screenshoots and zipped them
The errors happened
1) while zoning into the halls of lightning
2) During the quest "hour of the worg" while a partymember was mindcontrolled by arugal
3) After i left a group and joined another
and here are the screenshoots
http://filebeam.com/bb3994563b0f741cb677017a9586ddf5
Instead of changing the units attributes of the MUFs I'll have to move the MUFs arround...
Now I have more time. As to the exact message, 2.3.1 beta 1's Dcr_DebuffsFrame.lua & Dcr_Events.lua contains four different versions of it. Dcr_DebuffsFrame.lua has:
#1) ALERT:|rSanity check failed in MicroUnitF:UpdateMUFUnit() Cattrib ~= CurrUnit.
#2) ALERT:|rSanity check failed in MicroUnitF:UpdateMUFUnit() unit ~= MF.CurrUnit.
#3) ALERT:|rSanity check failed in MicroUnitF:OnEnter() Cattrib ~= CurrUnit.
Dcr_Events.lua has:
#4) ALERT:|rSanity check failed in combat event manager Unit_Array_GUIDToUnit[] is wrong.
Other than "Sanity check failed..." I have no memory of the rest of the message strings. Fortunately, though, I have a mod that takes screenshots after every boss death. And sure enough, checking them out, a couple had examples of the messages received. They were all what you quoted (#2 above): ALERT:|rSanity check failed in MicroUnitF:UpdateMUFUnit() unit ~= MF.CurrUnit.
The other three Sanity messages may or may not have occurred, but that's all I have record of. The WoWChatLog.txt file does not record debug messages such as that.
In the Gundrak Heroic instance, the NPCs cast mostly poison attacks, with some magic. Was playing a priest, thus could not dispell the poison. Despite the debug spam, the MUF's still alerted to magic attacks I could dispell without an issue. The debug messages seemed to occur as well long after combat when no one in party was affected with anything.
I switched to SmartDebuff soon after our old conversation. I came back to Decursive once the problem reported had apparently been resolved and have been using it since (it uses far less resources than SmartDebuff). Hope you are able to resolve what it is the Beta debug messages are alerting to.
Please update to Decursive 2.3.1 beta 2 and tell me if you still see those messages (there is a good chance you do unfortunately), I made some fixes but I still don't understand how this message could be displayed...
I've added debug information to the messages so I'll have more clues next time. :)
First tried it solo again mobs that cast debuffable spells. Then had it on running Utgarde Keep (UK) Heroic instance in a party of 5. No problems, everything worked smoothly. That is, until coming up to the first boss in Utgarde Keep. Then the spam began.
When mousing over the boss (or something else) before engaging him, the following Chat1 error was thrown up. The identical error was spammed nearly continually in Chat1 from then on until the party disbanded at the end of the instance:
"ALERT: Sanity check failed in MicroUnitF:UpdateMUF() unit ~= MF.Curr.Unit (partypet2 ~= partypet4 - true)"
It at first appeared to be reproducible by mousing over the hunter pet, warlock pet and/or shaman totems in party. Again, the error never appeared until we got to the first UK Heroic boss. But then, the error started coming up when I moused over the different party player unitframes, not the pets (I heal using the Clique mod). And virtually every other time. It stopped when the party disbanded. There was no issue dispelling any MUF alert, though, despite the chat spam.
I'm raiding this weekend; back to 2.3.0 (which operates without any issues so far) until next week. Hopefully one of the thousands of other users can provide bug reports if you release a beta update before then.