Results: 4Comments by: Undread
File: Aloft (Beta)03-27-10
Possibly #132 caused by Aloft
Posted By: Undread
A couple people have been getting some very specific #132 crashes out of WoW. I made a wild stab at disabling Aloft because it was the only Addon we had in common. I only use hostile nameplates and my crash occurred multiple times in AV (Where there a a ton of hostile nameplates). The other person used both friendly and hostile na...
File: SCT - Damage03-29-08
Grayhoof, from what I understand it...
Posted By: Undread
Grayhoof, from what I understand it pulls the name from the combat log then tries to find the nameplate using that name with the function SCT:GetNameplate(target). This function gets the nameplate from the available nameplates, however, these nameplates are indexed by the name WITHOUT the realm name. So if I'm attacking "TaurenWa...
File: SCT - Damage03-28-08
Grayhoof, even after the realm name...
Posted By: Undread
Grayhoof, even after the realm names were fixed I was encountering the same bug, I mentioned a few days ago. I tracked it down to the fact that the target name, and the name on the nameplate no longer match when BGs are involved. Basically the name would be "PlayerName-Realm" while the stored data holding the nameplates would be...
File: SCT - Damage03-25-08
Grayhoof, I think I found a little...
Posted By: Undread
Grayhoof, I think I found a little bug. I'm currently using SCT-D with the Nameplate options. It is working fine normally, except when I go into BG's it starts displaying in the default position. One thing I've noticed however is that if the person I'm fighting in the BG is from MY server, the damage displays correctly again....