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
Yes that's right, whenever BugGrabber reports something to me through Decursive, I get lag. I've read others report this too.
And now, it's gone. I knew it was this.
The message is displayed when BugGrabber disables itself (to not degrade performances) due to the great amount of Lua errors it has to handle and format in a short time. So the lag you have disappears completely once the message is displayed.
You'd had even less lag if you disable the incompatible add-ons.
Decursive falls back to its internal error handler when BugGrabber is not found... Unlike BugGrabber, Decursive doesn't disables its Lua error handling when hundreds of errors occur in a short time. Now if you decide to kill Decursive error handler too, you'll find out that your lag will dramatically increase.
The fact that you have this report several times per sessions is not normal though :/
Now, to answer your previous messages, what you are asking me to do is like asking to a mechanic to remove the engine warning light of your car because its constant blinking is annoying...
Other add-ons causing tens of Lua error per second does impact your game performances and can also cause issues within Decursive. (All add-ons run in the same thread and Lua instance).
I know it's easier to cover the smoke and use ear plugs than taking the time to fix the actual issues with your add-ons but you should really consider the later. Add-ons causing this amount of Lua errors are not working as intended...
I use SexyMap too and don't have any Lua errors, you may want to use alpha releases instead (you can select that in the Curse Client).
It sounds like you're just a strong advocate for people running some kind of "check engine" light so you want to try to get more people to have that light by rolling it into a widely used addon, like decursive. While I know it's done with good intentions, I think most people would rather have the personal choice of using your solution, or using their own. I mean honestly... What if several other authors decided they wanted to do the same thing with their popular addons? Suddenly people will have 5 or 6 different bug catchers running with no option to turn the superfluous solutions off.
All i can tell you is that with Decursive running BugGrabber on MY system which is a custom built gaming machine, each time it does its buggrabber functions, my system lags.
WITHOUT IT - No problems.
So that's all I can tell you, from experience, I have NEVER liked buggrabber and have had these issues with it before.
But I'm not here to bash your God.
Point is, you should give the player the option.
I mean for heavens sake, you have BOTH ways programmed IN YOUR CODE.
If buggrabber does not exist go to fall back way (YOUR CODE).
Why not just give us the damn option to force it to not use Buggrabber and use your old way?
In any case, I will be constantly disabling buggrabber from your addon each and every time.
BUT I will always use your addon. =)
PS: My Curse IS set to Alpha releases and I am still getting lua errors for sexy map.
What if I like something else?
It's like force feeding me MacDonalds when I prefer to eat KFC.
OR maybe I don't want to eat at either store instead cook at home?
No
You are missing the point.
THE ENGINE of the car has it's own checks.
WHEN I install a car speaker into my car, the car speaker doesn't have an oil checker built in.
Your ADDON is NOT a bug grabber, it's a cleanser.
I don't ask my battery to check the oil before giving my power to my stereo. I don't ask my stereo to check the oil to play sound through my speaker.
I assume all is working before hand and the speaker will work as intended.
Actually for me, the reverse is true.
If I disable BugGrabber and use your internal error handling, I get ZERO error reports and my lag is NIL.
If I use BugGrabber (what you are FORCING all to use), I get TONS of error reports and my lag increases.
You may have a jacket with a missing button.
The Jacket works fine, keeps you warm, looks good, just has a button missing.
I may choose to never replace that button but do I want to walk around with a sign on the back of the jacket saying, "Button Missing?"
I choose to wear the jacket without the button.
I choose to use Decursive without BugGrabber.
Instead of the car engine alarm analogy I should have used a battery alert one, it would have been more appropriate since the tons of errors you get DOES have an impact on Decursive performances.
Nevertheless you're still driving a car with a loose silencer trailing on the road...
I need to work on finding good analogies... I'm sad to be unable to show you or explain you how doubtful you're reasining is :/
Yes you got zero error reports because you've disabled Lua error reporting in your interface help options.
My point is that your lag will be EVEN MORE 'NIL' if you disable the faulty add-ons.
Instead of ignoring those errors, you should report them to the respective authors, it would be more useful than trying to convince me of adding a 'blinkers' option. (Think about all the reports you could have done during that time...)
So, yes, just delete BugGrabber if you don't care, it's your problem after all. Don't mind editing the embeds.xml, it just adds an error in a log file you're probably not interested in.
And please, to everyone, this page is not made for debates but for comments, next time use the wonderful ticket system available on Wowace.com (you can use your curse.com login there)
Wowace.com also provides a forum for Decursive where this kind of debate can flourish : http://www.wowace.com/addons/decursive/forum/
thanks for using my mod anyway :)
In any event, as sad as it is that you won't be considering giving people that option, I still do love Decursive and the work you have done on it.
I do wish that you were over here in Australia and close to me so that you could experience how smooth and lag free my game is with it off and how it changes when it is on as I believe that would be the only way you would understand that it is the problem and isn't a problem when it's gone.
In any case this debate is obviously going to bounce back and forth in a loop. It is a shame. Oh well. I didn't come here to spam your page though, so for that I am sorry. I just hope you understand that I am but 1 of your users who your choice to force people to use buggrabber has upset and frustrated.
Do take care and keep up the good work on the 'decursive' side of the addon...
=)
That's kind of my point too. I don't want BugGrabber being my error handler. I use another.
Thanks,
Solarwake8