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
@Pelf: Due all taint bullshit by Blizzard when in combat on some situation(I guess) , this problem isn't easy to fix, and...no one knows how to fix it...that's a big problem. :\
Since it looks like people are reading here ... this has been an issue for a good while now.
http://www.wowace.com/addons/xperl/tickets/1092-druid-shape-shift-health-bar-stuck/
It just stopped resizing properly after one of the patches back then. Whatever size the frame is when you go into combat is the size it's stuck at for combat. So, when you're in caster for combat and it tries to add a bar for rage/energy, it squishes stuff.
Thanks for keeping the addon up to date as much as possible guys thanks!
i am starting to think the taints only happen by interaction with a vehicle UI, after which they just spam happen. but the first taint that starts the problems happens when you use a vehicle. such as the turtle daily in hyjal. or bears in trees. i suspect the two raids i had no taints were cause i actually stopped doing dailies. Just didn't put 2 and 2 together until now and noticed it further. so gonna have to look into it. if vehicle UI is protected, and it's falling an unprotected function like compact unit frames, that could taint in combat if xperl is hooked into compactraidframe, but maybe if i hook the vehicle frame? More experimenting to come!
Yeah, I was remember if I don't bump those revision numbers in "XPerl_SetModuleRevision" and "XPerl_RequestConfig", sometimes X-Perl will display old revision, not the newer one. But sometimes it works fine at all... I don't know...
But at least, if I do bump them both, it never happens again. :\ (I guess the Wowace packager may do write revision in the result package so it may not be a problem but I don't know...)
And... I feel more warning would be fine... :p
don't think there was much reason to edit the main xperl file, when i moused over people in game it said r362 despite that file being 359. it doesn't need to be manually edited every commit, maybe before tagging a release I would.
Also although annoying and spammy (they fill up taint log), those settings actually both do work. The warning was already sufficent it didn't really need more. was just enough so they woudlnt' come to report the bugs, not cause it will actually make client unstable. i haven't see the taints actually cause any harm. they just annoy me. Seeing "interface failed because of an addon" in combat and knowing it was xperl and the dumb raid frames. however i continue raiding another 4 hours and have 0 actual UI glitches.
Maybe that's because Blizzard didn't made their shit works right at all, and cause those random tainting bullshit mess...whatever, it's not bad at all, even I had some bad feel about the whole BlizzardRaidFrame hiding mess-age...:\
aww, it's still buggy.
7/29 22:54:47.746 An action was blocked in combat because of taint from XPerl - CompactRaidFrame1:Show() 7/29 22:54:47.746 Interface\FrameXML\CompactUnitFrame.lua:260 CompactUnitFrame_UpateVisible() 7/29 22:54:47.746 Interface\FrameXML\CompactUnitFrame.lua:220 CompactUnitFrame_UpdateAll() 7/29 22:54:47.746 Interface\FrameXML\CompactUnitFrame.lua:101
So i guess it's not 100% fixed. but wierd that i did two raids without taint then today it's doing same thing it's always been. oh well, either way it's as good as it's gonna get. i'll just have to reword options again to warn they both still cause taints. Will just have to deal with it.
@mysticalos: Nice job, let's hope this mess would be ends with that......oh, wait...
the irony is the curent alpha, as long as you do NOT hide manager and only hide container, didn't taint at all last 2 nights. which is strange, cause it was container that was tainting before not manager. maybe container only taints if you mess with manager. in any cause i'mgonna run it a few more days, if i continue to get no taints i may comment out the manager hiding for now and release a taint free version that keeps raid frames dead and let users just deal with manager, at least that stays colapsed between logins