API CastSpellByName is NO LONGER PROTECTED!

[Iaccidentallytwink]

This is more a bug than an exploit, but I accidentally tested an old macro that had CastSpellByName in it and it worked. You can once again use CastSpellByName and it is no longer protected (it was protected since 2.0.1)! Apparently the last patch broke or disabled it's protection. This is an exploit because it is NOT intended to be unprotected.

[TOM_RUS]

It's still protected. Make sure you not running any wow hacks.

[xlAnonym0uslx]

What does this macro do? Just a normal cast?

[Leonim]

I'm not a pro on this kind of things but. What?

[Neer]

I'm not a pro on this kind of things but. What?

No need to be a pro, google does the shiz for you...
API CastSpellByName - WoWWiki - Your guide to the World of Warcraft

[sunshoes]

I'm not a pro on this kind of things but. What?

What does this macro do? Just a normal cast?

Yes, the same parameters as /cast, SpellName, Target, and Rank(Obsolete). However /cast can't be used through LUA, and the function that it calls (CastSpellByName) must be used instead. However, it was protected in 2.0.1 so addons cannot cast spells for you.

As far as I can tell it seems to still be protected though

[thehennyy]

IF castspellbyname would not be longer protected then an addon that shows an spell priority could cast the spells by itself, so you have not to play yourself