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
Comments people make here are simply noting problems, many of them small, that they are experiencing, that's all, not personal criticisms.
Thanks in advance.
4.) Disable xperls debuff timers via the toggle switch and let omnicc do all my timing. I do not want to go this route though, as omnicc seems to be a second behind in debuff timing. This is how I first noticed the problem. Omnicc would say there was 8 seconds left on my scorch, while xperl was displaying 7 second. That is how I knew they were overlapping like this in the first place.
There are two things I plan to try.
1.)I use bartender4. So I can try and make my action/spell bars smaller and then try and scale omnicc down.
2.) figure out how to add the target frame to some type of blacklist function in omnicc.
*3.) Zek labels the target debuff frames with the nocooldown count specifier. I dont know if my defining them that way if it would interfere with the xperl's own debuff timing.
I'm not having a problem with cooldown timers and I have both xperl and omnicc.
maybe you guys need to adjust your addons..
I think I'm going to start using Grid anyway.
I think one key issue people are having is this: OmniCC does not have any clue about what it is displaying cooldown text on. It could be buffs, action buttons, casting time, items...whatever. This is actually the reason OmniCC is able to work on everything in the first place.
OmniCC knows the following, though:
* The duration the timer. This, along with the minimum duration setting is used to determine if OmniCC should show text or not. This is also used to determine if a pulse should happen or not.
* How big the thing is. This, along with some magic math and the minimum scale setting, is used to determine if OmniCC should show text or not.
* A guess at the icon of the thing it is showing text for. This is used for the pulse.
* If .noCooldownCount is set or not. This is used to determine if OmniCC should show text or not.
I don't implement a blacklist for specific frames because of the following:
* The issue is typically fixable via adjusting the minimum scale option. Yes, this doesn't work if your debuffs are the size of your action bars.
***** Other addon authors can block OmniCC from displaying text (and CooldownCount) via the noCooldownCount flag.****
* I don't want to pollute OmniCC with addon specific code.
Please make this change.
I do not want any timers to display on my target debuff frames, besides the standard xperl timer. Right now omnicc is causing an issue for alot of people where the two timers are overlapping. This needs to be added so that omnicc will not display its timers on the target frame. Please make this change asap!
- Added option to only show cooldown for your own buffs and debuffs.
What does that mean? Will this help fix the problem with omnicc?
Regarding the movement of X-Perl frames, I ended up using a Mod called FluidFrames
(http://www.wowinterface.com/downloads/info7080-FluidFrames.html#info).
This allows me to move almost anything in the UI. I've used it with X-Perl to fine tune where everything is placed and it saves the information.
saving my settings while in bear form, logging out and back in will save it permanently. it's because of the druid mana bar while shapeshifted. probably something to do with conflicting coordinates saved in the saved variables folder's xperl LUA file.
saw that someone even had this problem in the Beta (comment by Daelus: http://wowui.worldofwar.net/index.php?p=mod&m=2855).... while I've found a temporary solution hopefully this gets fixed so that any others with this problem don't have to take the time and effort that I did...
the top one is what it looks like when I log in. the bottom is what I want it to look like--and what it looks like after I load my frame layout from another character (via the list in the bottom left of the xperl options window). I've tried to manually move it without loading from my other character, as this is the only frame that doesn't save.