Game limitations. And yes, they name their pet the same as themselves for exactly that purpose. (Exploiting things like /tar name, DPS meters, nameplate bars, etc.) You can report players that have named their pet the same as themselves, by the way, since it is an exploit.
By the way, it's been nearly a month and the bug I've mentioned several times that occurs every time I play has not even been mentioned.
I'm getting tired of reporting the same bug over and over. In terms of support, this mod appears dead. Can ANYONE please fix this bug? I have tried fixing it myself but I don't know enough LUA. It seems like a small bug that would be easy to fix for the person that actually wrote it, but there's been no response to this issue, at all, not even a "I'll work on it when I'm done with this" or something.
For someone who knows LUA, it should be a simple fix. It's just a nil error, for crying out loud. I just don't know enough about matrixes (or whatever the this.that variables are) to fix it.
I notice this in PvP / Arena (and I believe it's intentionally exploited by players that name their pet with the same name as their character, or their team's healer): If a pet has the same name as a player, the pet's name plate is colored by the player's class.
The result can be confusing, especially in a crowd, as there will be two green (for Hunter) "Joehunter" nameplates to pick from.
Are there some settings I should change to eliminate this, or is it a known bug, or maybe there's nothing Aloft can do about it due to game limitations?
Thanks!
Start by always reporting those hunters, its considered an exploit and is not alowed (GM's will force rename those pets).
It's not a game limitation, but nonetheless an issue that affects many addons, simply because they weren't written the possibility in mind that if there is a priest named Randomguy, that the name Randomguy will always belong to the priest. All addons which use RosterLib suffer from this problem, including Aloft, and numerous addons that don't use RosterLib still suffer from it because they don't do anything special to separate players and pets who may share names.
Aloft-r69497\Modules\CombatText.lua:167: bad argument #1 to 'unpack' (table expected, got nil)
I've been getting this whenever I have Combat Text displayed - anything I can do about it?
This part of Aloft still seems to use the old combat log format (and libs who parsed this). I disabled that module it for now. Until Aloft gets updated to 2.4 there is nothing to do about it i guess.
This part of Aloft still seems to use the old combat log format (and libs who parsed this). I disabled that module it for now. Until Aloft gets updated to 2.4 there is nothing to do about it i guess.
Ok, thanks. Pity there's a problem - here's hoping someone who knows what they're doing will take an interest.
Yes, no part of Aloft has actually been updated for 2.4. Roartindon, the author of Aloft, has been very busy with work and a cross-continental move, and has not yet had time to update any of his addons for WoW 2.4. A member of his guild did post in a thread about another of his addons that Roartindon does intend to update his addons, but that he currently doesn't even have time to play WoW much. Be patient.
Yes, no part of Aloft has actually been updated for 2.4. Roartindon, the author of Aloft, has been very busy with work and a cross-continental move, and has not yet had time to update any of his addons for WoW 2.4. A member of his guild did post in a thread about another of his addons that Roartindon does intend to update his addons, but that he currently doesn't even have time to play WoW much. Be patient.
Yeah, I'm not being impatient, just finding out what's up :) I realise all these mods are written by dedicated people in their own time for no financial gain - and I appreciate that.
Yeah, it was more directed at the posters further up the page going on about how "I reported this bug weeks ago but it still hasn't been fixed". Plus, it seems nobody reads more than the 1 or 2 posts at the end of the thread before posting, so... :P
I have this problem with Aloft that's been driving me crazy :p I don't know if it's the 2.4 patch, but it doesn't seem to save my "show" settings.
Namely, I have it show neutral/friendly NPCs but not PCs... and it works. Then I die, or I instance in, or *something* happens and it reverts back to showing PCs anyway.
It's not that hard. There is a nice text file with a list of tags and some examples. Comes with either Aloft or its tags library. DogTags are more powerful, tho, but then again, the DogTag lib is a lot bigger, too.
Are there any alternatives to Aloft, btw? I know it's not nice to ask this in Aloft's thread, but I am thinking about checking out alternatives until Aloft gets some love again. Haven't found any, tho. I vaguely seeing one when browsing wowi some time ago, but I couldn't find it again when I started looking actively for it.
Edit: Can't find the textfile I mentioned right now. Either I am stupid, or it was moved. ^^ I am hunting for the examples right now...
Edit2: Found it, it's called AloftTags.rtf and sits in Aloft's base directory. It seems to be missing from the no-ext version, tho.
It's not that hard. There is a nice text file with a list of tags and some examples. Comes with either Aloft or its tags library. DogTags are more powerful, tho, but then again, the DogTag lib is a lot bigger, too.
Are there any alternatives to Aloft, btw? I know it's not nice to ask this in Aloft's thread, but I am thinking about checking out alternatives until Aloft gets some love again. Haven't found any, tho. I vaguely seeing one when browsing wowi some time ago, but I couldn't find it again when I started looking actively for it.
Edit: Can't find the textfile I mentioned right now. Either I am stupid, or it was moved. ^^ I am hunting for the examples right now...
Edit2: Found it, it's called AloftTags.rtf and sits in Aloft's base directory. It seems to be missing from the no-ext version, tho.
would be nice thou to have the option to ue dogtags, especially since many of us already have dogtags through other addons.
And to me it just seems that is would compliment the Dogtag suite (we already have unit frames and tooltips using DogTags).
I must confess I find AloftTags fairly limited, yet still confusing (probably just used to DogTags too much now). While the RTF lists the Tags and conditionals, it's not providing much by way of example.
I don't know if this response is still applicable (its from quite a bit earlier in the thread), but regarding using Dogtags in Aloft:
Quote from: Cal on May 30, 2007, 05:15:45 pm
Just a question.. what is the function difference between what your TagCompiler library does and what DogTag does? From their description they appear to fill the same roll.
DogTag is a tag compiler that produces and handles strings for unitids.
TagCompiler is a tag compiler that determines strings, raw values or numeric values for a generic set of data. It does not handle updating strings. I had to write this, because Aloft does not have unitids to work with, so cannot use DogTag.
Ahh thank you Grita. Such a pity, but I guess at least it'll stop me wasting my time(!)
I've been trying to decipher the Aloft Lua's (on and off) for a couple of days to see if it's feasable. No luck of course, as my talent for addon coding is dire to say the least. I picked up the WoW addon programming book more or less just for this reason.
I guess it also accounts for why there are no alternatives. He's pulled off an amazing addon that only really has two shortcomings for me. (The inability to call DogTags, and the inability to set click-through*)
Thank you though Grita, it's good to know. Believe me I did read the entire thread, but I don't know how I missed this.
:)
*I have my Aloft plates set to transparent apart from the name text. It's murder trying to click on auctioneers/NPC's as the mouse always gets snagged on an invisible part of a nameplate.
Is it a huge undertaking to get Aloft to call for DogTags3.0 rather than AloftTags ?
Aloft uses the TagCompiler library instead of the DogTag library. This means that Aloft defines its own tags, rather than relying on the library to define the tags. I would strongly prefer that Aloft did not use DogTag; DogTag is massive, and would result in a significant performance hit for people who don't already use a DogTag-based addon. It's also hugely overkill for a nameplate... you don't need more than 2-3 texts on a nameplate, and all of them should be fairly simple. I can't think of a single useful nameplate text that isn't easily possible with the tags Aloft provides.
Quote from reeks »
It's murder trying to click on auctioneers/NPC's as the mouse always gets snagged on an invisible part of a nameplate.
You do know you can interact with NPCs by right-clicking their nameplate, right? ;)
By the way, it's been nearly a month and the bug I've mentioned several times that occurs every time I play has not even been mentioned.
I'm getting tired of reporting the same bug over and over. In terms of support, this mod appears dead. Can ANYONE please fix this bug? I have tried fixing it myself but I don't know enough LUA. It seems like a small bug that would be easy to fix for the person that actually wrote it, but there's been no response to this issue, at all, not even a "I'll work on it when I'm done with this" or something.
For someone who knows LUA, it should be a simple fix. It's just a nil error, for crying out loud. I just don't know enough about matrixes (or whatever the this.that variables are) to fix it.
Start by always reporting those hunters, its considered an exploit and is not alowed (GM's will force rename those pets).
I've been getting this whenever I have Combat Text displayed - anything I can do about it?
This part of Aloft still seems to use the old combat log format (and libs who parsed this). I disabled that module it for now. Until Aloft gets updated to 2.4 there is nothing to do about it i guess.
Ok, thanks. Pity there's a problem - here's hoping someone who knows what they're doing will take an interest.
Yeah, I'm not being impatient, just finding out what's up :) I realise all these mods are written by dedicated people in their own time for no financial gain - and I appreciate that.
Namely, I have it show neutral/friendly NPCs but not PCs... and it works. Then I die, or I instance in, or *something* happens and it reverts back to showing PCs anyway.
Any idea how this could be fixed?
I'm a complete beginner at addon coding and was hoping to do this myself, but instantly found the code daunting.
This would be nice, still haven't figured out how to use aloft tags :/
Are there any alternatives to Aloft, btw? I know it's not nice to ask this in Aloft's thread, but I am thinking about checking out alternatives until Aloft gets some love again. Haven't found any, tho. I vaguely seeing one when browsing wowi some time ago, but I couldn't find it again when I started looking actively for it.
Edit: Can't find the textfile I mentioned right now. Either I am stupid, or it was moved. ^^ I am hunting for the examples right now...
Edit2: Found it, it's called AloftTags.rtf and sits in Aloft's base directory. It seems to be missing from the no-ext version, tho.
would be nice thou to have the option to ue dogtags, especially since many of us already have dogtags through other addons.
And to me it just seems that is would compliment the Dogtag suite (we already have unit frames and tooltips using DogTags).
I must confess I find AloftTags fairly limited, yet still confusing (probably just used to DogTags too much now). While the RTF lists the Tags and conditionals, it's not providing much by way of example.
..OKAY so I'm just a DogTag whore/CkKnight fanboy
I've been trying to decipher the Aloft Lua's (on and off) for a couple of days to see if it's feasable. No luck of course, as my talent for addon coding is dire to say the least. I picked up the WoW addon programming book more or less just for this reason.
I guess it also accounts for why there are no alternatives. He's pulled off an amazing addon that only really has two shortcomings for me. (The inability to call DogTags, and the inability to set click-through*)
Thank you though Grita, it's good to know. Believe me I did read the entire thread, but I don't know how I missed this.
:)
*I have my Aloft plates set to transparent apart from the name text. It's murder trying to click on auctioneers/NPC's as the mouse always gets snagged on an invisible part of a nameplate.
Aloft uses the TagCompiler library instead of the DogTag library. This means that Aloft defines its own tags, rather than relying on the library to define the tags. I would strongly prefer that Aloft did not use DogTag; DogTag is massive, and would result in a significant performance hit for people who don't already use a DogTag-based addon. It's also hugely overkill for a nameplate... you don't need more than 2-3 texts on a nameplate, and all of them should be fairly simple. I can't think of a single useful nameplate text that isn't easily possible with the tags Aloft provides.
You do know you can interact with NPCs by right-clicking their nameplate, right? ;)