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
wouldn't if is_cata then
XPerl_Player_InitWarlock(self)
XPerl_Player_InitPaladin(self)
XPerl_Player_InitMoonkin(self)
else
XPerl_Player_InitDK(self)
XPerl_Player_SetupDK(self)
end
just break shit? that'd only support DKs on versions older than 4.0 and load nothing for DKs in 4.0 and up. personally i just uninstalled xperl and installed pitbull. raid frames are well beyond usable, xperl is fine, long as you don't raid, if you raid it's completely useless.
edit neermind uninstalled pitbull cause even though it's functunal it's gotta be the ugliest least configure friendly frames i've ever seen. i'll just raid with no raid frames at all.
Time: 10/12/10 21:35:48
Count: 4
Stack: Interface\AddOns\XPerl\XPerl_Usage.lua:49: in function `TooltipInfo'
Interface\AddOns\XPerl\XPerl_Usage.lua:36: in function <Interface\AddOns\XPerl\XPerl_Usage.lua:31>
[C]: ?
[C]: in function `SetUnit'
Interface\FrameXML\UnitFrame.lua:152: in function `UnitFrame_UpdateTooltip'
Interface\FrameXML\UnitFrame.lua:139: in function <Interface\FrameXML\UnitFrame.lua:126>
Locals: self = XPerl_UsageFrame {
0 = <userdata>
CHAT_MSG_ADDON = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:316
DecodeModuleList = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:395
CheckForNewerVersion = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:75
MakePacket = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:373
ParseCTRA = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:323
ProcessXPerlMessage = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:91
throttle =
}
PARTY_MEMBERS_CHANGED = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:304
GeneralTooltip = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:164
RAID_ROSTER_UPDATE = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:292
SendModules = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:337
PLAYER_ENTERING_WORLD = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:248
TooltipInfo = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:48
}
tooltip = GameTooltip {
0 = <userdata>
default = 1
updateTooltip = 0.066999998688698
SetUnitDebuff = <function> defined =[C]:-1
SetUnitBuff = <function> defined =[C]:-1
comparing = false
SetUnitAura = <function> defined =[C]:-1
shoppingTooltips =
}
}
unitid = "player"
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index field 'tooltip' (a nil value)"
conf =
pet =
}
}
UnitFullName = <function> defined @Interface\AddOns\XPerl\XPerl_Usage.lua:40
Right now, when I join a raid, my x-perl frames show all errors, the blizz frames pop up and my game crashes. Please help! Anyone else having this problem?
everything is right except that in the Init DK portion where you removed joddies hack you missed an end which is the one under RuneFrame.runes = {} and the if is_cata should not be above local XPerl_Player_InitDKCAT it should just say local XPerl_Player_InitDKCAT and then you should add XPerl_Player_InitDKCAT(self) to the line with the others like XPerl_Player_InitMoonkin(self) or XPerl_Player_InitPaladin(self) also in the player buff changes you should move the elseif for eclipse up one so it should look like this
also line 1178 which says this
should be changed to this to fix the Paladin extend portrait problem that Raz was talking about a couple comments down. I put it in here as a holy power fix but after it was in i found out its not necessary unless you attach the bars to the portrait frame instead of the stats frame.
@Brounks : I do this changes on my end based your comment.
XPerl_Player.lua line 73, removed 73-74 and changed to...
Same file , line 1188
Don't get your XPerl_Player_SetupDK and InitDK shit... :(
...right? Or...?
Added "local XPerl_Player_InitDKCATA"(was your XPerl_Player_InitDKCAT) on line 30, below of "local XPerl_Player_InitMoonkin", with client version check.
Move up "local is_cata = select(4, _G.GetBuildInfo()) >= 40000" to line 26, above of "local XPerl_Player_InitDK"
Added XPerl_Player_InitDKCATA function code(was your XPerl_Player_InitDKCAT) on end of file.
About XPerl_PlayerBuffs.lua...
Right?... If all of those are right then I'll (or someone will)commit... zhTW/koKR still on 3.3.5. :(
Also Mysicalos i wrote a better DK rune fix basically i made all the current stuff in XPerl_Player.lua for DKs which is XPerl_Player_InitDK and XPerl_Player_SetupDK stuff only run if your client is wotlk and then i basically copied what i did for the warlock/holy power bars so DK runes will actually work when 4.0 goes live. its quite a bit of changes. starting on line 73 in XPerl_Player.lua i made this change
then i made this change at line 1188
then i made these changes i basically added the get build info at the top of the the InitDK section and deleted joddie's hack fix which includes the end below RuneFrame.runes = {} and added another end at the very bottom above XPerl_Player_SetupDK
then i did the same to XPerl_Player_SetupDK added the get build info and another end at the very bottom. that is the last of the changes made to existing code now you add new code.
at the top around line 30 i added this local XPerl_Player_InitDKCAT.
then i added it to the load if is_cata with the other ones. on line 83.
then i added this at the very bottom of the file under the existing DK stuff.
NOTE: Do not change runed to runes or rune it gives tons of errors i tried that already =P
then i added this to XPerl_PlayerBuffs.lua
also the elseif for runed and eclipse in XPerl_PlayerBuffs.lua should be above this or the buffs appear wrong depending on if you have extend portrait checked or not.
ya playing a pally
@Raz what class are you playing for the extend portrait problem? If it is paladin i know what the problem is.
@mysticalos i am not sure if you really care but when i was doing all the frames i mostly just copied joddie's warlock fix and just made changes to get it to load holy and eclipse bars and i am not sure if you noticed this but all the frames are attached to the stat frame. So all the buffs appear under the stat frame as well instead of appearing under the portrait. If you want to change this for warlocks just edit lines 1262 and 1263 to say self.portraitFrame instead of self.statsFrame and for paladins edit lines 1302 and 1303 to say the same thing and for Moonkin edit lines 1346 and 1347 to say the same thing.
Then edit line 1175 to say
or you can change the first number in XPerl_PlayerBuffs line 147 which is 3 in this example to a stupidly high negative number i haven't quite found the number but i know that -20 barely made a dent in moving it left