X-Perl UnitFrames
Patch 6.0.3 compatibility and future of X-Perl
Use latest alpha from WoWAce for using in Patch 6.0.3
http://www.wowace.com/addons/xperl/files/
May still has problems but for most cases it should be working(at least was tested on beta), if not, clearing old setting by killing(and backup) XPerlxxxxxxx.lua in the WTF directory of your WoW installlation and try again with fresh new default setting, thanks your patience.
If still someone want to help Zeksie for he earns his donates from X-Perl then that's fine for Zek and X-Perl, but seems like it's time to cut him out as no one want to help X-Perl anymore (as many of users already heard about the mess of this poor addon), I guess.
I don't know X-Perl will still be continue or not(it's highly possible it won't be, as the new maintainer Resike continued the developing and forked to Z-Perl, and he said he won't abandon his addons), I won't force everyone should must to use Resike's one at this point, as his Z-Perl isn't stable yet, and for some reasons, I don't think he want to port his fixes back to X-Perl as he knows about how Zek did about his addons and everyone who helped Zek to maintaining this poor addon...and, of course...X-Perl may broken again when next time Blizzard's patches released..... /sigh
(At this point, I won't force everyone who used X-Perl to go Z-Perl until it's more stable than now, feel free to use Z-Perl or other Unitframe addons if you want, and do NOT hold your breathe about X-Perl too much, too. I already lost my hope on X-Perl, at least I can trust Resike and Z-Perl now...)
Sincerely,
PlayerLin - Maintainer of X-Perl but not a proper skilled coder, just a locale translator and do some shitty PRs. :(
Bug Reporting
Please use the Ticketing System on WoWAce Here and avoid posting bugs using comments on Curse because they're difficult to track and they will probably get lost.
Use a good error catcher (like BugSack from files.wowace.com) and provide the full error text, and give as much information as possible to recreate the problem. Don't assume We know what you're talking about with some three word report.
Introduction
Perl, with Extra stuff. Much enchanced from Nymbia's Perl UnitFrames, and a complete replacement for Blizzard's default unit frames, including raid frames and raid tools, with little remaining of the original Nymbia code.
- Range Finder (combined with optional health check and/or debuff check) for all frames based on spell or item range test.
- HoT Monitor will highlight units clearly that have ''your own'' active Heal over Time spells. Regardless of how many other heal over time buffs are on the raid members, you can keep track of your own ones and when they expire.
- Debuff Highlighting in standard debuff colours on all friendly frames. Priority given to show debuffs that ''you'' can cure first.
- Raid Frames, buff icons, MT list units and some other portions or X-Perl are Created on demand. Saving a lot of time and memory at system startup. Defering the creation of many parts of X-Perl to when they are actually required. And of course, most often outside of raids they are never required and are never created.
- Raid Target icon support for Target, Target's Target, MT Targets.
- Raid Tooltip will show combat rezzers available (druids with Rebirth ready (or very soon available) and any normal rezzers out of combat) if you bring up tooltip of a dead person.
- In-combat indicators for all units.
- 3D Portraits for player, pet, target, focus, party. Optional. Of course this may degrade your framerate somewhat because you are displaying more 3D character models that without this option. But some like it pretty, and it does look cool.
- Red and Green combat flashes for frames when player, pet, target, party, partypets, raid take damage/heals. Useful indication of things happening.
- Added '''time left''' on party member/target buffs/debuffs when in a raid, these depend somewhat on CTRA sending appropriate information over the addon channel, although some of it can be determined at run time by X-Perl, when a player gets a buff for example, we know how long it should last, and therefor when it should expire.
- Totally new options window including all X-Perl options and access via minimap icon and the /xperl splash command.
- Configurable colours for borders and backgrounds. Including class coloured names, and configurable reaction colours.
Much care has been taken with code size, memory load, memory usage per cycle and so on. LuaProfiler/OnEvent mods used extensively and regularly to ensure that X-Perl does not do more work than is absolutely necessary.
Assists View
Will show anyone from raid assising you with your target, and can also show healers or all plus known enemies targetting you.
Tooltips for the same also available (on player and target frames) if you prefer to not use the main window.
MT Targets
Replaces CTRA MT Targets window, and doubles as a replacement for the Perl RaidFrames warrior targets.
Indicator shows which target you are on.
Frames will be coloured to show if tanks have duplicate targets.
Casting Monitor
(WORK IN PROGRESS)
Shows selected classes (defaults to healer classes) in a list (much like the MT List), but with some differences.
Shows mana bars and cast bars on left. Their targets on right. Health bar as normal, but a secondary small red bar on targets which shows the maximum single hit this unit has received since entering combat. The secondary bar will extend downwards from their current HP level down to as far as zero.
A green name on the targets indicates this is the same target that you have. You can click on casters or their targets as expected.
For druids, right clicking on a caster will cast Innervate on them.
For shamans, right clicking on a caster will cast Mana Tide Totem. Check the * indicator to see if they're in your group.
All bars can be re-sized in X-Perl main options (Monitor section).
Totals can be toggled (from the 'T' minibutton at top of frame) which gives overview of raid mana status.
Raid Admin
(WORK IN PROGRESS)
Save/Load raid roster setups Only does direct save and load for the moment, but more to come (templates and such).
Item Check
Replacement for /raitem /radur /raresist /rareg. Use the old commands before, or drop items in the left item list.
Query button will perform /raitem on all ticked items (query always includes dur and resists) and you can then view and review all the results whenever, without having to re-query each item.
Includes everyone in raid, so you don't have to work out who doesn't have items, it'll list them with 0 instead of no entry.
Active Scanner to check raid member's equipment for the item selected. So you can be sure that people actually have the item worn (Onyxia Cloak for example), without having to go round single target inspecting everyone who 'forgot' to install CTRA for the 50th raid in a row.
Grim Reaper
Removed from X-Perl, but continues as it's own standalone Ace mod.
[http://www.wowace.com/projects/grim-reaper/]
More Buffing Features
Can be found in my new universal buffing mod, ZOMGBuffs
ah yeah something that's more glammer than actual utility in raid frames anyway, i think there are a lot of bling features that really have no real use that should just be yanked out, reduce cpu/memory usage and get xperl back to it's roots of being a unit frame mod.
Xperl has an option to display your targets talents under their portrait it shows up in a 0/0/0 format or as text. This is broken on live as well so probably no point in fixing it. I think it broke when they made the change to number of inspects able to happen at a time or w/e that change was.
what talents? i've never seen xperl display talents so i wouldn't know. i disable a lot of the plugins and features though since most of em are useless to me anyways.
something i didnt really pay attention to before, but i noticed talents arent displaying anymore either
with all the talent tree changes thats probably going to be a pain to fix tho, lol
The fact is, it's not fixable except you're using Blizzard's default Unitframe.
Like mysticalos said, it's not fixable and get blocked if unitframe mods replaced Blizzard one, even if you angry/blaming and stop using X-Perl, it still not fixable.
And there are some methods to set focus, not just with the "Set focus".
If you still persist want fixed the setfocus on X-Perl. Please, go to Blizzard's addon forum and angry on them, or just wait someone know how to get it works again, else you just did useless shit and it cannot helps.
*sigh*
I have done several searches for a few days now and apparently there is no fix or the DEV's refuse to fix it while blaming the error on other addons. Even after many people have been saying the error still occurs with a clean install or no other addons installed. I myself have tried this several times and I too get the error.
As well the dev's state the 4.0 has pretty much broken X-perl.
So seeing as they absolutely refuse to admit to the TaintForced error being their fault even after several years of issues concerning the error and considering that cata will break X-Perl I guess it is time to move on.
I want to give a big thank you to the author's of X-Perl for the awesome add on. It was a great run for several years now.
http://www.wowinterface.com/forums/showthread.php?t=32466
Your refusal to fix the focus frame error in your mod, that has been broken for over 2 year's, is no fault of the communities. You have known about it for quite some time. either fix it or continue lose people to other unit frame mods that work.
I won't apologize for your immaturity and anger over your unwillingness to fix it..
Xperl has it's fair share of issues. But this is not one of them, never has been. You want setfocus fixed, go to blizzard forums under UI/interface section and tell them to fix the contextual menu attached to setfocus to not be protected function with no possble secure hook work around that ANY addon author can use.
Then you complain about the addons state in 4.0 when if you followed development at all, would know there are literally DAILY updates to ensure 4.0 issues are worked out. The alpha builds are very functional with mostly minor bugs now. But i bet you haven't used any of them have you? probably fired up 3.0.9 in PTR then wondered why a version NOT designed for 4.0 didn't work.
but go ahead, download another unit frame mod, then give them the same immature feedback when setfocus still taints with that mod instead when accessed via the popup menu on target/player portrait. The only way any unit frame won't taint "setfocus" from popup menu is if it does not replace the default frames. Such as grid. cause grid will provide raid frames only, not target frames, and obviously default frames are not forbidden from using protected functions. (the very definity of a protected function is one that has restrictions to 3rd party developers such as us, sometimes with work arounds, sometimes, like this case, with no possible one at all.)
I don't speak what ever version of English that was.
I just want to say : Not one of us can fix the "Set focus" problem, even the author Zeksie himself, that's it.
with the release of r393 i am still getting that error but if you remove line 337. XPerl_Player_Pet_Events.UNIT_POWER = nil you no longer get that error and pet happiness also works.
really need to test stuff before you commit it. that pet fix is full of errors, for any class that isn't a hunter on login. as well as brounks error. Should be fixed now though.
Date: 2010-10-04 15:13:31 ID: 3 Error occured in: Global Count: 1 Message: ...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua line 385: attempt to call global 'XPerl_Player_Pet_SetHappiness' (a nil value) Debug: [C]: XPerl_Player_Pet_SetHappiness() ...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua:385: func() ...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua:320: ...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua:313
yes i am also getting that error iv been trying to fix it but no luck it happens on every class except hunter.
Edit: if you revert to r391 it fixes that error so it must be something to do with the pet happiness fix in r392.
getting this error now when attacking something with r392
Date: 2010-10-04 20:41:23
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\XPerl\XPerl.lua line 135:
attempt to concatenate global 'event' (a nil value)
Debug:
(tail call): ?
[C]: ?
XPerl\XPerl.lua:135 XPerl_ShowMessage()
...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua:326
...nterface\AddOns\XPerl_PlayerPet\XPerl_Player_Pet.lua:313