WoW BlueTracker Home | RSS | News | Contact
Recent | Search | Archive | CS Posts
Poster: Ziana at 3/29/2006 8:58:46 AM PST
Subject: CastSpellByName() errors - 1.10 help Slouken?
   Posting this here in the hopes Slouken might take a personal interest.

Prior to 1.10:

This macro worked fine:
/cast Prowl
/cast Shadowmeld

It would shadowmeld the player, and IF a pet was out, AND the pet had prowl, the pet would prowl. If either weren't true, nothing would happen; the /cast prowl line was ignored.

Now with 1.10

If the pet is dismissed, or the pet doesn't have Prowl, an error message box pops up: "CastSpellByName(): Couldn't find spell named Prowl".

The behavior of CastSpellByName has changed, in a bad way. Previously it would simply ignore unavailable spells, now it generates an intrusive error.

Additionally:
CastSpellByName("Smite") works
CastSpellByName("Smite(Rank 1)") works
CastSpellByName("Smite(Rank 4)"), when rank 4 is not known, generates an error.

This will cause many problems for simple macros players used to cast spells.

Suggested solutions:
• Simply ignore any CastSpellByName for unavailable/unknown spells.
• Display on-screen feedback such as "Spell unavailable" similar to messages like "You have no target"

[ post edited by Ziana ]


Hunter Issues: http://tinyurl.com/7vjmd
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=345574&p=#post345574
 
Poster: slouken at 4/12/2006 5:10:28 PM PDT
Subject: Re: CastSpellByName() errors - 1.10
  

Q u o t e:
This was fixed in 1.10.1. Thanks SO much Slouken!!


Stealth fix! Nerf! Nerf!!!
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=345574&p=#post359173

View all recent official Blue Posts

WoW Blue Tracker: Archiving World of Warcraft Blue Posts
since March 2005
Home | RSS | News | Contact
Recent | Search | Archive | CS Posts
 

Why Ads?