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
can you provide a more detailed error quote, using bugsack or similar? Also, does your FrameXML.log file in your /WorldOfWarcraft/Logs/ folder and see if there are any errors related to XPerl.
Using 362 I have no error on startup from Xperl, however, I also do not use the Raid side of Xperl, and its been having some issues lately. Since I don't use it, and PlayerLin doesn't really use it, we haven't been able to really do much for that part of Xperl. The normal Player/Party/Pet/Party Pet/Arcane Bar/Custom Highlight/etc modules work without error for me.
For this is obviously a timing problem, it's quite likely that it doesn't
occur for everybody. It will depend on how many addons or rather on how many settings are loaded during startup.
So, even if you cant reproduce the error, please check whether you have correctly reflected the changes that blizzard has introduced with 3.0 regarding firing of events.
Or to put it simpler: Shouldn't you use the ADDON_LOADED event (after 3.0) wherever you have been using VAIABLES_LOADED (before 3.0)
Thanks, XLION
This is annoying, because I posted the fix here (for version 3.07__3.3_Release).
X_Perl still doesn't reflect the changes that blizzard has introduced to the
Adddon loading process and firing of events with 3.0.
-- quote http://www.wowwiki.com/AddOn_loading_process --------------------
Until 3.0, VARIABLES_LOADED used to fire upon completion of the addon loading process; since 3.0, it is fired in response to CVars, Keybindings and other associated "Blizzard" variables being loaded, and may therefore be delayed until after PLAYER_ENTERING_WORLD. The event may still be useful to override positioning data stored in layout-cache.txt
----------------------------------------------------------------------------
Line 630-660
Do you mean all "VARIABLES_LOADED" must change to "ADDON_LOADED" ?
(Maybe others file should changed too? like XPerl_RaidFrames\XPerl_Raid.lua Line 78 and 1112-1131)
If yes, it's easy task but I can't test as I was said, I don't really play with RAID shit...
(I checked your post on below, but I found more "VARIABLES_LOADED" on other files that you didn't listed, should I change that too? I don't want to fixed this bug but broke anything. :3)
because that was -- in my case -- sufficient to solve
my 2 problems.
1. A LUA error from RaidHelper on every logon
2. The picture in my player's nameplate was often blank/black after logon.
For me it's even harder to tell, if all occurrences of "VARIABLES_LOADED" can or should be replaced by "ADDON_LOADED",
because I'm neither involved in X-Perl development nor am I
experienced in WOW addon programming at all ...
I actually hoped that the author / some developer would read
my post and would say <<ah yes, we can or even should (after 3.0) switch x-perl's initialization code to use the "ADDON_LOADED"
event>>
Furthermore I think that such a decision can't be made based
on tests due to the "depends on timing" kind of the problem.
Cheers, xlion
Because this two bugs didn't happens in my end, I'm suspect maybe some other addons can cause this bug happens, but I still can't sure...
I'm afraid if I change that will cause other problem or find that's not X-Perl bug in later...
So needed more detail about what's situation will cause those bugs happens, like what addons loaded with X-Perl or something. :)
So when it doesn't occur with all other addons disabled or doesn't occur for somebody nothing is proven.
So my suggestion needs to be "verified/disproved from theory" which requires deep knowledge of the X-Perl code.
If that can't be done, we are stuck.
Luckily I have saved my patch, so next time when a new release of X-Perl comes out and I run into the bug again,
it wont take much time to fix it for me.
Thanks, xlion
http://www.wowace.com/addons/xperl/files/256-r362/
Curse only appears the release versions, so it didn't update.
*flee*
-OR-
Using the Curse Client, you right click on it and select Alpha as the release type.
Either one will accomplish the same goal, using the curse client keeps you up to date however.
This is extremly confusing espically when this is the main addon i use to help with my tanking a bit. Is there an update anywhere?
Turn off percentages; Mana percentage stays enabled.
FIX:
The following 4 lines of "XPerl_Player.lua" should be removed:
if (not self.statsFrame.greyMana) then
mb.text:Show()
mb.percent:Show()
end
^ Fixed several of my issues. Thanks eurymachus!