WoW:Events/V: Difference between revisions

1,322 bytes added ,  15 August 2023
m
Move page script moved page Events/V to WoW:Events/V without leaving a redirect
No edit summary
m (Move page script moved page Events/V to WoW:Events/V without leaving a redirect)
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
{{evt|VARIABLES_LOADED|System}}
{{evt|VARIABLES_LOADED|System}}


Fired during the loading phase of the UI to indicate that the Saved Variables of all AddOns that will be loaded during the initial load (or reload) of the UI have have been read into memory from their files.
Fired in response to the CVars, Keybindings and other associated "Blizzard" variables being loaded.  Since key bindings and macros in particular may be stored on the server they event may be delayed a bit beyond the original loading sequence.


Note that using this event means that your addon can not be loaded on demand properly. It is better to use ADDON_LOADED and test for arg1 being the name of your addon.
Previously (prior to 3.0.1) the [[Events V-Z (Variables, Who, World, Zone)#VARIABLES_LOADED|VARIABLES_LOADED]] event was part of the loading sequence.  Although it still occurs within the same general timeframe as the other events, it no longer has a guaranteed order that can be relied on.  This may be problematic to addons that relied on the order of [[Events V-Z (Variables, Who, World, Zone)#VARIABLES_LOADED|VARIABLES_LOADED]], specifically that it would fire before [[Events P (Party, Petition, Pet, PlayerBank, Player)#PLAYER_ENTERING_WORLD|PLAYER_ENTERING_WORLD]].
 
Addons should not use this event to check if their addon's saved variables have loaded.  They can use ADDON_LOADED (testing for arg1 being the name of the addon) or another appropriate event to initialize, ensuring that the addon works when loaded on demand.
 
{{evt|VEHICLE_ANGLE_SHOW|Vehicle}}
?
 
{{evt|VEHICLE_ANGLE_UPDATE|Vehicle}}
?
 
{{evt|VEHICLE_PASSENGERS_CHANGED|Vehicle}}
?
 
{{evt|VEHICLE_POWER_SHOW|Vehicle}}
?
 
{{evt|VEHICLE_UPDATE|Vehicle}}
?
 
{{evt|VOICE_CHANNEL_STATUS_UPDATE|Voice}}
?


{{evt|VOICE_CHAT_ENABLED_UPDATE|Misc}}
{{evt|VOICE_CHAT_ENABLED_UPDATE|Misc}}
Line 12: Line 32:


{{evt|VOICE_LEFT_SESSION|Misc}}
{{evt|VOICE_LEFT_SESSION|Misc}}
{{evt|VOICE_PLATE_START|Voice}}
?
{{evt|VOICE_PLATE_STOP|Voice}}
?


{{evt|VOICE_PUSH_TO_TALK_START|Misc}}
{{evt|VOICE_PUSH_TO_TALK_START|Misc}}
Line 20: Line 47:


Fired when you release the Push-To-Talk hotkey
Fired when you release the Push-To-Talk hotkey
{{evt|VOICE_SELF_MUTE|Voice}}
?


{{evt|VOICE_SESSIONS_UPDATE|Misc}}
{{evt|VOICE_SESSIONS_UPDATE|Misc}}
Line 33: Line 63:
Fired when someone stops using Voice Chat
Fired when someone stops using Voice Chat
; arg1 : The [[API_TYPE_UnitId|UnitId]] of the person who stopped talking
; arg1 : The [[API_TYPE_UnitId|UnitId]] of the person who stopped talking
{{evt|VOTE_KICK_REASON_NEEDED|Looking for Group}}
Fires when you need to supply a reason for the kick vote you wish to initiate. Use {{api|UninviteUnit}}("name", "reason") to provide the reason.
; arg1 : String - name of the player you wanted to initiate a kick vote for.
|}
Anonymous user