another question, and i swear i've looked everywhere :)
when i mouse over buffs now on any frame (x-perl or otherwise), there's a few lines on the tooltip that say:
Without buff: (x)
1: name name name name etc
how can i remove that from my tooltip (stop xperl from scanning that type of stuff)? i dont need xperl scanning my party/raid for missing buffs - i use another mod that does that much more effectively.
Whenever I change the width of my unitframe, the red aggro indicating border doesn't seem to grow with the width of the frame. Also, being a bear tank, this frameborder doesn't always grow over the extra mana bar (seems to be dependend on what form I was when I changed settings), so it looks like a red square just partially covering the unitframe. Like I said, it's just cosmetic, but does make it a bit harder to see if I'm really at full health.
I don't know where to post bugg reports but here's mine:
When I duel the same person a few times, HP stops updating, same thing in arena sometimes and when in raids, thanks in advance.
I don't know where to post bugg reports but here's mine:
When I duel the same person a few times, HP stops updating, same thing in arena sometimes and when in raids, thanks in advance.
Can anyone help me out trying to get LibHealComm 4.0 to work with X-Perl. All our healers with Grid have it, but I have no idea where I'm supposed to put the addon or how to get it activated in-game. Do I need to put the LibHealComm folder into one of my X-Perl folders, just in the general addon folder, etc? Once in game, is there something I have to do to get it to show up or be active?
You should be able to download LibHealComm-4.0 and place it in your addons folder alongside X-Perl.
I've done that before (not with the most current version, but a few months back), and the other healers using Grid with LibbHealComm still were unable to see any of my heals. Are you sure that the only thing requires is placing the LibHealComm folder inside my Add Ons folder and that is all? Is there any configuration for it in X-Perl or in-game?
So the little info I've been able to find more or less says (and please tell me if i'm wrong or missing steps):
1. Download LibHealComm 4.0
2. Unzip and put the folder in your Addons folder.
3. Log into World of Warcraft
4. Done. Now you should see all incoming heals from people using the mod, and they should see mine.
When I did do this a few months ago, I could not see any incoming heals and likewise grid users could not see any of my heals. If anyone is using LibHealComm with their X-Perl and knows for a fact they see incoming heals from Grid users, and Grid users can see their outgoing heals I'd really appreciate hearing how it's set up.
Also, once it is functional what exactly is it going to look like in X-Perl? I already see glowing green frame borders when other X-Perl users having incoming heals. Will the LibHealComm addon show predictive health gains from incoming heals on the raid frames? How much does this interfere with reading other indicators on the frames (like current health/mana, debuffs, raid icons, etc)?
Thanks for whoever can help me out.
Edit:
Looked at the latest version of X-Perl and it only mentions LibHealComm 3.0. I'm assuming it only supports 3.0 right now? If I were to download LibHealComm 3.0 just like I did above, only putting it in my addon directory and nothing else, would that work with Grid users running the 4.0 version?
I've done that before (not with the most current version, but a few months back), and the other healers using Grid with LibbHealComm still were unable to see any of my heals. Are you sure that the only thing requires is placing the LibHealComm folder inside my Add Ons folder and that is all? Is there any configuration for it in X-Perl or in-game?
The currently released Grid (on Curse) supports LHC3. The alpha (available here) supports LHC4. This support went into r1218 on 2009-10-22.
If you tried this a few months ago, you probably did it before support went in.
LHC3 and LHC4 cannot directly communicate with each other. LibWrapperHealComm-1.0 exists for this purpose. Most addons that support LHC4 also include this, but it appears that X-Perl does not. For X-Perl to send and receive LHC3 data, therefore, you need another mod installed that loads LWHC. Try VisualHeal.
Edit: Alternately, install LibWrapperHealComm-1.0 just as you do for LibHealComm-4.0.
I don't use X-Perl, so I can't speak for the configuration. I don't believe it requires any, though.
So the little info I've been able to find more or less says (and please tell me if i'm wrong or missing steps):
1. Download LibHealComm 4.0
2. Unzip and put the folder in your Addons folder.
3. Log into World of Warcraft
4. Done. Now you should see all incoming heals from people using the mod, and they should see mine.
When I did do this a few months ago, I could not see any incoming heals and likewise grid users could not see any of my heals. If anyone is using LibHealComm with their X-Perl and knows for a fact they see incoming heals from Grid users, and Grid users can see their outgoing heals I'd really appreciate hearing how it's set up.
Also, once it is functional what exactly is it going to look like in X-Perl? I already see glowing green frame borders when other X-Perl users having incoming heals. Will the LibHealComm addon show predictive health gains from incoming heals on the raid frames? How much does this interfere with reading other indicators on the frames (like current health/mana, debuffs, raid icons, etc)?
Thanks for whoever can help me out.
It should show predictive heal amounts in some fashion.
Edit:
Looked at the latest version of X-Perl and it only mentions LibHealComm 3.0. I'm assuming it only supports 3.0 right now?
X-Perl supports both, preferring LHC4. However, it appears that the .toc lists LHC3 as an optional dependency, but not LCH4. This is a bug. If you're running on an alphabetical file system, this likely won't affect you.
If I were to download LibHealComm 3.0 just like I did above, only putting it in my addon directory and nothing else, would that work with Grid users running the 4.0 version?
Thanks for the reply. From what I gather from your post I can download and drop LibHealComm 4.0 into my WoW/Interface/Addon/ directory and X-Perl should automatically see and load it. When I get into a raid it will automatically be running/working without me having to do anything else?
Also, people using the latest release of Grid should have LibHealComm 3.0, which can't directly communicate with LibHealComm 4.0. But since the release version of Grid has LibWrapperHealComm-1.0 they should be able to see my heals without any special configuration.
Finally, for my X-Perl using LibHealComm 4.0 to be able to see other people running LibHealComm 3.0 I will need to put LibWrapperHealComm-1.0 in my addon folder. Then run an addon like Visual Heal that will load it. I could then just decide in-game to not show the visual heal stuff.
I'm going to try it out, hopefully tonight, but might not get a chance till tomorrow. I'd still really like to hear from people who currently use X-Perl with LibHealComm (3.0 or 4.0) in raids with other healers who are using Grid.
Thanks for the reply. From what I gather from your post I can download and drop LibHealComm 4.0 into my WoW/Interface/Addon/ directory and X-Perl should automatically see and load it. When I get into a raid it will automatically be running/working without me having to do anything else?
Finally, for my X-Perl using LibHealComm 4.0 to be able to see other people running LibHealComm 3.0 I will need to put LibWrapperHealComm-1.0 in my addon folder.
Having an issue with countdown? Whenever I use the default for displaying health/mana/all the things related that X-Perls changes, I can see the countdowns when I cast spells on enemies. Such as, when I cast judgment of light on an enemy, it does the counterclockwise shadow, letting me know when it's going to expire so I can cast again. However with X-Perls, the spell is there, but no countdown, just stays bright and I have to mouse over it to see how much time is left. Any suggestions?
Really like X-Perl except I cannot set a focus. This is the error:
Error occurred in AddOn:***TaintForced***
Message : Error: Addon***TaintForced*** attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Options - Raid - Tooltip Buff Helper
thanks again Shadoweric, but I don't use any of the Raid modules - I don't even have those folders installed, so I don't have that option.
i wonder if i install them, enable em, set the option and then disable them again, if the behavior i want will stay...hmmm
:p
thanks for the idea!
Whenever I change the width of my unitframe, the red aggro indicating border doesn't seem to grow with the width of the frame. Also, being a bear tank, this frameborder doesn't always grow over the extra mana bar (seems to be dependend on what form I was when I changed settings), so it looks like a red square just partially covering the unitframe. Like I said, it's just cosmetic, but does make it a bit harder to see if I'm really at full health.
Date: 2009-10-30 20:36:43
ID: 1
Error occured in: AddOn: *** TaintForced ***
Count: 1
Message: Error: AddOn *** TaintForced *** attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Debug:
[C]: FocusUnit()
..\FrameXML\UnitPopup.lua:1206: func()
..\FrameXML\UIDropDownMenu.lua:563: UIDropDownMenuButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
AddOns:
Swatter, v5.6.4424 (KangaII)
AckisRecipeList, v1.0 3.2 Beta 3 2412
Atlas, v1.14.2
AtlasBattlegrounds, v1.14.2
AtlasDungeonLocs, v1.14.2
AtlasOutdoorRaids, v1.14.2
AtlasTransportation, v1.14.2
AtlasLoot, vv5.07.06
AtlasLootFu, vv5.07.06
AucAdvanced, v5.6.4424 (KangaII)
AucDb, v5.1.DEV.3583
AucFilterBasic, v5.6.4424 (KangaII)
AucFilterOutlier, v5.6.4424.2531
AucMatchUndercut, v5.6.4424.2531
AucStatClassic, v5.6.4424 (KangaII)
AucStatHistogram, v5.6.4424 (KangaII)
AucStatiLevel, v5.6.4424 (KangaII)
AucStatPurchased, v5.6.4424 (KangaII)
AucStatSales, v5.6.4424.2842
AucStatSimple, v5.6.4424 (KangaII)
AucStatStdDev, v5.6.4424 (KangaII)
AucStatWOWEcon, v5.6.4424.2530
AucUtilAHWindowControl, v5.6.4424.3311
AucUtilAppraiser, v5.6.4424.2530
AucUtilAskPrice, v5.6.4424.3175
AucUtilAutoMagic, v5.6.4424.3142
AucUtilCompactUI, v5.6.4424.2530
AucUtilEasyBuyout, v5.6.4424.3583
AucUtilFixAH, v5.6.4424 (KangaII)
AucUtilItemSuggest, v5.6.4424.3108
AucUtilPriceLevel, v5.6.4424.2545
AucUtilScanButton, v5.6.4424.2530
AucUtilScanFinish, v5.6.4424.2530
AucUtilScanProgress, v5.6.4424.2530
AucUtilSearchUI, v5.6.4424.3655
AucUtilSimpleAuction, v5.6.4424.0
AucUtilVendMarkup, v5.6.4424.2530
Babylonian, v5.1.DEV.130
BeanCounter, v5.6.4424 (KangaII)
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
CartographerWaypoints, v2.0
CartographerZoneInfo, v2.0
ChatMOD, v133
Clique, vwowi:revision
Configator, v5.1.DEV.130
DBMCore, v
DebugLib, v5.1.DEV.130
DPMCore, v
Enchantrix, v5.6.4424 (KangaII)
EnchantrixBarker, v5.6.4424 (KangaII)
ErrorMonster, v3
FuBar, v
FuBarRecountFu, v3.10
FuBarTopScoreFu, vv1.0.5
Gatherer, v3.1.14
GFWDisenchantPredictor, v3.2
Grid, v1.30200.2009081101
GridAutoFrameSize, v2.3.6
IceHUD, v1.5.14 (Revision: 442)
Informant, v5.6.4424 (KangaII)
LightHeaded, v296
LLBuddy, v1.11
Necrosis, v3.0 (r221)
OmniCC, v2.5.7
Quartz, v1.0
QuartzBuff, v1.0
QuartzFlight, v1.0
QuartzFocus, v1.0
QuartzInterrupt, v1.0
QuartzLatency, v1.0
QuartzMirror, v1.0
QuartzPlayer, v1.0
QuartzRange, v1.0
QuartzTarget, v1.0
QuartzTimer, v1.0
QuartzTradeskill, v1.0
RangeColors, v
Recount, v
ShackleWatch, v30013
SharedMedia, v3.0.1-177
SharedMediaAdditionalFonts, v1.0
simpleMinimap, v30000-5
SlideBar, v5.6.4424 (KangaII)
Spy, v
Stubby, v5.6.4424 (KangaII)
TinyTip, v0.3-Beta
TrinketMenu, v
XPerl, v3.0.6
XPerlArcaneBar, v
XPerlParty, v
XPerlPartyPet, v
XPerlPlayer, v
XPerlPlayerBuffs, v
XPerlPlayerPet, v
XPerlRaidAdmin, v
XPerlRaidFrames, v
XPerlRaidHelper, v
XPerlRaidPets, v
XPerlTarget, v
XPerlTargetTarget, v
ZHunterMod, v
BlizRuntimeLib_enUS v3.2.2.30200 <us>
(ck=bfd)
That's because you can't set a focus using an addon. You must do it manually with /focus and /clearfocus
When I duel the same person a few times, HP stops updating, same thing in arena sometimes and when in raids, thanks in advance.
http://www.wowace.com/addons/xperl/tickets/
You should be able to download LibHealComm-4.0 and place it in your addons folder alongside X-Perl.
I've done that before (not with the most current version, but a few months back), and the other healers using Grid with LibbHealComm still were unable to see any of my heals. Are you sure that the only thing requires is placing the LibHealComm folder inside my Add Ons folder and that is all? Is there any configuration for it in X-Perl or in-game?
So the little info I've been able to find more or less says (and please tell me if i'm wrong or missing steps):
2. Unzip and put the folder in your Addons folder.
3. Log into World of Warcraft
4. Done. Now you should see all incoming heals from people using the mod, and they should see mine.
Also, once it is functional what exactly is it going to look like in X-Perl? I already see glowing green frame borders when other X-Perl users having incoming heals. Will the LibHealComm addon show predictive health gains from incoming heals on the raid frames? How much does this interfere with reading other indicators on the frames (like current health/mana, debuffs, raid icons, etc)?
Thanks for whoever can help me out.
Edit:
Looked at the latest version of X-Perl and it only mentions LibHealComm 3.0. I'm assuming it only supports 3.0 right now? If I were to download LibHealComm 3.0 just like I did above, only putting it in my addon directory and nothing else, would that work with Grid users running the 4.0 version?
The currently released Grid (on Curse) supports LHC3. The alpha (available here) supports LHC4. This support went into r1218 on 2009-10-22.
If you tried this a few months ago, you probably did it before support went in.
LHC3 and LHC4 cannot directly communicate with each other. LibWrapperHealComm-1.0 exists for this purpose. Most addons that support LHC4 also include this, but it appears that X-Perl does not. For X-Perl to send and receive LHC3 data, therefore, you need another mod installed that loads LWHC. Try VisualHeal.
Edit: Alternately, install LibWrapperHealComm-1.0 just as you do for LibHealComm-4.0.
I don't use X-Perl, so I can't speak for the configuration. I don't believe it requires any, though.
Correct.
See above.
It should show predictive heal amounts in some fashion.
X-Perl supports both, preferring LHC4. However, it appears that the .toc lists LHC3 as an optional dependency, but not LCH4. This is a bug. If you're running on an alphabetical file system, this likely won't affect you.
Grid does include LWHC, so yes.
Also, people using the latest release of Grid should have LibHealComm 3.0, which can't directly communicate with LibHealComm 4.0. But since the release version of Grid has LibWrapperHealComm-1.0 they should be able to see my heals without any special configuration.
Finally, for my X-Perl using LibHealComm 4.0 to be able to see other people running LibHealComm 3.0 I will need to put LibWrapperHealComm-1.0 in my addon folder. Then run an addon like Visual Heal that will load it. I could then just decide in-game to not show the visual heal stuff.
I'm going to try it out, hopefully tonight, but might not get a chance till tomorrow. I'd still really like to hear from people who currently use X-Perl with LibHealComm (3.0 or 4.0) in raids with other healers who are using Grid.
Correct.
Correct.
Incorrect. The current release of Grid doesn't use LWHC, as LWHC depends on LHC4. The alpha of Grid includes it.
Correct.
If you put LWHC and LHC4 into your addons folder, you don't need VisualHeal. It's just another way to load the libraries.
Check the options next time.
Error occurred in AddOn:***TaintForced***
Message : Error: Addon***TaintForced*** attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Thanks