WoW:API CastSpellByName - Revision history

Move page script: Move page script moved page API CastSpellByName to WoW:API CastSpellByName without leaving a redirect

2023-08-15T04:45:14Z

Move page script moved page API CastSpellByName to API CastSpellByName without leaving a redirect

← Older revision

Revision as of 04:45, 15 August 2023

WoWWiki>Egingell: /* Notes */

2009-08-18T18:12:12Z

Notes

← Older revision		Revision as of 18:12, 18 August 2009
Line 20:		Line 20:
	* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.		* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.
	* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.
	* You ''can'' still use this function outside of secure code to open trade skill windows.		* You ''can'' still use this function outside of secure code to open trade skill windows and to summon non-combat pets and mounts.
	** Apparently not anymore. <tt>CastSpellByName("Inscription")</tt> would do nothing when called from my addon.

WoWWiki>Krellmax: /* Notes */

2009-06-13T19:23:03Z

Notes

← Older revision		Revision as of 19:23, 13 June 2009
Line 21:		Line 21:
	* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.
	* You ''can'' still use this function outside of secure code to open trade skill windows.		* You ''can'' still use this function outside of secure code to open trade skill windows.
			** Apparently not anymore. <tt>CastSpellByName("Inscription")</tt> would do nothing when called from my addon.

WoWWiki>Egingell at 06:43, 26 November 2008

2008-11-26T06:43:13Z

← Older revision		Revision as of 06:43, 26 November 2008
Line 20:		Line 20:
	* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.		* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.
	* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.
			* You ''can'' still use this function outside of secure code to open trade skill windows.
	~~It was previous claimed that~~ this ~~could still be used~~ to open ~~craft~~ windows ~~and activate lock picking, but opening craft windows with an unprotected call is no longer possible. Lock picking is as of yet unconfirmed~~.

WoWWiki>TinyEditor: /* Notes */

2008-09-04T11:40:48Z

Notes

← Older revision		Revision as of 11:40, 4 September 2008
Line 21:		Line 21:
	* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.

	~~Although~~ this ~~function is protected, you can~~ still ~~use it~~ to open ~~Craft~~ windows and activate Lock ~~Picking~~.		It was previous claimed that this could still be used to open craft windows and activate lock picking, but opening craft windows with an unprotected call is no longer possible. Lock picking is as of yet unconfirmed.

WoWWiki>Egingell: Caveat

2007-02-27T14:19:09Z

Caveat

← Older revision		Revision as of 14:19, 27 February 2007
Line 20:		Line 20:
	* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.		* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.
	* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.

			Although this function is protected, you can still use it to open Craft windows and activate Lock Picking.

WoWWiki>Starlightblunder: 2.0.1 protected note

2006-12-16T11:33:42Z

2.0.1 protected note

← Older revision		Revision as of 11:33, 16 December 2006
Line 1:		Line 1:
	~~<center>'''CastSpellByName''' ''-Documentation by Sliver-''<~~/~~center>~~		{{wowapi}}
	~~----~~		{{protectedapi\|2.0.1\|For alternatives, try [[API_SecureTemplates\|Secure Template]] or the new [[Conditional slash commands#/cast\|/cast]].}}
	~~;''Arguments''~~

	:( ~~name~~{, onSelf})		CastSpellByName(spellName{, onSelf});
	:;~~name : String - Spell Name(as seen when mouse-over).~~
	~~:;onSelf : Value - Any value or nil.~~

	~~----~~		==Arguments==
	;~~''Returns''~~		:;name : String - Name of the spell to cast. Rank is optional, if omitted, highest possible is picked automatically.
	:~~;nil~~		:;onSelf : Boolean - Should the spell be cast on the player (vs target)? If no target exists and the onSelf evaluates to false, cursor is switched to casting mode.
	~~---~~-
	~~;''Example''~~
	~~:( syntax )~~
	:;~~CastSpellByName("spellname(Rank X)")~~
	:~~;CastSpellByName~~(~~"spellname"~~)
	~~:;CastSpellByName("spellname"~~, ~~onSelf )~~


	~~CastSpellByName('Life Tap(Rank 2)')~~		==Example==
	~~----~~
	~~;''Result''~~

	~~: Casts Life Tap~~ (~~This example is warlock specific~~)~~. When the~~ (Rank X) ~~string is omitted, the ''highest rank of the spell which the user has in his spellbook'' is cast~~. ~~''This is not true for Stone creation spells~~ (~~i.e.~~ "~~Create Firestone~~")~~, because they do not use~~ "~~ranks~~"~~.''~~		CastSpellByName("Flash Heal(Rank 2)"); -- Cast Flash Heal (Rank 2) on target.
	----		CastSpellByName("Flash Heal"); -- Cast Flash Heal (Highest rank) on target.
	~~;''Description''~~		CastSpellByName("Flash Heal",1); -- Cast Flash Heal (Highest rank) on self.

	~~: Casts a spell by the spells given name.~~		==Notes==
			To cast spells that contains parentheses in the spell name, such as "Create Healthstone (Major)" and "Faerie Fire (Feral)", it's necessary to either specify rank or add () to the end of the spell name, like:
	~~----~~		CastSpellByName("Faerie Fire (Feral)()");
	~~;''~~Notes~~:''~~		You might encounter difficulties when using this on a localized version of WoW.
	: To cast spells that contains parentheses in the spell name, such as "Create Healthstone (Major)" and "Faerie Fire (Feral)", it's necessary to either specify rank or add () to the end of the spell name, like: CastSpellByName("Faerie Fire (Feral)()").		* See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.
	: You might encounter difficulties when using this on a localized version of WoW.		* This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.
	: See the [[HOWTO:_Localize_an_AddOn#Unicode\|Unicode part]] of the Localization HOWTO for more details about editing a source file containing localized strings.

	: This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.

	:In patch 1.10, this function operates when called From Button presses, Slash Commands and '''some''' Events. (PLAYER_TARGET_CHANGED is the only one i have found, but there may be more, i assume Events that are called In reaction to Player's Actions are those that work).

	~~:This function can not be called by an AddOn itself. You need a hardwareevent (mouse or keyboard) to activate the function.~~

	~~----~~

	~~{{Template:WoW API}}~~

WoWWiki>Chef de Loup at 11:19, 8 September 2006

2006-09-08T11:19:38Z

← Older revision		Revision as of 11:19, 8 September 2006
Line 37:		Line 37:

	:In patch 1.10, this function operates when called From Button presses, Slash Commands and '''some''' Events. (PLAYER_TARGET_CHANGED is the only one i have found, but there may be more, i assume Events that are called In reaction to Player's Actions are those that work).		:In patch 1.10, this function operates when called From Button presses, Slash Commands and '''some''' Events. (PLAYER_TARGET_CHANGED is the only one i have found, but there may be more, i assume Events that are called In reaction to Player's Actions are those that work).

			:This function can not be called by an AddOn itself. You need a hardwareevent (mouse or keyboard) to activate the function.

	----		----

	{{Template:WoW API}}		{{Template:WoW API}}

WoWWiki>LudiKalell2 at 16:48, 28 July 2006

2006-07-28T16:48:39Z

← Older revision		Revision as of 16:48, 28 July 2006
Line 15:		Line 15:
	:;CastSpellByName("spellname(Rank X)")		:;CastSpellByName("spellname(Rank X)")
	:;CastSpellByName("spellname")		:;CastSpellByName("spellname")
			:;CastSpellByName("spellname", onSelf )

WoWWiki>The Nerd Wonder: punctuation fix

2006-06-04T12:12:24Z

punctuation fix

← Older revision		Revision as of 12:12, 4 June 2006
Line 35:		Line 35:
	: This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.		: This problem does only appear when working with Lua source files. When you're using macros, inside the WoW client, it should work in unicode directly.

	:In patch 1.10, this function operates when called From; Button presses, Slash Commands and '''some''' Events. (PLAYER_TARGET_CHANGED is the only one i have found, but there may be more, i assume Events that are called In reaction to Player's Actions are those that work.)		:In patch 1.10, this function operates when called From Button presses, Slash Commands and '''some''' Events. (PLAYER_TARGET_CHANGED is the only one i have found, but there may be more, i assume Events that are called In reaction to Player's Actions are those that work).

	----		----

	{{Template:WoW API}}		{{Template:WoW API}}