Quantcast

* Currently in patch 2.2 Blizzard changed the unit attribute resolution. As a result, a unit attribute of "nil" is different from a unit attribute that has never been set. This release works around this issue by only setting the attribute if you've set it in your configuration.

Author James Whitehead II <jnwhiteh@gmail.com>
Author date 2007-09-27 18:18:24
Author local date 2007-09-27 18:18:24 +0000
Committer James Whitehead II <jnwhiteh@gmail.com>
Committer date 2007-09-27 18:18:24
Committer local date 2007-09-27 18:18:24 +0000
Commit a38a2a0b84f91e16c4121bf1f8360555de38f78a
Tree 41b38af2bd868c3f8f631d8443f5b1db576d0e76
Parent 6d11be7d0ccf2508016df87793e30427e256b058
* Currently in patch 2.2 Blizzard changed the unit attribute resolution.  As a result, a unit attribute of "nil" is different from a unit attribute that has never been set.  This release works around this issue by only setting the attribute if you've set it in your configuration.
* If you set the "unit" argument for a given custom type, and then clear it, you will need to reload your UI in order to get teh change applied.  This should not affect the average user in any way.