No edit summary |
@DeletedUser40286997 (talk | contribs) (bot; redirecting to Events index) |
||
(9 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
+ | #REDIRECT [[Events#Q]] |
||
− | <noinclude>__NOTOC__{{eventlistheader}}</noinclude> |
||
− | |||
− | |} |
||
− | ===== ===== |
||
− | {| |
||
− | {{evt|QUEST_ACCEPTED|Quest}} |
||
− | |||
− | This event fires whenever the player accepts a quest. |
||
− | |||
− | ; arg1 : Quest log index. You may pass this to [[API GetQuestLogTitle|GetQuestLogTitle]]() for information about the accepted quest. |
||
− | |||
− | {{evt|QUEST_ACCEPT_CONFIRM|Quest}} |
||
− | |||
− | This event fires when an escort quest is started by another player. A dialog appears asking if the player also wants to start the quest. |
||
− | |||
− | ; arg1 : Name of player who is starting escort quest. |
||
− | ; arg2 : Title of escort quest. Eg. "Protecting the Shipment" |
||
− | |||
− | {{evt|QUEST_AUTOCOMPLETE|Quest}} |
||
− | ? |
||
− | |||
− | {{evt|QUEST_COMPLETE|Quest}} |
||
− | |||
− | Fired after the player hits the "Continue" button in the quest-information page, before the "Complete Quest" button. |
||
− | |||
− | In other words it fires when you are given the option to complete a quest, but just before you actually complete the quest (as stated above). |
||
− | |||
− | {{evt|QUEST_POI_UPDATE|Quest}} |
||
− | Fired whenever Quest POIs change. For example after accepting an quest. |
||
− | |||
− | {{evt|QUEST_QUERY_COMPLETE|Quest}} |
||
− | Fired when the data requested by {{api|QueryQuestsCompleted}}() is available. |
||
− | |||
− | |} |
||
− | |||
− | ===== ===== |
||
− | {| |
||
− | {{evt|QUEST_DETAIL|Quest}} |
||
− | |||
− | Fired when the player is given a more detailed view of his quest. |
||
− | |||
− | |||
− | {{evt|QUEST_FINISHED|Quest}} |
||
− | |||
− | Fired whenever the quest frame changes (Detail to Progress to Reward, etc.) or is closed. |
||
− | |||
− | ; arg1 : mousebutton (LeftButton) |
||
− | |||
− | |||
− | {{evt|QUEST_GREETING|Quest}} |
||
− | |||
− | Fired when talking to an NPC that offers or accepts more than one quest, i.e. has more than one active or available quest. |
||
− | |||
− | |||
− | |} |
||
− | ===== ===== |
||
− | {| |
||
− | {{evt|QUEST_ITEM_UPDATE|Quest}} |
||
− | |||
− | Fired when the quest items are updated |
||
− | |||
− | |||
− | {{evt|QUEST_LOG_UPDATE|Quest}} |
||
− | |||
− | This event is fired very often. This includes, but is not limited to: viewing a quest for the first time in a session in the Quest Log; (once for each quest?) every time the player changes zones across an instance boundary; every time the player picks up a non-grey item; every time after the player completes a quest goal, such as killing a mob for a quest. It also fires whenever the player (or addon using the CollapseQuestHeader or ExpandQuestHeader() functions) collapses or expands any zone header in the quest log. |
||
− | |||
− | |||
− | {{evt|QUEST_PROGRESS|Quest}} |
||
− | |||
− | Fired when a player is talking to an NPC about the status of a quest and has not yet clicked the complete button. |
||
− | |||
− | {{evt|QUEST_WATCH_UPDATE|Quest}} |
||
− | |||
− | Fired just before a quest goal was completed. At this point the game client's quest data is not yet updated, but will be after a subsequent QUEST_LOG_UPDATE event. |
||
− | |||
− | ; arg1 : questIndex (not watch index) |
Latest revision as of 22:58, 9 May 2018
Redirect to: