m
→AddOns: Recategorized until we have more questions
m (→Census: added some stuff) |
m (→AddOns: Recategorized until we have more questions) |
||
| Line 34: | Line 34: | ||
; Q) Where do I start if I want to write an AddOn? | ; Q) Where do I start if I want to write an AddOn? | ||
: A) Try the [[WoW UI Customization Guide]] as a starting point. | : A) Try the [[WoW UI Customization Guide]] as a starting point. | ||
;Q) Where do I start with these XML files? | |||
:A) Try the [[XML User Interface]] guide - its full of useful information! | |||
; Q) How do I reload my UI? | ; Q) How do I reload my UI? | ||
: A) Type /console reloadui or /script ReloadUI(); | : A) Type /console reloadui or /script ReloadUI(); | ||
;Q) What is Lua? | |||
:A) See the [[Lua]] page for some basic details. | |||
;Q) How do I know what verion number to use in the .toc files? | ;Q) How do I know what verion number to use in the .toc files? | ||
:A) | :A) When you launch the game, it's listed in parenthesis after the version number (e.g. <tt>Version 1.2.1 (4150)</tt>. If you dont have access to the game you could check on the [http://forums.worldofwarcraft.com/board.aspx?forumName=wow-interface-customization WoW Interface Customization forum] or the [http://cosmosui.org/forums CosmosUI forums] for the latest information. Alternatively, use WinMPQ to read the .mpq files, check the Patch.MPQ file and lookup the number in Interface\FrameXML\FrameXML.toc | ||
==Function Questions== | |||
;Q) Why doesn't [[API UnitDebuff|UnitDebuff]] accurately report the spell I just cast? | ;Q) Why doesn't [[API UnitDebuff|UnitDebuff]] accurately report the spell I just cast? | ||
:A) There is a ~0.5 second gap between the end of a spell being cast and its associated debuff texture showing up on the unit upon which it was cast. This gap causes problems for "Smart Cast" scripts which try to prevent a spell like Immolate from being run when the target already has the debuff on it. If there is a pause between casting, the script would work; however, if the script is triggered rapidly then it is likely to try to cast Immolate twice (since it does not yet see the debuff on the target unit). The workaround for this problem is to subscribe to the SPELLCAST_STOP event. Every time that event is triggered, store the [[API GetTime|current time]] in a variable. From then on, whenever you subtract the [[API GetTime|current time]] from the stored time of the last SPELLCAST_STOP event, you get the time (in seconds) since the last spell stopped. If that time is greater than 0.5, you can proceed to cast your spell. If not, do not cast your spell. Note: this is not an issue for instant cast spells (their debuffs seem to be immediately noticeable), therefore it would be inefficient to do this check on them. | :A) There is a ~0.5 second gap between the end of a spell being cast and its associated debuff texture showing up on the unit upon which it was cast. This gap causes problems for "Smart Cast" scripts which try to prevent a spell like Immolate from being run when the target already has the debuff on it. If there is a pause between casting, the script would work; however, if the script is triggered rapidly then it is likely to try to cast Immolate twice (since it does not yet see the debuff on the target unit). The workaround for this problem is to subscribe to the SPELLCAST_STOP event. Every time that event is triggered, store the [[API GetTime|current time]] in a variable. From then on, whenever you subtract the [[API GetTime|current time]] from the stored time of the last SPELLCAST_STOP event, you get the time (in seconds) since the last spell stopped. If that time is greater than 0.5, you can proceed to cast your spell. If not, do not cast your spell. Note: this is not an issue for instant cast spells (their debuffs seem to be immediately noticeable), therefore it would be inefficient to do this check on them. | ||
==Questions on Specific AddOns== | ==Questions on Specific AddOns== | ||
| Line 63: | Line 61: | ||
===Thottbot=== | ===Thottbot=== | ||
---- | ---- | ||