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
This is fixed in the latest beta
Please report the content of this window to [email protected]
(Use CTRL+A to select all and then CTRL+C to put the text in your clip-board)
Also tell in your report if you noticed any strange behavior of Decursive.
2.7.2.1 PRIEST(88) CT: 7737.3810 D: 09/27/12 03:51:38 enUS BGe BDTHFAd: true nDrE: 2 Embeded: true W: 1 LA: 42 TA: 0 (5.0.5, 16057, Sep 10 2012, 50001)
*****************
7711.1030 (h87_w100-33fps-Kun-Lai Summit): Decursive-2.7.2.1\Dcr_DIAG.lua:217: script ran too long,
STACK:
, Decursive-2.7.2.1\Dcr_DIAG.lua:217: in function <Decursive\Dcr_DIAG.lua:178>
Thanks for this report, this will no longer happen if you use the latest alpha:
http://www.wowace.com/addons/decursive/files/
How do I clear the interface LUA errors log out? I updated an addon (arkinventory) and it generated a TON of problems, so I backed it out to the previous release, but decursive is still saying there are 1000+ errors when in reality there's only one that gets reported anymore and the rest are all the stored messages from that rolled back addon.
I've tried poking around my WoW directory to see if I can find it but haven't had any luck - where is the LUA/interface error log kept so I can zero it and start clean?
There is no persistant Lua error log, if decursive tells you that there are 1000+ errors then it's true. You might want to install the addons buggrabber and buggsack to see those errors (the default Blizzard error hanler is bugged).
Just got the popup that it could not find shared library libshefkitimer-1.0
i exited WoW. I use curse premium, did a refresh, update all and restarted WoW and got same message
I entered libshe into my windows 7 search and it did not find anything on my disk
LibShefkitimer-1.0 should be in Decursive's lib folder:
World of Warcraft Beta\Interface\AddOns\Decursive\Libs
if it isn't, it means that your installation of Decursive is corrupted, delete the decursive folder and reinstall it from the curse client.
Can you stop spamming me when it's a blizzard UI that's generating the lua errors? I can't fix them so the "messenger" should stop telling me to do so... At least consider changing it to something that doesn't take 10 lines of my chat window away.
could you give me one of these Lua errors as an example?
Hello. Im playing prist ant there is 2 dispel spells - Dispel Magic and Purify.
There is no magic, as i know, that can be dispelled from friend with Dispel Magic (which Decursive assign to left-click). And i cannot find where to disable this spell in configuration or at least switch left-right clicks, cause left click to dispel friend used on my HPal, this would be great to dispel with left-click on Prist.
Dispel magic is used on magically mind controlled players (whom are no longer friendly when mind ontrolled). You can change the click assignments in the micro unit frames settings. Type /decursive
@frozuntexan
This should be fixed in the latest alpha.
See this post, I think it will explain this issue http://us.battle.net/wow/en/forum/topic/6413024969?page=1#6
On my resto druid.
I've tried uninstalling and reinstalling, to no avail.
It starts out working fine, and then I get a slew of lua errors, like five pages, and it stops working.
Then it starts "removing" members of the party from what it tracks and shows, each time it does that I can tell because I get another round of lua errors and a party member's little box disappears, until I'm the only one left showing, and even then it doesn't show that I have something on me I can cure or dispell.
I'm not sure how to copy/paste that info here, so if that's helpful information, some guidance would be appreciated.
I'm using the most current version of Decursive (at least according to Curse Client). The other add-on's I'm using are Clique, Elphie's Interrupt Say, and Recount (though I leave Recount turned off when I'm healing).
Without the Lua erros there is nothing I can do. Normally the window where the Lua errors are displayed lets you copy the text displayed (Ctrl+C or Apple+C).
OK, I ran a couple instances in "boomy" mode, where no one would notice if I read the report, lol. Turns out that there are also errors in recount and quartz, but the following is the Decursive error I received ...
Please report the content of this window to [email protected]
(Use CTRL+A to select all and then CTRL+C to put the text in your clip-board)
Also tell in your report if you noticed any strange behavior of Decursive.
2.7.1.1 DRUID(69) CT: 1668.5150 D: 09/09/12 10:00:46 enUS BGe BDTHFAd: true nDrE: 2 Embeded: true W: 1 (5.0.4, 16016, Aug 21 2012, 50001)
*****************
461.4040 (h131_w160-11fps-Utgarde Keep): Decursive\Decursive-2.7.1.1.lua:802: script ran too long,
STACK:
, Decursive\Decursive-2.7.1.1.lua:802: in function "CheckUnitForBuffs"
Decursive\Decursive-2.7.1.1.lua:853: in function "CheckUnitStealth"
Decursive\Decursive-2.7.1.1.lua:729: in function "ScanEveryBody"
Decursive-2.7.1.1\Dcr_Events.lua:289: in function <Decursive\Dcr_Events.lua:251>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0-6.lua:166: in function <...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0.lua:138>,
LOCALS:
, nil -|count: 1
*****************
461.4040 (h131_w160-11fps-Utgarde Keep): Decursive-2.7.1.1\Dcr_DIAG.lua:196: script ran too long,
STACK:
, Decursive-2.7.1.1\Dcr_DIAG.lua:196: in function <Decursive\Dcr_DIAG.lua:169>
<string>:"safecall Dispatcher[2]":4: in function <string>:"safecall Dispatcher[2]":4
<in C code>
<string>:"safecall Dispatcher[2]":13: in function "?"
libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "Fire"
Decursive-2.7.1.1\Libs\BugGrabber\BugGrabber.lua:146: in function <Decursive\Libs\BugGrabber\BugGrabber.lua:144>
Decursive-2.7.1.1\Libs\BugGrabber\BugGrabber.lua:381: in function <Decursive\Libs\BugGrabber\BugGrabber.lua:328>
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0-6.lua:166: in function <...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0.lua:138>,
LOCALS:
, method = <func> @Decursive\Dcr_DIAG.lua:169
arg1 = "BugGrabber_BugGrabbed"
arg2 = <table> {
message = "<string>:"safecall Dispatcher[1]":9: script ran too long"
time = "2012/09/09 09:40:37"
locals = "(*temporary) = 0.11500000208616
(*temporary) = <func> =[C]:-1
"
stack = "<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
...\Decursive\Libs\..\AceTimer-3.0-6.lua:166: in function <...\Decursive\Libs\..\AceTimer-3.0.lua:138>"
session = 1
counter = 1
}
-|count: 1
Loaded Addons:
_NPCScan (5.0.0.1)
_NPCScan.Overlay (5.0.0.1)
Clique (v50001-1.0.1)
Decursive (2.7.1.1)
GatherMate2 (1.18)
Healers-Have-To-Die (2.0.1)
Quartz (3.1.0)
Recount (N/A)
SilverDragon (v2.6.3)
InterruptSay (3.4.2)
This is fixed in the latest alpha
Please report the content of this window to [email protected] (Use CTRL+A to select all and then CTRL+C to put the text in your clip-board) Also tell in your report if you noticed any strange behavior of Decursive.
2.7.1.1 SHAMAN(85) CT: 678.1230 D: 09/07/12 14:27:46 enUS BGe BDTHFAd: nil nDrE: 1 Embeded: true W: 1 (5.0.4, 16016, Aug 21 2012, 50001)
*****
634.8780 (h55_w58-20fps-Sethekk Halls): Decursive\Decursive-2.7.1.1.lua:254: script ran too long, STACK: , Decursive\Decursive-2.7.1.1.lua:254: in function "PlaySound" Decursive-2.7.1.1\Dcr_DebuffsFrame.lua:1489: in function "SetColor" Decursive-2.7.1.1\Dcr_DebuffsFrame.lua:1161: in function <Decursive\Dcr_DebuffsFrame.lua:1119> Decursive-2.7.1.1\Dcr_utils.lua:572: in function <Decursive\Dcr_utils.lua:570> (tail call): ? <in C code> <string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5 (tail call): ? ...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0-6.lua:166: in function <...\Decursive\Libs\AceTimer-3.0\AceTimer-3.0.lua:138>, LOCALS: , nil -|count: 1
Loaded Addons:
Decursive (2.7.1.1) HealBot (5.0.4.4) DBM-Core (N/A) DBM-LDB (N/A) DBM-Party-BC (N/A)
I heal on a Shaman and a Druid... They both only have one spell for curing/dispelling, but Decursive still wants you to left or right click depending on the debuff, even though it is casting the same spell.
Shaman: purify spirit Druid: Natures Cure (for resto, they changed the name/icon for other specs)
I can't reproduce this issue with the current version of Decursive. It detects the following:
Resto Shamans:
Purify spirit: cures magic and curse
Purge: removes magic on mind controlled unit (ie: not friendly units)
Hex: is used on mind controlled players whose affliction is not caused by a magical debuff
Resto Druids:
Nature's cure: cures Curse, Magic and Poison
Cyclone: used on mind controlled units.