»
Aloft (Cataclysm)
| Updated: | 09-02-2010 07:03 PM |
| Created: | 09-02-2010 07:03 PM |
| Downloads: | 1,747 |
| Favorites: | 5 |
| MD5: |
Aloft (Cataclysm)
This version will not contain any new features, it is offered as a means to help "debug" Aloft, so that it is ready to go when Cataclysm is released. This version contains both Aloft and AloftCastWarning. This version will not work under the current production version of WoW (3.X).
Note that I have been able to run the most recent version of SharedMedia successfully under WoW 4.X.
Please report Cataclysm-related problems here in the comments for this addon.
The main Aloft page can be found here here.
Current changes (please help validate):
- abbreviations for Worgen/Goblin race names incorporated (AloftRaceData)
- spellids updated for all forms of crowd control supported by Aloft (AloftCrowdControl)
-----
(Editorial comment: Now that we have a selection of faces/hair+ear styles/etc... Worgen are great, IMO the best thing Blizzard has ever come up with for WoW, from the permanent snarl and glowing eyes to the lopsided mutant motheaten ears; you can trivially generate the most disreputable, psychotic-looking toon you have ever seen. Everyone is in for a real treat. Sadly, i can't seem to stomach Goblins.)
 |
Comment Options |
09-21-2010, 02:32 PM
|
|
|
A Cobalt Mageweaver
 Forum posts: 230
File comments: 1178
Uploads: 5
|
nameplate overlap in Cataclysm
looks like the concept of "nameplate overlap" is basically the default in Cataclysm. the Blizzard standard interface option that enables user control of this is gone.
however, there are (apparently) a couple of console commands, at least at the moment: /console spreadnameplates 0 (will turn on overlap-like behavior) /console spreadnameplates 1 (will turn off overlap-like behavior) this should be a relatively easy Aloft change to make, but i have been unable to find any documentation of this in any of Blizzard's Beta patch notes, and i have NO idea if they intend to keep any of it, so i am going to put off fiddling with this for the moment. i could end up having to disable the whole "overlap" feature, or leave it in place exactly as implemented (i.e. if Blizzard decides to keep it as it is in WoW 3.X). if you have the AutoShow module enabled, Aloft currently generates a (harmless) LUA error related to nameplate overlap.
__________________
Current author/maintainer of Aloft (the nameplate addon) http://www.wowinterface.com/download...AloftBeta.html ----- Yes, Virginia, there is no such thing as permanent free web hosting!
Last edited by acapela : 09-21-2010 at 02:37 PM.
|
|
|
|
09-20-2010, 09:01 PM
|
||
|
A Cobalt Mageweaver
Forum posts: 230
File comments: 1178
Uploads: 5
|
Re: aloftclassdata error
update: digging into the LUA in the Blizzard MPQs for the 2010/09/20 Beta patch (LUA that populates Blizzard's own battlefield score window), it looks like the GetBattlefieldScore() API has not in fact changed: same manifest and order of return values are used (versus WoW 3.3.5 live) in Blizzard's own UI code.
so, there may be a "bug" in GetBattlefieldScore() in Beta right now. i will code Aloft to dump this data as it mines it, and get into a BG and see what i discover. could be that some of these return values got switched around (your error is complaining that class, which should be a string, is actually a number).
i will dig into it and see if i can get this fixed. thanks for the report.
__________________
Current author/maintainer of Aloft (the nameplate addon) http://www.wowinterface.com/download...AloftBeta.html ----- Yes, Virginia, there is no such thing as permanent free web hosting!
Last edited by acapela : 09-20-2010 at 09:43 PM.
|
|
|
|
|
|
09-17-2010, 07:04 PM
|
|
|
A Kobold Labourer
Forum posts: 0
File comments: 17
Uploads: 0
|
aloftclassdata error
10x Aloft-4.0.0-1895-enUS\AloftClassData\AloftClassData.lua:346: attempt to index local 'class' (a number value)
CallbackHandler-1.0-6:147: in function <...oft\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-6:92: in function `Fire' AceEvent-3.0-3 (Aloft):120: in function <...face\AddOns\Aloft\Libs\AceEvent-3.0\AceEvent-3.0.lua:119> im playing on the ptr US server and i can't get rid of this error using aloft 1895(Cata). seems to only show up when playing battlegrounds. i have not tried any raids yet so don't know about that. i have the exact same settings as live i think? maybe im doing something wrong or missing something. thx |
|
|
|
|
WoWInterface
Game Sites
Community
ZAM Network
©2011 ZAM Network LLC
