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
I like to use icehud for player and target, but xperl for the rest of frames ie party and raid and focus
clique is working fine for me
Now, I have it set to NOT hide default buffs, so I see the Blizzard ones. However, those for some reason seem to not update correctly when I am using xperl and on a vehicle either, so that work-around does not work.
If anyone knows a way to make it work so that I can see the correct buffs that my VEHICLE has (and not ME) please let me know. Otherwise can you please fix this? Bliz loves vehicles so it's not something we can avoid :(
But thanks otherwise for a great addon.
After the changes made on the 2nd, the raid frame doesn't seem to be playing nice with Clique.
After a UI reload some Clique actions don't work on the raid frame (but do on other frames), the Clique authors are saying this is an x-perl issue with the frame.
When the smallgroup option is enabled (raid of 5 or less is displayed as a party) if i decide to turn my party into raid while in combat then the raid frame won't show up because I've added the manual setting of fullyInitiallized = true and this is OK;
if i invite more ppl into the raid, then the party frame get hidden, this is OK;
BUT the raid frame won't show up until another roster event is triggered while ooc.
If I decide to not use the smallgroup option then if I turn my party into raid while in combat the raid frame will show up and all will be fine, but the party frame won't hide until we are ooc.
I've searched through the code for some InCombatLockDown() related to the smallraid option, but couldn't find the solution.
The second problem is the one with highlight screwing up after the leader change.
If the leader change is done while the raid is shown, then you will see the reordering of the group where the leader his, while he goes on top of his party the target highlight won't bug. Instead this happens if the party is displayed.
This leads me to think that the bug is in Xperl_PartyFrame because both party and raid uses the highlight call back function, and since this works fine for the raid frame then the problem is not in an external file.
I've noticed that while you have the highlight bug, if you open and close the xperl option panel then all return fine. What function is triggered? the AttributeChanged one ? or maybe the group array must be recreated after a leader change? Dunno.
If you want to reproduce it, target the last party member then promote it to leader.
I'd like to submit a feature request for once things settle down.
It'd be awesome if there was a way to display weakened soul on the raid frames (an icon in the corner or something). With variant durations due to strength of soul, it's harder to know when shield can be recast now, so a visual cue would be cool.
Thanks for all the hard work!
It's funny because I cannot get any error/get tainted shit with my Druid in combat when using sontix's fix... :\ Maybe I missed something...
(If it happens on my end, I will skipped it and say it cause problem on my end. But it's not...)
EDIT : Fixed typo... :\
@Zek you have added in the latest alpha r508 the combatlockdown check
to protect self.statsFrame:SetHeight(h) from being triggered while in combat. I've tried many time in many different places if this cause any error, but I can't generate any. What's wrong in allowing the frame to show correctly the druid mana bar if you are in combat? What error this may cause ? I really don't get it.