Spell Name Changes (Immolate = Corruption)

[ssiard]

It is either bugged or Blizzard has internally changed the names of spells to support the new talent system. What I have found is that the internal name of the warlock spell "Immolate" is "Corruption".

I basically have a mini addon to call SetBinding to implement all of my key bindings. On live, the following works

/script SetBindingSpell("3", "Immolate")

This would bind Immolate to key 3. On MOP Beta, I have to do the following to bind Immolate to key 3

/script SetBindingSpell("3", "Corruption")

Another is to use Shadow Bolt to bind Incinerate. I'm finding this out by using the following function and passing in spell book ids.

function PrintName(inputIndex)

   local skillType, spellId = GetSpellBookItemInfo(inputIndex, BOOKTYPE_SPELL)

   if (spellId ~= nil) then

      DEFAULT_CHAT_FRAME:AddMessage(spellId)

   end

   local name, rank, icon = GetSpellInfo(spellId)

   if (icon ~= nil) then

      DEFAULT_CHAT_FRAME:AddMessage(icon)

   end

   if (name ~= nil) then

      DEFAULT_CHAT_FRAME:AddMessage(name)

   end

end

I haven't found a good programmatic way to this as

name = GetSpellInfo("Immolate")

returns Immolate and not Corruption.

[p3lim]

This seems like a bug

[Xrystal]

Maybe not, they did do quite a bit of Warlock changes so I wouldn't be surprised if they renamed a few to make them make sense.

[p3lim]

Even if they renamed anything, having two apis return different names for the same spell is a bug.

[Xrystal]

Ah I see, I misunderstood, thought they had changed the name of the spell as well.

[Zorben]

This also happens with frost strike <-> blood strike and asphyxiate <-> strangulate for DKs

[Gethe]

Originally Posted by Zorben asphyxiate <-> strangulate for DKs

This, I'm sure, is due to the fact that Asphyxiate is a Talent and will replace Strangulate if you take it.

[Maul]

Originally Posted by Zorben This also happens with frost strike <-> blood strike and asphyxiate <-> strangulate for DKs

Just confirmed this as well this morning. If you create a macro - "/cast blood strike" - but you are in frost spec, it will show as Frost Strike on the action bar and actually cast Frost Strike.

[Shabaella]

Anyone figured out a way to work arround this yet?

I'm working on a Shaman add-on and the Earthbind Totem and Earthgrab Totem have the same problem.

It get's worse since I have to create a button with it, the IsSpellInRange only works with Earthbind Totem id, even if I have Earthgrab, but the GetSpellCooldown only works with the Earthgrab Totem id, and since I use LibActionButton, I couldn't make this work yet.

Also the flyout info for this totem is kind of broken, here is a what I'm getting for it's return. Look that it now has a new object returning as the second variable(it's only spellId and isKnown on live).

-- With Earthgrab Totem
spellId, somethingNew, isKnown = GetFlyoutSlotInfo(79, 1)
-- spellId is 2484 - Earthbind Totem id
-- somethingNew is 51485 - Earthgrab Totem id
-- isKnown is true

spellId, somethingNew, isKnown = GetFlyoutSlotInfo(79, 2)
-- spellId is 51485 - Earthgrab Totem id
-- somethingNew is 51485 - Earthgrab Totem id
-- isKnown is false

-- Without Earthgrab Totem
spellId, somethingNew, isKnown = GetFlyoutSlotInfo(79, 1)
-- spellId is 2484 - Earthbind Totem id
-- somethingNew is 2484 - Earthbind Totem id
-- isKnown is true

spellId, somethingNew, isKnown = GetFlyoutSlotInfo(79, 2)
-- spellId is 51485 - Earthgrab Totem id
-- somethingNew is 51485 - Earthgrab Totem id
-- isKnown is false