Decursive’s options are not directly available in the « Interface » panel due to ongoing tainting issues Blizzard is not willing to fix. I was wondering if there’s a way to stop decursive from telling me that I’m having so and so LUA errors. In reply to Galthera: For other videos about Decursive, see the YouTube playlist. Am very new to macro creation so I kinda scratch my head about your macro, but it looks like any click on a MUF will Remove Curse being Priority 1 , and cntl click will Counterspell, while shift click does Remove Curse seems redundant no?
|Nom:||add on decursive|
|Système d’exploitation:||Windows, Mac, Android, iOS|
|Licence:||Usage Personnel Seulement|
For suggestions, feature request, or bug report , use the ticket system provided by WoWAce. All Decursive alert colors can be modified making it suitable for color-blind people. Just got Decursive, darista’s guide seriously helped! This should be fix in the latest alpha:. It’s because it’s already listed as an example Control what and who you want to dispel:
I don’t think many people use this. Turned off hide muf’s and saw it’s mouse bindings are set that way, so I should be good to go tonight is my second ToT progression run and I was told I have to be able to cure the curse happening to team members on the fourth deccursive of Horridon, hence a tad extra anxiety.
Just got Decursive, darista’s guide seriously helped!
Files – Decursive – Addons – Projects – WowAce
Decursive for World of Warcraft
In brief, what you get with Decursive is effectivenessa player using Decufsive will always dispel faster than other players. Any help would be awesome thanks!
For other videos about Decursive, see the YouTube playlist. The regular macro Decursive creates as a « mouseover » macro you can use on any unit or unit portrait you can bind it to a key. It’s because it’s already listed as an example In reply to kenji Dfcursive reply to Galtherawas wondering if i was the only one having this issue.
Your cleansing spell Cooldown is displayed to maximize your dispel speed.
It seems that it is editable whether I have « Allow internal Simply read the tool-tips in Decursive’s option panels, they should explain everything you need to know on each and every settings.
Indeed, I did manage to deccursive Curse first, then Charm, so the feedback in the Custom Spell panel should be correct.
Last edited by kenji Tired to go back to default by « Removing » it so the Custom Spell panel was blank, then re-added it back into the Add Custom Spell text field via spellbook and it still comes with the red asterisk. Special sound alert when Unstable Affliction is detected and you’re about to dispel it. Actually I just tested and you’re out of luck, there is a bug specifically with Counterspell where it ignores the « Allow macro editing » option.
I did mean ‘editing’, this typo will be fixed in the next release, thanks for noticing: Which test function are you talking about? Quote from BrightBrown Saw that there was a subsequent beta to what I think you referred to as an alpha named beta xxx, so assumed a true alpha so I installed beta 4 latest file posted.
I was wondering if there’s a way to stop decursive from telling me that I’m having so and so LUA errors. Likewise, I too am having this issue. Ah, got back the Counterspell without the red asterisk.
Decrusive can’t seem to find any information, how can this be integrated into the MUFs because those are party members, not evil targets. A complete Decursive guide by darista: I’ve made corrections in the latest alpha, please try it if you can: An automatic blacklist will prevent you from loosing time on players who can’t be dispelled.
Decursive supports all classes with cleansing abilities and configures itself automaticallyit works straight out of the boxno configuration is required.
The mouseover macro and the MUF macros are different and unrelated I should clarify that as well in the option panels.
How does this help me to decusive a mob? Development versions of Decursive are available at this URI: Am very new to macro creation so I kinda scratch my head about your macro, but it looks like any click on a MUF will Remove Curse being Priority 1and cntl click will Counterspell, while shift click does Remove Curse seems redundant no?