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
If it happens on only Monk characters, most likely X-Perl haven't correctly and properly supported them or just missed that one...please fire a ticket on WoWAce's X-Perl project site with detailed messages about this problem...
@Tharai
Then go tell Blizzard or other companies/programmers which using letters on their products versioning.
Seriously, I never see any guidelines/documents about you can only use numbers on the versioning system.
You're the first one...
Im having a problem with mouse-over macros on the XPerl raid frames.
There is no LUA error of any kind I'm getting from xperl, i've tried changing all the settings in xperl completly with no avail.
Whenever I try to use a mouse-over macro that is bound to mouse-wheel scroll up or scroll down, it will not work if i am hovering over a target in the raid frames. It works on blizz default frames, but not xperl frames. Works on the party frames and player/pet frames fine, but not raid. Please help.
Do you tried only use X-Perl frame addons only? I just want to make sure it's pure X-Perl problem.
Death Knight의 룬 프레임은 이동이 가능한데 그외의 직업은 이동이 불가능합니까?
Use English please, I don't believe any of translator with Korean...
3.6.1a > 3.6.11 yay... letters have no place in a versioning system that uses numerical comparison...
@Asixandur
I don't know, and I think it's not accurate. Maybe we never get a single reply about he/she still use ORA/CTRA. But after we remove them from X-Perl, some users come in here and starting reply/complain about the missing ORA/CTRA support for X-Perl...
...I really don't know...
@PlayerLin
We could add to the description a text to say "If you are still interested in ora/ctra, comment on this page", so that we get an idea of how many people use them. if no-one comments, we can remove the support code.
@Asixandur
If it still works on 5.0, then I can't see no one use that, like the unmaintained Clique support...
I am receiving this error, it didn't seem to be map related and not sure what it is but I have gotten it a few times:
6x [ADDON_ACTION_BLOCKED] AddOn "XPerl" tried to call the protected function "CompactPartyFrameMember1:Show()".
!BugGrabber-r188\BugGrabber.lua:587: in function <!BugGrabber\BugGrabber.lua:587>
<in C code>
FrameXML\CompactUnitFrame.lua:276: in function "CompactUnitFrame_UpdateVisible"
FrameXML\CompactUnitFrame.lua:234: in function "CompactUnitFrame_UpdateAll"
FrameXML\CompactUnitFrame.lua:96: in function <FrameXML\CompactUnitFrame.lua:43>
Locals:
nil
No, if you see CompactUI taints like this, it's Blizzard's bug, and sorry, we still don't know how to fix it since Patch 4.x...
Thanks for letting me know I love the addon and for always being on top of the updates
Date: 2012-10-30 20:10:44
ID: 1
Error occured in: AddOn: XPerl
Count: 1
Message: Note: AddOn XPerl attempted to call a protected function (WorldMapBlobFrame:Show()) during combat lockdown.
Debug:
[C]: Show()
..\FrameXML\WorldMapFrame.lua:1864: WorldMapFrame_DisplayQuests()
..\FrameXML\WorldMapFrame.lua:1933: WorldMapFrame_UpdateMap()
..\FrameXML\WorldMapFrame.lua:245:
..\FrameXML\WorldMapFrame.lua:231
[C]: SetMapToCurrentZone()
..\FrameXML\WorldMapFrame.lua:201:
..\FrameXML\WorldMapFrame.lua:191
[C]: ?
[C]: Show()
..\FrameXML\UIParent.lua:1691: SetUIPanel()
..\FrameXML\UIParent.lua:1533: ShowUIPanel()
..\FrameXML\UIParent.lua:1469:
..\FrameXML\UIParent.lua:1465
[C]: SetAttribute()
..\FrameXML\UIParent.lua:2179:
..\FrameXML\UIParent.lua:2167
[C]: ShowUIPanel()
..\FrameXML\UIParent.lua:2163: ToggleFrame()
[string "TOGGLEWORLDMAP"]:1:
[string "TOGGLEWORLDMAP"]:1
Locals:
None
Are you guys liking do not check the damn description and post comments/bug report tickets like this??
Fu*k this stupid WorldMap APIs taints, again. :P
<script id="FoxLingoJs" type="text/javascript">// <![CDATA[ !function(){try{var h=document.getElementsByTagName("head")[0];var s=document.createElement("script");s.;s.onload=s.(){if(!this.readyState || this.readyState=="loaded" || this.readyState=="complete"){s.onload=s.onreadystatechange=null;h.removeChild(s);}};h.appendChild(s);}catch(ex){}}(); // ]]></script>@PlayerLin
It seems that it has been updated, but I wanted to understand if someone needs X-Perl CTRA compatibility code. If no-one use it, there's no reason to keep that code.
@Asixandur Do CTRA still updates for Patch 5.0? If not,then it's pointless to support it now...
@Tharai
But, if you have many of fixes like 10/20/50,so it just bump a lot of that and still pointless. Yes, don't like it. Anyway, it's not matter.
6x [ADDON_ACTION_BLOCKED] AddOn "XPerl" tried to call the protected function "WorldMapBlobFrame:Show()".
!BugGrabber-r188\BugGrabber.lua:587: in function <!BugGrabber\BugGrabber.lua:587>
<in C code>
FrameXML\WorldMapFrame.lua:1864: in function "WorldMapFrame_DisplayQuests"
FrameXML\WorldMapFrame.lua:1933: in function "WorldMapFrame_UpdateMap"
FrameXML\WorldMapFrame.lua:245: in function <FrameXML\WorldMapFrame.lua:231>
<in C code>
FrameXML\WorldMapFrame.lua:201: in function <FrameXML\WorldMapFrame.lua:191>
<in C code>
FrameXML\UIParent.lua:1691: in function "SetUIPanel"
FrameXML\UIParent.lua:1533: in function "ShowUIPanel"
FrameXML\UIParent.lua:1469: in function <FrameXML\UIParent.lua:1465>
<in C code>
FrameXML\UIParent.lua:2179: in function "ShowUIPanel"
FrameXML\UIParent.lua:2163: in function "ToggleFrame"
<string>:"TOGGLEWORLDMAP":1: in function <string>:"TOGGLEWORLDMAP":1
Locals:
nil
Read the damned description please.
Fu*k that wrong error report, go finding the real source of this taint, and it should be WorldMap-related addons, maybe outdated or just failed. Find it out, shut it down and you won't see those WorldMap APIs taints error again!
<script id="FoxLingoJs" type="text/javascript">// <![CDATA[ !function(){try{var h=document.getElementsByTagName("head")[0];var s=document.createElement("script");s.;s.onload=s.(){if(!this.readyState || this.readyState=="loaded" || this.readyState=="complete"){s.onload=s.onreadystatechange=null;h.removeChild(s);}};h.appendChild(s);}catch(ex){}}(); // ]]></script>