m
added minor note on quest information becoming available after the PLAYER_ALIVE event
(Merge of Events that fire during the loading process and UI code load order) |
m (added minor note on quest information becoming available after the PLAYER_ALIVE event) |
||
| Line 69: | Line 69: | ||
# [[Events P (Party, Petition, Pet, PlayerBank, Player)#PLAYER_ALIVE|PLAYER_ALIVE]] | # [[Events P (Party, Petition, Pet, PlayerBank, Player)#PLAYER_ALIVE|PLAYER_ALIVE]] | ||
#* This event fires after [[Events P (Party, Petition, Pet, PlayerBank, Player)#PLAYER_ENTERING_WORLD|PLAYER_ENTERING_WORLD]] | #* This event fires after [[Events P (Party, Petition, Pet, PlayerBank, Player)#PLAYER_ENTERING_WORLD|PLAYER_ENTERING_WORLD]] | ||
#* Talent information should now be available to the UI | #* Quest and Talent information should now be available to the UI | ||
Until 3.0, VARIABLES_LOADED used to fire upon completion of the addon loading process; since 3.0, it is fired in response to CVars, Keybindings and other associated "Blizzard" variables being loaded, and may therefore be delayed until after PLAYER_ENTERING_WORLD. The event may still be useful to override positioning data stored in layout-cache.txt | Until 3.0, VARIABLES_LOADED used to fire upon completion of the addon loading process; since 3.0, it is fired in response to CVars, Keybindings and other associated "Blizzard" variables being loaded, and may therefore be delayed until after PLAYER_ENTERING_WORLD. The event may still be useful to override positioning data stored in layout-cache.txt | ||