I've discovered a strange behavior with the event order during the login/load process.
A simple addon with only one frame and the events below registered does fire the events in different orders.
Login in while out of combat and /reload in combat:
VARIABLES_LOADED
PLAYER_LOGIN
PLAYER_ENTERING_WORLD
SPELLS_CHANGED
So far so good.
Login in while in combat:
SPELLS_CHANGED
PLAYER_LOGIN
PLAYER_ENTERING_WORLD
PLAYER_REGEN_DISABLED
SPELLS_CHANGED
VARIABLES_LOADED
VARIABLES_LOADED is the last event that is fired? Wtf?
Since Patch 3.0.2, VARIABLES_LOADED has not been a reliable part of the addon loading process. It is now fired only 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.
/edit: if you're looking for an event that fires when your addon's saved variables have loaded, that event is ADDON_LOADED.
__________________
"You'd be surprised how many people violate this simple principle every day of their lives and try to fit square pegs into round holes, ignoring the clear reality that Things Are As They Are." -Benjamin Hoff, The Tao of Pooh