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
http://wow.curse.com/downloads/wow-addons/details/hideblizz.aspx
(This is no advertising!)
My raid pet bars are all faded out and showing nothing.
Ty for all the work that's put in to this add on as well - much appreciated :) tried a few others after the patch but I like x-perl too much :D
I am having a problem with what I isolated to be Xperl's "close blizzard raid frames" function... the issue is whenever I hit 'O' and go to Raid tab and anything changes ingame (someone logins/logouts - does not have to be even in raid; I change promotes/demotes from within "raid" tab or change change group composition, invite/kick people) the whole raid tab goes black - just a bit annoying
--EDIT: how the hell did I miss it being on known issues list ;/ Anyway ... I guess it WILL be fixed then...Now it is buggy on raid frames. You select player via raid frames, cast HoT, the moving HoT bar/line appears on target frame, but it does not appear on actual raid frames, so it is impossible to tell which players are HoTed.
The only way to make it visible is to hover mouse over player raid frame again, then the HoT bar/line becomes visible, but that's not a solution at all.
my issue was't with the overlap i'm aware of that, my issue is that the toggle doesn't actually disable holy power frame, yet it disables eclipse one
as for docking i'm not concerned with it at all, only show/hide.. those other frames far as i know wouldn't even support being undocked right now they weren'ta s thoroughly coded as dk stuff.
as for statement yeah that's an easy fix. i more or less didn't finish testing it cause regardless of the statement the option itself didn't work, calling hide on holy power frame doesn't work unless i call it before show, but then when i do, calling show doesn't work, i don't know why. since druid code is identicle but allows me to show and hide just fine with the checkbox.
Concerning Rune, Holy Power, Druid Eclipse, etc.
I found the code issue where it is to set to hide / show those extra things for the player frame.
This is Build r457 File Xperl_Options\Xperl_FrameOptions.xml
Line 4690 Currently is this if (select(2, UnitClass("player")) = "DEATHKNIGHT") or (select(2, UnitClass("player")) = "DRUID") or (select(2, UnitClass("player")) = "WARLOCK") or (select(2, UnitClass("player")) = "PALADIN") then Should be this if (select(2, UnitClass("player")) = "DEATHKNIGHT") and (select(2, UnitClass("player")) = "DRUID") and (select(2, UnitClass("player")) = "WARLOCK") and (select(2, UnitClass("player")) = "PALADIN") then
I noticed on my DK that the box to disable the runes was missing, but the box to detach them from the Player Frame was not. I then looked at the logic (I am very new to LUA, so I got lucky) and saw that the logic was wrong. It should be this logic if the class is not a DK, AND not a Druid AND not a Warlock AND not a Paladin then hide it.
Remember for OR and AND logic it goes this way - AND logic, every statement must be true. OR logic, only 1 statement must be true. The current logic for this code is always going to return true, because it includes the multiple classes. If you pick Mage, well it is not a Paladin, not a lock, not a DK and not a Druid, returns true. If you pick Paladin, well it is not a DK (true), not a Druid (true), not a lock (true), but is a paladin (false) but since 3 of the 4 returned true, it returns true.
If you wanted to use ORs, then the logic should have been If the class is a mage or is a priest or is a rogue or is a hunter. That would have worked.
Move on down to line 4714. This line is the check box to Dock the Runes to the Player frame. It is currently set to this if (select(2, UnitClass("player")) = "DEATHKNIGHT") then
So if you are not a DK, it hides it. So that Logic also needs to be changed to match Line 4690 if you want to support undocking. (Looks like other bits of code will need to be updated to support that as well)
Now the only problem is that on a Paladin (I did not check Druids, Warlocks) is that the check box overlaps with the Show Caster Check Box. I have no idea on how to move the check boxes, but I propose you move it to its own section in the lower Right hand section of the frame.
Hopes this helps.
Therigwin
I will have to use a new addon if this is not fixed.
"Message: Interface\AddOns\XPerl\XPerl_Globals.lua:323: Usage: XPerl_Globals:UnregisterEvent("event")
Time: 10/21/10 23:14:59
Count: 1
Stack: [C]: in function `UnregisterEvent'
Interface\AddOns\XPerl\XPerl_Globals.lua:323: in function <Interface\AddOns\XPerl\XPerl_Globals.lua:321>
Interface\AddOns\XPerl\XPerl_Globals.lua:388: in function <Interface\AddOns\XPerl\XPerl_Globals.lua:362>
Locals: (*temporary) = XPerl_Globals {
0 = <userdata>
}
(*temporary) = nil"
Message: Interface\AddOns\XPerl\XPerl_Globals.lua:323: Usage: XPerl_Globals:UnregisterEvent("event")
Time: 10/21/10 23:14:59
Count: 1
Stack: [C]: in function `UnregisterEvent'
Interface\AddOns\XPerl\XPerl_Globals.lua:323: in function <Interface\AddOns\XPerl\XPerl_Globals.lua:321>
Interface\AddOns\XPerl\XPerl_Globals.lua:388: in function <Interface\AddOns\XPerl\XPerl_Globals.lua:362>
Locals: (*temporary) = XPerl_Globals {
0 = <userdata>
}
(*temporary) = nil
The player frames have a gray background and just look like a glitchy mess. Un-installed and re-installed, same problem.
Thanks
haha nevermind he found it.
i think he forgot to upload XPerl_PlayerBuffs.xml
unfortunately gonna probably have to wait til monday for him to upload it he said he won't be on computer again til then.
its not just buggy zeksie its broken. i load up wow and just get spammed with lua errors. All of them say couldn't find inherited node XPerl_Secure_BuffTemplate. 31 errors total.
3x CreateFrame(): Couldn't find inherited node "XPerl_Secure_BuffTemplate":
<in C code>: ?
<in C code>: ?
<in C code>: in function `CreateFrame'
Interface\FrameXML\SecureGroupHeaders.lua:718 in function <Interface\FrameXML\SecureGroupHeaders.lua:692
Interface\FrameXML\SecureGroupHeaders.lua:1031 in function `SecureAuraHeader_Update':
Interface\FrameXML\SecureGroupHeaders.lua:661 in function <Interface\FrameXML\SecureGroupHeaders.lua:657
Locals:
(*temporary) = "Button"
(*temporary) = "XPerl_PlayerbuffFrameAuraButton1"
(*temporary) = XPerl_PlayerbuffFrame {
0 = <userdata>
}
(*temporary) = "XPerl_Secure_BuffTemplate"
---
Okay.. r455.. PlayerBuffs module re-write. It works... somewhat. PLEASE DO NOT tell me it's buggy.. I know it is. Largely due to a number of bugs and errors in the new secure aura header. Nothing I can do about that whatsoever.