It fades the unitframes of people who are out of range, which is now also a feature in the default WoW interface. It's based on one of your spells or a bandage if you don't have that kind of ability (e.g. rogues). There's also one setting for range on your target frame.
You guys should check the latest alphas (alphas = unstable, so do this knowingly), the castable/curable buffs/debuffs problems should now be fixed. Not sure why Zeksie doesn't post it here since it's been such a big issue, but *shrug*...
Cos I'm fiddling with the code that does the exceptions to castable, so things work like they used to. You know, where a priest will see all hots from all classes etc. ;)
The same display problem also happens in ZOMG portal module. The big font won't display properly in TW client which might cause by UTF8 display requirement.
The same display problem also happens in ZOMG portal module. The big font won't display properly in TW client which might cause by UTF8 display requirement.
Thanks your update. I fixed my copy to make sure I will not missed them again.
About Aggro messages in raid helper. That was fixed by other unofficial X-Perl version
(I remember that version was by original zhTW translator and he didn't (or can't...who knows) told Zeksie to fix the stupid font problem. Then his version of X-Perl v 2.x.x had fixed the Aggro font problem but not fixed in official X-Perl releases.)
So I think it can be fixed by Zeksie. :D
I know some TW/HK players can't know what Aggro mean, so I think it should be translated. But still thanks your point. :)
About Aggro messages in raid helper. That was fixed by other unofficial X-Perl version
(I remember that version was by original zhTW translator and he didn't (or can't...who knows) told Zeksie to fix the stupid font problem. Then his version of X-Perl v 2.x.x had fixed the Aggro font problem but not fixed in official X-Perl releases.)
So I think it can be fixed by Zeksie. :D
I know some TW/HK players can't know what Aggro mean, so I think it should be translated. But still thanks your point. :)
Whatever, the download package will give an annoying -?- for every aggro and this is rather scary when regular users saw this in raid.
my 2 cents, if you translate anything, use the original version instead of other users modified codes. And test before submit.
Cos I'm fiddling with the code that does the exceptions to castable, so things work like they used to. You know, where a priest will see all hots from all classes etc. ;)
I did not recieve an error message for this, because wow kept crashing / freezing up. After some testing of turning off all add ons and turning them back on one at a time I came to the conclusion it was X-perl that was the source of my sorrow.
The specific problem that went unnoticed with xperl as the only addon actived was: in any tradeskill window (default blizz) I could not type in the search function.
What caused the game to crash: Running X-perl and Skillet at the same time. The game would freeze up the second I openned any tradeskill with Skillet actived.
I have been using X-Perl and Skillet without a problem since wrath came out. Today is the first I have encountered a problem of this nature.
Zeksie,
First, thank you so very much for keeping the X-Perl development underway.
I'm looking to display the raid icon of a players target on the players raid frame. Below is the code I've copied and modified to produce a second raid icon on the raid frame, calling the new function where ever the original function is called within the rest of the lua file. It's from the XPerl_Raid.lua. The red are my additions and the green is a change.
local function XPerl_Raid_RaidTarget[COLOR="Red"]OfTarget[/COLOR]Update(self)
local icon[COLOR="Red"]t[/COLOR] = self.nameFrame.raidIcon[COLOR="Red"]t[/COLOR]
local raidIcon[COLOR="Red"]t[/COLOR] = GetRaidTargetIndex(self.partyid)
if (raidIcon[COLOR="Red"]t[/COLOR]) then
if (not icon[COLOR="Red"]t[/COLOR]) then
icon[COLOR="Red"]t[/COLOR] = self.nameFrame:CreateTexture(nil, "OVERLAY")
self.nameFrame.raidIcon[COLOR="Red"]t[/COLOR] = icon[COLOR="Red"]t[/COLOR]
icon[COLOR="Red"]t[/COLOR]:SetTexture("Interface\\TargetingFrame\\UI-RaidTargetingIcons")
icon[COLOR="Red"]t[/COLOR]:SetPoint("[COLOR="Lime"]RIGHT[/COLOR]")
icon[COLOR="Red"]t[/COLOR]:SetWidth(16)
icon[COLOR="Red"]t[/COLOR]:SetHeight(16)
else
icon[COLOR="Red"]t[/COLOR]:Show()
end
SetRaidTargetIconTexture(icon[COLOR="Red"]t[/COLOR], raidIcon[COLOR="Red"]t[/COLOR])
elseif (icon[COLOR="Red"]t[/COLOR]) then
icon[COLOR="Red"]t[/COLOR]:Hide()
end
end
Now please understand I'm not fluent in lua what-so-ever, but I have tried doing some research and attempted to change the self.partyid to get the player's target raid icon index number but have been unsuccessful. Some of what I've tried are: self.partyid.."target", self.target, self.playertarget. I can't seem to get the UnitId right. If it's too much of a rewrite it's not something I'm dire need of. If it is just as simple as changing the self.partyid I would very much appreciate your assistance in finding the correct variable representing the player's target raid icon.
Anyone else seeing an issue when coming alive after a naxx wipe in Dragonblight xperl shows your health as 0 until you heal yourself even though you are at full health?
During various encounters it has consistently bugged me why I couldn't always select the vehicles I was riding in.
Doing some testing, I realized that it does work properly, but it seems like the targeting portion of the name plate was somehow switched around.
To clarify, if I click on anything clickable (portrait, health/mana bars) it will properly target my vehicle. However if I try to click on the name plate, it attempts to target myself, which doesn't work on various combat vehicles (such as the drakes at Malygos). On the other side, doing the same on the pet frame (that shows me) will target myself in most parts, but the vehicle if I click on the name plate.
If possible, I hope you can fix this, so targeting gets less of a hassle using XPerl, as I like them otherwise, and would hate to have to look for something new just because I get confused during the heat of the battle to select the proper thing.
Hi. This may sound really simple to some, but to me its not. I have accidentally disabled the estimate of incoming heals on my player frame and I do not know how to re-enable it. I use to be able to see a smaller, lighter bar of the incoming heal, no I see nothing. Its driving me crazy along with freaking out while I tank, not knowing if someone is healing me or if I need to mash one of my safety buttons. I am using the latest version. Any ideas? I would remove x-perl and reinstall with a new profile but I have about an hour in to making it work the way I want except for this one item. Thank you for all your help.
This targetting method I am aware of too, but its not x-perl to blame. You can select other players using x-perl, but it is not other players you are intending to select... its their pet. When you ride the drakes for Malygos or any vehicles you are basically becoming that pet. You should see your very own pet frame pop up. As of now, I too have to click the actual person/pet to target for Oculus, which is faily easy. And for encounters like Malygos, aren't you just AOE healing and single (1) target DPS anyway? This seems to be a "feature" (or limitation) in the way blizzard has created these "pets" and what their relationship is to the rider.
Cos I'm fiddling with the code that does the exceptions to castable, so things work like they used to. You know, where a priest will see all hots from all classes etc. ;)
BTW, Please don't translate this in raid helper, the font won't display properly
The same display problem also happens in ZOMG portal module. The big font won't display properly in TW client which might cause by UTF8 display requirement.
Thanks your update. I fixed my copy to make sure I will not missed them again.
About Aggro messages in raid helper. That was fixed by other unofficial X-Perl version
(I remember that version was by original zhTW translator and he didn't (or can't...who knows) told Zeksie to fix the stupid font problem. Then his version of X-Perl v 2.x.x had fixed the Aggro font problem but not fixed in official X-Perl releases.)
So I think it can be fixed by Zeksie. :D
I know some TW/HK players can't know what Aggro mean, so I think it should be translated. But still thanks your point. :)
Whatever, the download package will give an annoying -?- for every aggro and this is rather scary when regular users saw this in raid.
my 2 cents, if you translate anything, use the original version instead of other users modified codes. And test before submit.
I was checked both the enUS and old zhTW to know what strings missing in zhTW.. maybe I oversight on those strings.
Next time I'm sure do from original version. Thanks your advice. :D
Yeah, I know, I feel sorry about that.
Hmm... I was tested and know that bug was exist.
But I forgot changed that strings back... :'(
Whatever, I just hope Zeksie can back soon and change those two strings back and can fix the "-?-" problem... :)
Aha, cool. :) Glad you're reading this.
PS: please remember the new shaman HoTs. :)
The specific problem that went unnoticed with xperl as the only addon actived was: in any tradeskill window (default blizz) I could not type in the search function.
What caused the game to crash: Running X-perl and Skillet at the same time. The game would freeze up the second I openned any tradeskill with Skillet actived.
I have been using X-Perl and Skillet without a problem since wrath came out. Today is the first I have encountered a problem of this nature.
Whenever I try to set something as focus, X-Perl breaks [well still works, but won't let me set a focus]:
Date: 2009-01-11 13:14:26
ID: 51
Error occured in: AddOn: XPerl
Count: 1
Message: Error: AddOn XPerl attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Debug:
[C]: FocusUnit()
..\FrameXML\UnitPopup.lua:1181: func()
..\FrameXML\UIDropDownMenu.lua:568: UIDropDownMenuButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
AddOns:
Zoom, v
Swatter, v5.1.3715 (SnaggleTooth)
ArkInventory, v3.02
Atlas, v1.13.0
AtlasBattlegrounds, v1.13.0
AtlasDungeonLocs, v1.13.0
AtlasOutdoorRaids, v1.13.0
AtlasTransportation, v1.13.0
AucAdvanced, v5.1.3715 (SnaggleTooth)
AucFilterBasic, v5.1.3715 (SnaggleTooth)
AucFilterOutlier, v5.1.3715.2531
AucMatchUndercut, v5.1.3715.2531
AucStatClassic, v5.1.3715 (SnaggleTooth)
AucStatHistogram, v5.1.3715 (SnaggleTooth)
AucStatiLevel, v5.1.3715 (SnaggleTooth)
AucStatPurchased, v5.1.3715 (SnaggleTooth)
AucStatSales, v5.1.3715.2842
AucStatSimple, v5.1.3715 (SnaggleTooth)
AucStatStdDev, v5.1.3715 (SnaggleTooth)
AucStatWOWEcon, v5.1.3715.2530
AucUtilAHWindowControl, v5.1.3715.3311
AucUtilAppraiser, v5.1.3715.2530
AucUtilAskPrice, v5.1.3715.3175
AucUtilAutoMagic, v5.1.3715.3142
AucUtilCompactUI, v5.1.3715.2530
AucUtilEasyBuyout, v5.1.3715.3583
AucUtilItemSuggest, v5.1.3715.3108
AucUtilPriceLevel, v5.1.3715.2545
AucUtilScanButton, v5.1.3715.2530
AucUtilScanFinish, v5.1.3715.2530
AucUtilScanProgress, v5.1.3715.2530
AucUtilSearchUI, v5.1.3715.3483
AucUtilSimpleAuction, v5.1.3715.3708
AucUtilVendMarkup, v5.1.3715.2530
Babylonian, v5.1.DEV.130
Bartender4, v4.2.1
BasicBuffHide, v1.1
BeanCounter, v5.1.3715 (SnaggleTooth)
BEB, v
Bison, v1.4.3
BonusScanner, v4.2
Cartographer, v2.0
CartographerBattlegrounds, v2.0
CartographerCoordinates, v2.0
CartographerFoglight, v2.0
CartographerGroupColors, v2.0
CartographerGuildPositions, v2.0
CartographerInstanceLoot, v2.0
CartographerInstanceMaps, v2.0
CartographerInstanceNotes, v2.0
CartographerLookNFeel, v2.0
CartographerNotes, v2.0
CartographerPOI, v2.0
CartographerProfessions, v2.0
CartographerWaypoints, v2.0
CartographerZoneInfo, v2.0
Configator, v5.1.DEV.130
CurseProfiler, v
DDPlus3, v0.1
DebugLib, v5.1.DEV.130
DragQueen, v3.0.2-1.01
EnhTooltip, v5.1.3715 (SnaggleTooth)
FuBar, v
FuBarAtlasFu, v
FubarAutoLootFu, v2
FuBarBagFu, vv1.1.3
FuBarClockFu, v3.0
FuBarCustomMenuFu, v1
FuBarDigiCamFu, vv1.1
FuBarDurabilityFu, v2.11
FuBarExperienceFu, v1.1 $Revision: 65606 $
FuBarGroupFu, v1
FuBarMoneyFu, vv1.2
FuBarQuestsFu, v2.0
FuBarRecZone, v2.0.57
FuBarSpeedFu, v2.0.$Revision: 48 $
FuBarTrackerBoyFu, v1.0
FuBarTrainerFu, v0.2
Informant, v5.1.3715 (SnaggleTooth)
LootDB, v3.0.3
LootFilter, v3.10
OmniCC, v2.2.5
Outfitter, v4.3b13
Prat30, v3.0.0
Prat30Libraries, v
QuestHelper, v0.82
simpleMinimap, v30000-4
Stubby, v5.1.3715 (SnaggleTooth)
TomTom, v193
XPerl, v3.0.2a
XPerlArcaneBar, v
XPerlParty, v
XPerlPartyPet, v
XPerlPlayer, v
XPerlRaidAdmin, v
XPerlRaidFrames, v
XPerlRaidHelper, v
XPerlRaidPets, v
XPerlTarget, v
XPerlTargetTarget, v
(ck=aea)
Man, I just answered that (again) a few posts above yours... known Bliizard bug.
First, thank you so very much for keeping the X-Perl development underway.
I'm looking to display the raid icon of a players target on the players raid frame. Below is the code I've copied and modified to produce a second raid icon on the raid frame, calling the new function where ever the original function is called within the rest of the lua file. It's from the XPerl_Raid.lua. The red are my additions and the green is a change.
Now please understand I'm not fluent in lua what-so-ever, but I have tried doing some research and attempted to change the self.partyid to get the player's target raid icon index number but have been unsuccessful. Some of what I've tried are: self.partyid.."target", self.target, self.playertarget. I can't seem to get the UnitId right. If it's too much of a rewrite it's not something I'm dire need of. If it is just as simple as changing the self.partyid I would very much appreciate your assistance in finding the correct variable representing the player's target raid icon.
Thanks,
Boom
Shaman Totem timers.
When I first log on and drop a totem, I can not see the stock totem timers come up.
Open options, unclick and reclick to show stock totem timers and they appear.
This broke about 4 alpha's ago and I thought it best to report it here.
Love Xperl, thanks for the great work.
During various encounters it has consistently bugged me why I couldn't always select the vehicles I was riding in.
Doing some testing, I realized that it does work properly, but it seems like the targeting portion of the name plate was somehow switched around.
To clarify, if I click on anything clickable (portrait, health/mana bars) it will properly target my vehicle. However if I try to click on the name plate, it attempts to target myself, which doesn't work on various combat vehicles (such as the drakes at Malygos). On the other side, doing the same on the pet frame (that shows me) will target myself in most parts, but the vehicle if I click on the name plate.
If possible, I hope you can fix this, so targeting gets less of a hassle using XPerl, as I like them otherwise, and would hate to have to look for something new just because I get confused during the heat of the battle to select the proper thing.
Regards
Quin
Thanks for the great mod!
This targetting method I am aware of too, but its not x-perl to blame. You can select other players using x-perl, but it is not other players you are intending to select... its their pet. When you ride the drakes for Malygos or any vehicles you are basically becoming that pet. You should see your very own pet frame pop up. As of now, I too have to click the actual person/pet to target for Oculus, which is faily easy. And for encounters like Malygos, aren't you just AOE healing and single (1) target DPS anyway? This seems to be a "feature" (or limitation) in the way blizzard has created these "pets" and what their relationship is to the rider.