2.7.2-745
- separated the existing AutoShow options into their own "player state" category, added a "player location" category (governing where the player is), made nameplate show contingent on the validity of one condition from each category
- refactored target tracking (for target-of-target and etc), extracted it to its own "always loaded" module, preparatory for using it in cast warning and PvP glow functionality
- got rid of options allowing user to disqualify race/class/raid-target as discriminators in target tracking (target-of-target); always use all of them
- made a variety of small changes to improve load-order processing of "dynamic" modules, hopefully will help with tag error messages
- changed Nameplate Glow logic to use a global Ace2 repeating event (rather than a frame OnUpdate hook), cleaned up code
- updated to latest/greatest version of Ace2

2.7.1-715
- changed checks for Broker2FuBar/FuBar2Broker: when Broker2FuBar is present, Aloft's LDB support is disabled (use Aloft's FuBar support directly); when FuBar2Broker is present, Aloft's FuBar support is disabled (use Aloft's LDB support directly)
- updates to zhCN/zhTW localization, courtesy of digmouse
- applied some syntatic changes to localization files, in preparation for recombining them back into a single/combined file; watch for "No translation" errors

2.7.0-667
- should have upped the version number to 2.7.x when i added the "AutoShow" functionality; this release should have been another bug-fix release for that major version
- AutoShow functionality is now a "dynamic module"; enable it under Aloft "Modules" options; this also changes the organization of SavedVariables, so once enabled, you will need to configure your "Auto Show" options again (menus will appear under the standard Aloft nameplate show/hide options when the module is enabled)
- AutoShow now has a "Set All" capability, under the relevant options; enabling this will apply changes to any AutoShow options for neutral/hostile (or friendly), nameplates apply to all options for the same type of nameplate (this applies to use of keybindings as well)
- TagCompiler-1.0 has been tweaked slightly, pending some interaction with its author(s), to generate empty strings when ~Tag/Not(Tag)/ColorIf()/etc conditions evaluate to "false"; please watch for unwanted side-effects in your text tags
- fixed intermittent LUA errors in AloftThreat and AloftStackedPointText modules
- enhanced to avoid status-change announcements when changing "Visibility" options or selecting/deselecting "dynamic" modules
- saw only occasional PvP titles on cross-realm players in my testing, so have disabled player title gathering for cross-realm units, so that realms are not confused with titles; will revisit this again later (should be possible to detect the realm in the player tooltip and parse around it, needs more experimentation)

2.6.5-644
- enhanced "Show Nameplate"/"Show Friendly Nameplate" functionality to control basic nameplate visibility automatically/conditionally on behalf of the user: on combat, on resting, on being grouped (and a default for when these conditions don't apply); a new feature, please watch for problems
- backed out optional dependencies on FuBar, Broker2FuBar, FuBar2Broker, and the mainstream Broker display addons (Carousel, Fortress, NinjaPanel, StatBlockCore)
- updated to latest/greatest FuBarPlugin-2.0 embedded library (r9 from WoWAce, which has gone back to being FuBarPlugin-2.0)
- fixed some typos in the ruRU localization (thanks to McFLY for the helpful report)

2.6.4-631
- made FuBar, Broker2FuBar, FuBar2Broker, and the mainstream Broker display addons (Carousel, Fortress, NinjaPanel, StatBlockCore) as optional dependencies, to enforce load order; if this is "bad" (you there, Phanx? :-), let me know, and i can back it out
- added an AceAddon-2.0 "InitializeAddon()" invocation to the load process for Aloft's FuBar and LibDataBroker dynamic modules; these are actually full/separate addons, not just Aloft modules, and initialization must be driven manually when they are loaded
- fixed bugs (FuBar/Broker libs not in TOC; Nameplate Glow color processing which was causing a LUA error; Crowd Control Bar default background color, which was inconsistent with other default background colors)
- updated to latest/greatest FuBarPlugin-2.0 embedded library (r7 from WoWAce, which is actually now FuBarPlugin-2.1)

2.6.3-617
- fixes and enhancements to AloftPlayerTitle module; player titles are somewhat dynamic, but it is now possible to cache the most recently seen prefixes/suffixes between sessions (look at Aloft "Data Options"; defaults to disabled); mouseover/target action will update them

2.6.2-612
- incorporated "ruRU" translations; thanks to Xisraa/Henrietta; i have no good way to test localizations, so: users of Russian-language WoW clients, please feel free to mouseover all menu items, proofread the text and watch for LUA errors, and report anything you see
- added "AloftPlayerTitle" dynamic module; this enables two new text tags: [PlayerTitlePrefix] and [PlayerTitleSuffix] (for leading and trailing titles, so you can format them accordingly); scrapes tooltips on mouseover/target action, watch for inaccuracies, especially on rapid mouseover
- re-applied "simple" fixes/workarounds to changes to unit level and name that occur "behind Aloft's back"; dropping and re-aquiring target should update name/level text
- added border/border color, spell icon, spell name/rank text, and remaining spell time text to crowd control bar (NOTE: Aloft crowd control subsystem has restrictions, read project description and FAQ)
- reorganized crowd control module options, to make them consistent with other "bar" functionality (mana/threat/castbar, etc); changes to SavedVariables have occurred, you will need to reconfigure your "Crowd Control" options
- added "color transition" to stacking point debuff text (lacerate/sunder); text counter will change slowly through a continuous range from one color to another as the debuff slowly counts down; the two colors at each end of the range are user-selected, defaults set to cyan (at maximum remaining time) and red (at minimum remaining time)
- reorganized stacking point debuff options (changes to menu organization only), to make consistent with other "text" functionality; there should be no changes to existing SavedVariables (though there is an extra color in the options now, for the color transition capability)
- enhanced creature type processing to "assume" any neutral level 1 NPC with <= 8 maximum health is a "critter"; this will not catch all critters (but should catch most typical ones); this may cause problems with other NPCs, please report any errors
- re-named the Aloft "AloftSpellNameText" module to "AloftCastBarSpellNameText", for consistency; the module will need to be re-enabled, no changes to SavedVariables
- AloftPresets is now a dynamic module; if you want access to presets, enable the module via the "Modules" options

2.6.1-570
- backed out "simple" initial fixes/workarounds to changes to unit level and name that occur "behind Aloft's back", pending more thorough analysis/testing of framerate/update issues
- made border/border color separate/independent options on each of cast bar, mana bar, and threat bar

2.6.0-559
- rolled all Aloft functionality back into a single addon folder, and implemented a poor-man's "dynamic load" mechanism (like that used by Prat; kudos to Sylvanaar)
- enhanced AloftStackedPointsText module to permit combo points on any class (e.g. dailies and Malygos raid encounter; nod to Gnarfoz for identifying this problem); needs testing
- enhanced AloftStackedPointsText module to sense druid form changes, and switch from lacerate count to combo point count on the fly
- enhanced cast bars, mana bars, and threat bars to use the same border/border color settings as the health bar (which is controlled under Aloft "Frame" options)
- added functionality to re-apply visibility settings at end of combat (in case nameplates disappear/reappear during combat lockdown)
- critters should be hideable via "Visibility" options;
- attempted simple initial fixes/workarounds to changes to unit level and name that occur "behind Aloft's back"

2.5.2-403
- separated additional Aloft functionality out of the core addon: FuBar_AloftFu, Broker_Aloft, AloftClassIcon, AloftCombatText
- separated ComboPointsText functionality out of core addon, renamed to "AloftStackedPointsText", added Lacerate and Sunder support (available for Druid, Rogue, and Warrior appropriately)
- separated Polymorph/ShackleUndead functionality out of core addon, combined and renamed to "AloftCrowdControl", added Banish support (available for Mage, Priest, and Warlock appropriately)
- provided "invert" options under "Nameplate Glow" and "Threat Bar>Threat Flash", to enable glows in the "opposite" fashion (i.e. when player does not have aggro, or when threat is below threshold)
- added a couple of new "glow" textures, selectively truncated so they do not obscure elements of the nameplate
- made the new "ThreeQuartersSoftOutline" texture the default for threat flash

2.5.1-367
- made the "enUS" locale unconditional in the new Aloft "child" addons, as the default locale; this should get rid of the "translation does not exist" errors seen in 2.5.0-342
- added options to allow the user to control class colors (these default to the Blizzard colors, and can be reset to these defaults)
- added a couple of new "glow" textures, selectively truncated so they do not obscure elements of the nameplate
- made the new "ThreeQuartersSquareGlow" texture the default for aggro glows

2.5.0-342
- began the process of teasing Aloft apart into separate modules (which the user can physically disable if desired); no bugs fixed, really
- broke out AloftThreat Data/Bar/Text and AloftMana Data/Bar/Text functionality as separate modules
- enhanced AloftTags.rtf document to specify which modules originate which text tags (which will become increasingly important as this modularity increases)
- implemented AloftHealthBarDeficit optional module (which converts existing health bars to display a health deficit, growing from the right as health is lost); enabled via "Aloft>Health Bar>Deficit Health Bar" option, disabled by default
- updated to latest/greatest embedded libraries (LibRoster-2.1, which added "vehicle" as a valid unit; vehicles in groups not yet tested with Aloft, report any issues)

2.4.6-315
- checked over code used to monitor changes to group events (pet/party/raid), delegated completely to LibRoster-2.1
- fixed typo in use of UnitClass() method that was causing class validation on nameplate identification to fail
- fixed typo in mouseover vs. target class information gathering
- added some normalization of class names (normalized to the namespace returned in the second value of UnitClass(), and the class names in the RAID_CLASS_COLORS global), just in case parts of the non-localized Blizzard API and/or LibBabble-Class are inconsistent (i.e. return "DEATHKNIGHT" or "Death Knight" variously), etc
- added Runes/Runic Power to "[PowerTypeColor]" tag color table, enhanced to gather power type (as a string) from UnitPowerType(), added "[PowerTypeName]" and "[ShortPowerTypeName]" tags
- updated use of Blizzard's GetBattlefieldScore() to match new return value/order
- updated to latest/greatest versions of embedded libraries (LibBabble-Class-3.0), removed some older/unused versions of libraries

2.4.5-293
- checked over code used to calculate "[HealthFraction]|[ManaFraction]|[ThreatFraction]", fixed defects and made basic method of calculation consistent

2.4.4-288
- beefed up things like class/race/classification/creature-type/is-pet collecton/assignment to incorporate further cross-checking (including class colors on underlying Blizzard nameplates), to help disambiguate and/or clean up nameplates for hunters/pets when hunter and pet are named the same
- applied LUA's intrinsic math.ceil() to the calculation of the "[HealthFraction]" tag value, to insure fractional health does not show "0%" when targets actually still have health (for bosses, this could be a lot of health)
- added Death Knight as a class (esES locale users beware, LibBabble-Class-3.0 has no localizations for Death Knight)
- added Runic Power as a power type
- did small bits and pieces of code refactoring and cleanup here and there

2.4.3-261
- added Broker2FuBar and FuBar2Broker as optional dependencies, to force load order so that Aloft can sense their presence
- coded both LibDataBroker and FuBar support to sense the presence of the other guy's broker and disable itself if present
- if neither of the FuBar/LDB brokers are present, both FuBar and LDB support will load (and presumably not interfere with each other); if both are present, Aloft will offer neither FuBar nor LDB support; "/aloft waterfall" will have to be used
- enhanced Class Data collection to treat the color of a hostile nameplate as an indication of class when ShowClassColorInNameplate CVar is enabled by the user; colors are not apparently exact, so had to jump through some hoops
- fixed pernicious typo in global use of variable "profile" (which should have been declared local), which was breaking FuBar_LuckyCharms
- enhanced FuBar plugin to refresh Dewdrop when nameplates are "redisplayed" (primarily a function of Visibility options); this was ultimately yet another framerate-related update/delay issue (it is possible to bounce the ShowClassColorInNameplate CVar "too fast", programmatically from an addon)
- fixed bug in redisplay functionality that inadvertantly set all nameplates visible (basic options) when Visibility options were twiddled
- updated to latest/greatest versions of embedded libraries

2.4.2-244
- updated embedded libraries (looks like very minor TOC change(s))
- integrated with ShowClassColorInNameplate CVar and "beefed up" class-based information gathering and checking, so that health-bar colors and color text tags for hostile PvP targets will be checked and updated properly (i.e. as documented in AloftTags.rtf)
- addressed some very cryptic framerate-related update/delay issues induced by changing the ShowClassColorInNameplate CVar with live/actively-displayed nameplates; hopefully these are dealth with, but please watch for artifacts (i.e. "[HealthBarColor]"/"[OriginalHealthBarColor]" and health bar colors themselves not updating correctly)
- enhanced FuBar plugin to refresh Dewdrop when nameplates are "redisplayed" (primarily a function of Visibility options); this was ultimately yet another framerate-related update/delay issue (it is possible to bounce the ShowClassColorInNameplate CVar "too fast", programmatically from an addon)
- fixed typo in advanced color tags example in AloftTags.rtf; added hex color code for DeathKnight to AloftTags.rtf
- implemented class icon system (request from WoWAce user, and it was easy enough, once i knew where to go for the icon art)

2.4.1-221
- removed native LibDataBroker-1.1 (LDB) support; per user suggestion, those wishing LDB support should use Broker2FuBar
- fixed typo in ReportStatusChanges

2.4.0-215
- added LibDataBroker-1.1 (LDB) support, with mouseover status and shift-click waterfall instantiation (like the FuBar support); my LDB display of choice is Carousel
- fixed typo in FuBar support
- experimented with and cleaned up Frame dimension options, to allow nameplates to be more closely tiled on-screen (packing height/width) and to permit healthbar borders to be inset slightly (plain height/width)
- went ahead with SpellID-based implementation of GetSpellInfo (kudos to gix, who proposed it); my mage only has sheep-based polymorph, so i have no real means of experimenting with this purely via spell name
- shackle and polymorph timers will now attempt to identify active debuffs on the player's current target and retroactively attach a timer bar when the nameplate comes into range, even when the "speculative" option is disabled
- cast bar color may now be specified; looks like obvious enhancements, like coloring the cast bar according to spell school, and other such things, could be difficult
- looked into player titles... nothing in the Blizzard API lets you query them for other players; will investigate tooltip data as a workaround

2.3.1-201
- too much of a rush job; fixed the stupid typo; this version is identical to Aloft-2.3.1.200 except for the single typo
- my apologies, should have done my usual release test process

2.3.1-200
- a bit of a rush job, testing focused primarily on FuBar and ReportStatusChanges bugs; report any other problems and they will be addressed ASAP
- fixed various bugs in FuBar support
- fixed various bugs related to ReportStatusChanges
- updated embedded libraries, incorporated original TOCs and licensing as a means of providing author credit
- deprecated LibBabble-Spell-3.0, trying GetSpellInfo() instead; those in non-enUS locales, please see if your Polymorph and Shackle timers have localized spell names in them
- upgraded to LibGratuity-3.0 (tooltip scraping), though this is not searchable on Curse and is listed as a "beta"; watch for problems identifying vendor comments and pet owner names

2.3.0-174
- implemented experimental hostile target-of-target system, both for PvP targets generally and for instance targets that have a raid target assignment (only PvE requires raid target assignment); use the "[TargetName]" tag as usual
- the target-of-target system actually does require raid target assignments in PvE; PvE targets without raid target assignments will be ignored by the target-of-target system; race and class are sufficient in PvP (raid target assignments are not expected but will hurt nothing)
- watch for perceived "inefficiency" in the target-of-target system (UI pausing every 15 seconds to so) while in crowded PvP environments, or even in PvE environments; disable the feature if desired
- applied several bug fixes (Alpha subsystem typo, pet Visibility, Aggro "glow" color management)
- went into an AV game, and saw health bar colors, color text tags, and the "[Class]" text tag working "properly" on Aloft hostile player nameplates
- Aloft "Health Bar>Colors>Color Hostile by Class" and "Combat>Class Colors in Nameplates" options , as well as "[HealthBarColor]" and "[OriginalHealthBarColor] tags, work fairly intuitively together
- restored FuBar support (tested with FuBar 3.5)
- race data is now updated regularly from the battlefield score (like class data)
- added key bindings for Aloft (enable/disable friendly nameplates), bindings toggling each of enemy/friendly/all; these will replace the default Blizzard nameplate bindings and interact with "Report Status Changes"

Aloft-2.2.0.154:
- Aloft is still an Ace2 mod; the intended Ace3 port is on hold for the moment
- the latest/greatest Ace2 is embedded in this release
- i have seen no library conflict or "incompatibility" with the "large" addons i have used in testing (Pitbull 3.2.6, XPerl 3.0.0h, IceHUD 1.3.6, Omen3 RC1, Prat 3.0, Macaroon, Cartographer), all of which embed various libraries
- Aloft now uses the Blizzard(tm) default threat API exclusively (Threat-2.0 has not yet been updated, and it may in fact now be superfluous, even for area threat)
- the numbers flowing from the default threat API seem to be behaving better than they did on the PTR, conforming to 100% threat as an upper limit
- APIs like MobHealth3/LibMobHealth-4.0/MobInfo2 are no longer required for health estimation; Blizzard's underlying nameplate implementation, as well as its UnitHealth API, both now seem to offer explicit/accurate health values at all times
- having said this, MobInfo2 may remain useful as a means of tracking drop rates and etc; however, i have no idea if its author is still around
- there is a new "Nameplate Glow" feature, which accurately emulates the default Blizzard(tm) nameplate glow (a target-of-target capability, useful in AOE tanking)
- the "Nameplate Glow" feature is independent of the Aloft threat module, slaved to Blizzard(tm)'s nameplate glow; alas, the texture region used by Blizzard(tm) does not seem to use hookable methods (e.g. Show() and Hide()), so it seems i must micromanage this
- the "Nameplate Flash" feature that attempted to emulate this "Nameplate Glow" remains a component of the Aloft threat module, and activates on grouped nameplates when maximum threat is reached (resembling the Banzai module, but graphically different)
- i went into GIMP and created some additional soft-edged/airbrushed-looking outline textures for these "Glow" and "Flash" effects; they are controlled by the "Style" parameter of the respective options
- there exists some duplication of function between these various types of glow, but they do mean slightly different things, so try them out and see how you like them
- a new "Acapela" preset has been added; this reflects how i configure Aloft; it is best used in conjunction with SharedMedia (for textures and fonts)

Aloft 2.1.2.109-WotLK
- regressed embedded Ace2 library AceComm-2.0 to main r82173 (from WotLK branch r79554)
- updated zhCN and zhTW translations, courtesy of volunteer "digmouse" (thanks again!)

Aloft 2.1.1.103-WotLK
- fixed bug(s) in collection/display of combo points
- simplified/improved group threat calculation/display
- fixed bug in calculation of ThreatFraction value
- Blizzard(tm) threat values seem to be squirrely

Aloft 2.1.0.95-WotLK
- revised nameplate handling for WoW 3.x
. new nameplate frame heirarchy
. CVar processing
. conditioning of obsolete hooks
- updated to sense and use Blizzard(tm) native threat API, if it is present
- disabled Blizzard(tm) native WotLK nameplate "threat flash" feature
. no way to re-use their texture or control the placement of their texture region
. re-implemented as an Aloft feature, which can be selectively disabled (though the native feature remains turned off)
- added "threat flash" capability for nameplates
. a logical duplication of existing Banzai functionality, but resembles Blizzard(tm) native WotLK nameplate behavior
- included various mob health APIs and LibStub as optional dependencies
- enhanced to sense and use any of MobHealth3, LibMobHealth-4.0, and MobInfo2, in that order of preference
- added target change handling for grouped units (including solo pets); affects the TargetName tag for grouped units
- disabled FuBar for the duration of the transition to Ace3 and WoW 3.x
- enhanced various update events to fire on a "next frame" delay
- made certain unitids are being cleared when they should.
- got rid of Babble-2.x usage and embedded libraries
- updated to use LibBabble-Class-3.0, and embedded this library
- updated to use LibBabble-Spell-3.0, and embedded this library
- updated to use LibSharedMedia-3.0, and embedded this library
- updated Ace2 embedded libraries to current WotLK versions
- removed MaxThreatName tag
- enabled GroupTargetCount data collection and text tag to operate at all times
- added a GroupTargetCount example to tag documentation
- updated some debug instrumentation
- updated translation notes to request assistance

known problems; various forms of the following (presumably an artifact of using WotLK versions of Ace2):

the above does not occur on the PTR (WoW 3.0.2)

Aloft 2.0.1.49
- implemented internal event to trigger text update on changes to health bar color.
- fixed typo in alpha hook method name.
- refactored to centralize health bar color change processing in a single method.
- simplified some of the debug API method names.
- commented out debugging.

Aloft 2.0.0.27
- Initial BETA release.