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
@zeman:
you can already bind a key and use a macro (rtfm)
Yoiu shouldn't lose your target, what is your class?
Can you make it where I dont lose my target when I use decurive to remove debuffs? Also if you could make it where you can make a macro like /decursive that uses decursive so you can make a macro where you can put it on a action bar and assign it a key binding so you could for example press "1" every time you wanted to use decurive.
@guest10:
OK, 1.9.8.3 is released and works as you wanted.
http://www.2072productions.com/?to=decursive.php
@Mashonawen:
Unfortunately, it'simpossible, Blizzarrd forbids to test the distance of a unit... I can only know that it is at range of cleansing spells or beyound so 31 yards or 400 yards is the same for Decursive...
@Sumomo:
Decursive suppots warlock' Fellhunter and DoomGuard.
@guest10:
In fact when you start to cast an non-instant spell, there is a global cooldown of about 2 seconds, if you cancel the cast, this ooldown is also canceled but the client needs to know from the server that the spell has been canceled to reset the cooldown so, instead of the 2 seconds cooldown you have a 0.5s cooldown (that depends of your lag).
I'll see if it's possible but I need to make additional modifications if I move the cooldown test before casting. Anyway Decursive is very optimized compared to CT_raid that divides your frame rate by at least 2...
Spells do not need to be cancelled during cooldowns. When global cooldowns have expired, with one key press you can SpellStopCasting() and begin casting a spell (such as a cure) instantly, hence there is no need to cancel any spells during cooldowns since you cannot begin a spell anyway.
I've not looked at it from a UI performance point of view because I glad to say decursive code is pretty efficient (and intelligent too) and I've not faced any UI performance issues while spamming it. Meanwhile, while casting a 2sec or 3sec spell, you're standing still and not doing anything else but waiting for the spell to finish, sadly greater UI performance does not make the casting time shorter neither does spamming decursive make it longer. How long does decursive take to scan a raid of 40 people? I'm glad to say it's faster then you can spam a key.
Spamming decursive is a style of play I'm sure a number of people can relate to, while the "spam decursive" phrase is probably not an uncommon occurrence in raids too. Spamming decursive in anticipation of an incoming debuff is perhaps to cut down on reaction time. It would cause it to check for curable debuffs during each keypress and could deal with it instantly the split second it appeared without the delay of reaction time. Have you had a heal land the split second the MT took a massive blow? Do you always and only start heals in reaction to damage taken? Or do you occasionally have to start heals in anticipation of the expected incoming damage?
I would like to request you consider implementing my previous suggestion and pass it to friends or guild members doing NAX as alpha testers and gather their feedback to see if they can feel the difference in their raid performance. I have and I glad to say the feedback has been encouragingly positive and our raid performance and survivability has certainly improved.
For your continued consideration. BB-IC
i've got a question:
before i download and try this mod, i'd like to know if it works with my warlocks felhunter too? like i can set devour priority etc?
Is it possible to filter by range? For example, I'd rather not see prompts for cures from people who are on the other side of Alterac Valley. Thanks.
@guest10:
yes but Decursive will not cast if there is a cooldown so it will never get there and won't cancel the spell until the cooldown is gone, each time you push your key, Decursive must scan the whole raid. This would degrade performances.
If you have the live-list displayed, you can see and hear when there are debuffs to cure so you don't need to spam your key like a programmable keyboard...
@Mestar:
Well it's very specific and is a part of the game, Decursive is not meant to replace player brains :/
@Powske:
Well this is to show you that someone needs to be debuffed, read the readme.txt file to know how to disable it.
"Abort spells in progress before curing" currently aborts any spell in progress with or without a curable debuff. Could you change this to only abort if a curable debuff is detected instead? This would allow spells to continue casting and decursive can be spammed in anticipation; sometimes you just know a debuff is gonna hit but you still want to continue doing your job (eg healing) while it has not and still be able to spam decursive "on the side" during spell casts.
The current implementation isnt useful with spamming the keybind "on the side", and as commented is "dangerous"; hence my suggestion to replace:
Line 2804: -- if a spell is awaiting for a target, cancel it if ( SpellIsTargeting()) then SpellStopTargeting(); end
with (updated):
if (Dcr_Saved.AbortCurrentCast and Dcr_PlayerClass ~= DCR_CLASS_WARLOCK) then SpellStopCasting() elseif (SpellIsTargeting()) then SpellStopTargeting() end
For your consideration. Thank you.
Since the Itch debuff from the wasps in AQ20 and AQ40 isn't of debuff type poison, would there be some way to have decursive detect this debuff and apply abolish poison so that when it does get converted into the poison, it is removed immediately so the person with the debuff isn't charged and instantly killed. Any chance this feature could be added into the next version?
When im in a raid and someone gets a spell on them a icon of the spell shows up in a little box on my screen, how can i remove this? i turned off everything i could find in options
Please test the new 1.9.8.3 and tell me if purge from Shaman is working. (The download link should appear in the next 20 minutes)
@Tartaris:
Well make sure that Decursive is activated in the addon (where you can choose which character to play with). Also try the /dcrreset command to put all Decursive windows in the middle
@Tricker:
A new version is on its way fixing all the reported issues.
@Archarodim:
im using 1.9.8.2, if there is a newer version, i would be happy to get the link. and btw, it was mentioned earlier and ive experienced it in Strat Baron with my mage, was getting party members cursed but Nothing to Clean from decursive. note that it's not a frequent thing.
Thank you
I tried to DL both version of the newest Decursive and niether are working.. Niether the .exe version or the zip... I have the decursive folder in my addons but none of the /dcr commands work nor does the /decursive macro... any ideas?
I figured out the problem, and it's not decursive (sorry about that!). It turns out the mini-map frame is rectangular, so there's a dead area in the sections not covered by the circle, and I had decursive placed very close to the minimap. I'd never noticed the minimap behavoir before, so I blamed decursive.
If I've experienced the same problem I think I would have fixed it...
PLEASE IGNORE, fixed by clean reinstall
Hi, I'm a 28 mage and have been using decursive for a while, but every time I or a group member gets a curse ad I hit the bound button, all I get is 'Nothing Cleansed'
So obviously something must be wrong, be it with the auto configuration or the functionality in general, i dont know.
Hope you experience the same problem so that it can be fixed.
This error (gsub on line 951) has been fixed in Decursive 1.9.8.1 (in decursive 1.9.8.2 the line 951 is "return false"... you are not using the latest version or you didn't installed it correctly.
(Re-)Install the latest version please
@flowers:
Is it UNDER the decursive bar when it is shown or at the location of the Decursive bar when it is hidden?
@Tricker:
Give me the exact error message please.
I'm getting the same
Interface\AddOns\Decursive\Decursive.lua:951: bad argument #4 to 'gsub' (number expected, got string)
error as posted below. So far I've only noticed it happen in BGs, so maybe its something to do with the new automatic BG raid groups? Also, when it pops up, its not just once, I have to click the button in the message box a LOT of times before it goes away (ie, each time I click it, the same error pops back up). I haven't counted exactly how many times it pops, but it seems about right to be once per raid member.