Ike

Could you elaborate? Not reliably, no. If there are multiple NPCs with the same name then there's no way of telling who's the one casting the spell.

No need to worry! I will keep fixing bugs if they are reported and I'm even willing to add new things if someone has a neat idea!

No, I'm afraid not. I tried since I also made the jump to TBC, but many of the functions used to make this work are no longer available or only in a very limited way.

There's currently no tooltip support available to the public. My local version has an experimental implementation but it's too unreliable right now. And regarding [swimming]: As far as I'm aware there are no API functions that tell me whether you're swimming or not. I could ghetto it by checking whether your breathing bar is displayed but that would be more of a [diving] then, wouldn't it? If anyone knows a way please let me know! Not right now, no. Why would you need this anyway? I'm asking since Decursive exists and that pretty much takes care of all your decursing needs. First of all, CheckInteractDistance doesn't check if you're in melee range. The range index 3 means 10 yards while melee distance is 5 yards. If this weren't the case I would have already implemented a conditional for melee range! But oh well. If this doesn't bother you since it's the closest you can get with the vanilla client, then I'd do it this way: Create 3 Macros "Master", "Ranged" and "Melee". "Master" should look like this: /run if(CheckInteractDistance("target", 3)) then CastModifier.ExecuteMacroByName("Melee") else CastModifier.ExecuteMacroByName("Ranged") end "Ranged": /cast !Auto Shot "Melee": /cast [mypower>60] Raptor Strike With this, you can spam "Master" all day long and it'll do exactly what you want if I didn't make any typos. There's no need for a database. You can do this pretty easily by using GameTooltips. function GetUnitDebuffInfo(unit, i) SomeTooltip:ClearLines(); SomeTooltip:SetUnitDebuff(unit, i); local name = SomeTooltipTextLeft1:GetText(); local type = SomeTooltipTextRight1:GetText(); return name, type; end Et voila, the debuff's name and its type! But again, I don't see why I should put this in the Addon since Decursive is a thing. But maybe I'm missing something, so please let me know what you're trying to do!

Another small update with a few new Conditionals: attacks (Wiki) isplayer / isnpc (Wiki) @jagonx: You're now able to create your macro. Would you mind sharing with me what you're trying to do? I'm genuinely curious why you'd need to see if your target is specifically a player.

The issue with your macro is that after checking for Rake you immediately cast Claw without checking anything. This will skip the last condition. Also, if you want to cast Attack if you don't have the energy for your other abilities, you need to tell the Client in the Macro to do so. Also, you mustn't put commas between conditions. A plain old white space does the job. Here's how I'd do this: /cast [combat nostealth] !Attack /cast [mypower<40] !Attack /cast [stealth mypower>49] Pounce /cast [harm nodebuff:Rake mypower>39] Rake; [mypower>44] Claw This does what you want. Attack when you're in combat and not prowling. Attack when you do not have enough energy for any of your abilities. Cast Pounce if you're in stealth and have enough energy. Cast Rake if your target is hostile if it has no Rake debuff and you have enough energy. If any of these fail, cast Claw as long as you have the energy to do so. The "mypower"s in the last two lines are optional, but using them gets rid of the "I don't have enough energy" spam. This was a limitation of the early macro calling implementation. You weren't able to use conditionals when calling another Macro. However, I've just implemented this in the current version! Using it, you could rewrite my macro from above like this: Master: /cast [combat nostealth] {AA} /cast [mypower<40] {AA} /cast [stealth mypower>49] Pounce /cast [harm nodebuff:Rake mypower>39] Rake; [mypower>44] Claw AA: /cast !Attack

Don't think that's possible as that function requires an action and not a macro. I'll have a look at it though when I find the time to dig into it. 1) Not sure if that's possible for the same reasons mentioned above. But I'll give it a shot. 2) How would you use such a condition? This sounds like a very niche use-case. From your edit message, I gather that you got the macros working? Because they look sound to me. Should be fixed. Thank you once again!

Big update! You're now able to combine multiple modifiers! (Wiki) You can now invoke other Macros from another Macro! (Wiki) Added [no]cooldown Conditionals! (Wiki) Added [no]channeled Conditionals! (Wiki) Fixed a bug that caused /use to not use equipped items! Fixed a bug that caused buff names not to be fully parsed! Make sure to re-download the Addon! Two things: 1) I introduced a parsing bug in the last updates. Should be fixed now, so please re-download the Addon! 2) You can not use white spaces in between the square brackets []. You have to use "_" instead. So make sure to replace "[nomybuff:Aspect of the Hawk]" with "[nomybuff:Aspect_of_the_Hawk]" @jagonx @PrioR @Meitie @Makonha

1) There was indeed a bug here! Thank you for reporting this, it should be fixed now! 2) This macro can't work like that because in Vanilla you can not switch from one form to another without leaving your current form first. So something more like this would be appropriate: /cast [stance:0]Cat Form;[stance:1]Dire Bear Form;[stance:2]Aquatic Form;[stance:4]Travel Form;[nocombat nostealth]Prowl 3) But since that isn't really nice, I've added the new chat command "/unshift" which also supports all Conditionals! You can use it like this: /unshift [stance:1/2/4] /cast [stance:0] Cat Form; [nocombat nostealth] Prowl This makes it a lot easier to understand what is actually going on! This is a really cool idea! I've implemented it like this: /cast [@target type:Beast] Hibernate; Entangling Roots For more information take a look at the wiki. These pages in particular: https://github.com/DennisWG/CastModifier/wiki/unshift https://github.com/DennisWG/CastModifier/wiki/cast-Conditionals#typecreaturetypeid

You might want to take a look at my CastModifier addon. It provides you with a wide array of new macro functionality including mouseover support for all mainstream unit frames addons.

Are you sure this just happened after updating and that this Addon is the cause of the error? I'm asking because I've done nothing that could've caused this error to appear.

Oh, my bad! I missed two lines when I pushed the update to Github. Should work fine now!

Quick update: Fixed a bug where only the partial name of a buff was checked for the [no][my][de]buff conditional Implemented support for NotGrid (thank you @Cha for bringing it to my attention) Implemented support for FocusFrame (thank you @jagonx for bringing it to my attention) @Alsorin shift works fine. See: You have to make absolutely sure that you don't have the shift + button combination bound. Just bind it to some unused action and then unbind it again with the "Unbind Key" button. Press "Okay" and try it again. If that doesn't help try disabling all other Addons and see if it then works. If it does turn them back on one by one and see which one causes the issue. Report your result back to me please, so that I can try and fix any possible incompatibilities.

@jmul1212 https://github.com/DennisWG/CastModifier/wiki/Supported-AddOns ClassicFocus is 100% supported. But ClassicFocus has its limits like it can't differentiate between two NPCs with the same name. If you're using it for unique NPCs or other Players, though, it works like a charm!

I don't think that either [swimming] or [mod:altgr] are possible. [form] is the same as [stance], so you can just use that instead. I can't use "/cast Faerie Fire (Feral)" even if I disable all Addons which means that this is a limitation of the 1.12 client and therefore not doable. This one is odd. Here I was thinking I created the greatest thing ever that no one else thought of. Spooky how he even started working on it around the same time I did. Not sure about pmana for druids, though. Sounds pretty complicated when taking things like mana regeneration into account. Could you provide me some examples on how you'd use this? I might divert some time into this if I can see a good use case. /petattack [@mouseover harm nodead]; [@target] Attack any enemy living mouseover target or, when there is none, the current target.