WowAce

What steps will reproduce the problem?

1. Enable AddonLoader & the following two mods: Vamp & VampArrow

2. Log on

What is the expected output? What do you see instead?

Expected: those two mods not to load until one of their AddonLoader conditionals are met. In Vamp's case:

## X-LoadOn-Slash: /vamp
## X-LoadOn-Zone: The Sanctum of Blood
## X-LoadOn-InterfaceOptions: Vamp

In VampArrow's case:

## X-LoadOn-Slash: /vamparrow
## X-LoadOn-Zone: The Sanctum of Blood

Instead: they always load "delayed" after logon. Despite none of those conditionals being met.

What version of the product are you using?

r113-release

Do you have an error log of what happened?

No errors.

Please provide any additional information below.

Those mods always loaded properly in WoW 3.x when reaching The Sanctum of Blood ICC zone. When I removed

## X-LoadOn-Zone: The Sanctum of Blood

from both of their TOCs currently, no further problems. They now paid attention to their remaining conditionals on further logons and did not load delayed. So it appears X-LoadOn-Zone: has issues in WoW 4.0.1.

This is happening with other addons as well eg:

EnsidiaFailsWotlk YorsahjAnnounce

Fixed in r120: The problem was GetRealZoneText() can sometimes return nil during login, and that was matching LibBabble-Zone-3.0[zone] which is usually nil on enUS.

This whole mechanism is crap tbh. Should be changed to use map IDs.

Well it works fine now, at least under enUS (I cannot attest for the accuracy of LIbBabble-Zone). This UI has the advantage of being more readable, and thus more feasible for a user to override. I can't imagine any but the most enthusiastic user looking up mapids.