"PLAYER_ALIVE" Alternative?

[suicidalkatt]

Is there any particular reason why PLAYER_ALIVE doesn't fire on log in?

I've read the events to which it fires, but using it in the addon load sequence hasn't worked for me.

It just simply isn't triggering.

Any ideas?

[nightcracker]

I personally use "PLAYER_ENTERING_WORLD" for pretty much everything exept savedvar for which I use "ADDON_LOADED".

[Xrystal]

I used PLAYER_ENTERING_WORLD as well as VARIABLES_LOADED. I use ADDON_LOADED when I need to but most of the time I can avoid it.

[Dridzt]

PLAYER_ALIVE fires for first logon but not for ReloadUI.

As a rule of thumb:
If you need to delay initialization of something on a clean start (entering the game from the account selection level) you can use PLAYER_ALIVE as it will fire after PLAYER_ENTERING_WORLD.

If you need to do the same after a reload (or entering the game after logging out to the character selection screen only) you can use PLAYER_ENTERING_WORLD and it will have the same effect.
(things that might not be available to the client at P_E_W on a clean start will be after a reload and for the rest PLAYER_ALIVE is usually delayed enough)

Bottomline if you need to use one of them, use both and unregister when you've done what you want to do.

[Ailae]

Yeah, Dridzt is right, it will only fire on a "cold" login so to speak. If you're using PLAYER_ALIVE to know when talents are available you can register for PLAYER_ENTERING_WORLD and when it fires do this:

if (GetNumTalentTabs() == 0) then
    frame:RegisterEvent("PLAYER_ALIVE")
else
    -- talents are available already, so this was probably a /reload. 
end

[SDPhantom]

I usually use PLAYER_LOGIN. It fires when everything's ready and only fires at loading.