Mage's Displacement not working in macro

Referred to as “Displacement”, the only one I see in my spell book, it shows the wrong ability stats and it is grayed, doesn’t work. Also shows the blink icon. If I use Displacement manually, dragged onto the action bar from the spell book, it works.

If I make a macro with only Displacement, it shows the right icon and stats, but trying to use it it says “spell not learned”. Something about ranks maybe? I tried “Displacement (Rank 3)” or such, but doesn’t work.

I have it activated in my talent tree!

This is the whole macro:

#showtooltip
/use [mod] Displacement; Shimmer

EDIT: So, this is the base spell:

and this is the one when you talent into Shimmer:

Is there a way to refer to spells in macros using some kind of ID instead of its real name?

1 Like
#showtooltip
/cast [mod,known:389713] Displacement; Blink

Keep in mind that keybinds take priority over macro modifiers. So make sure whichever mod+key combo you’re using doesn’t conflict with a keybind.

  1. Where is the 389713 from?
  2. How would a spell being known work as condition for whether to execute a spell? As I explained, the game does try to execute a spell, but says it is unknown.
  3. Interesting convenience feature: The game executes Shimmer when instructed to execute Blink. I used your macro exactly as written, but identical results.

The problem is that for some reason the game interprets “Displacement” in a macro as an unlearned spell that has the same icon as Shimmer. - I am wondering whether maybe the game expects Shimmer to turn into Displacement once used, as an alternating spell, but because I have Shimmer specced to have two charges, it doesn’t go to Displacement.
But if I Shimmer twice, it still doesn’t trigger Displacement next time.

389713 is the spell id of displacement. The known condition tests if you know a spell.
https://www.wowhead.com/spell=389713/displacement

The only “displacement” im seeing on wowhead with the Shimmer icon is Mark of Displacement.

Do you have the ? selected as the macro icon?

Can try forcing the specificity:

#showtooltip
/cast [mod,known:389713] Displacement(Talent); Blink
1 Like

/use searches for items in your inventory with that name. If it finds one matching it will try to use it. If it doesn’t find an item it will try to find a spell with that name.
/cast looks for spells with that name, and only then looks for items.

So it’s better to use /cast to cast spells and avoid the chance to find an item with that name

1 Like

Executing a talent apparently doesn’t work.
Also, the “known” parameter blocks execution if I use the ID of either uncategorized spell I linked. Only the talent is accepted as known.
The core problem remains: How can I specifically refer to a spell? I find it frustrating that there is that “known” parameter that works, but trying /cast with a spell ID does not work. This is weird, this unspecificity in macro syntax/code. - Also because otherwise macros could be made shorter. If you have an item with a bigass name, putting it in a macro takes up precious space. And I really don’t want to install yet another addon just to have extended macro length. It’s getting messy then.

@Lotimar - Thanks for the tip. I guess I can also save a couple milliseconds of computing by using /cast for spell-only macros. - Sadly doesn’t solve this problem, though.

Tested it on my Mage this morning, it’s definitely bugged.

I haven’t found any method of specifying the correct version of the spell to get it to work in a macro.

Even something as simple as the following isn’t working.

#showtooltip
/cast Displacement

I’ve submitted an in-game bug report, recommend you do the same.

2 Likes

I meant, not for saving time, but for avoiding the macro using an item with a similar name in your inventory instead of the spell.

1 Like

I noticed it’s an old bug:
mages cant cast displacement via macro

2 Likes

WoW a.k.a. SIF (still isn’t fixed)

Reminds me of what normally is only tolerable in alpha development, e.g. Star Citizen.

Yesterday I also encountered the notorious “Are You Kitten Me?” WQ. (Today it probably was a different shard and it wasn’t bugged. It’s hit-and-miss for months now.)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.