WowAce

Why did you take my post down and not reply to it yesterday? Is there something your not telling us about this add-on?
This leads me to believe that I am going to have to uninstall WoW, wipe my registry and reinstall because your add on messed up WoW?

Guessing it was removed because you're being combative and that if you really have disabled the addon, then there is no way it can interfere with WoW.

Now, if you want to really make sure there are no addons installed that could cause issues, I'd suggest renaming your C:\Program Files (x86)\World of Warcraft\Interface folder to something like Interface-old or something similar. Do the same for the WTF folder as well. Make sure you do this while WoW is not running. The next time you start WoW, the folders will be remade with only Blizzards own addons/information. If that still does not fix your issue, then there is likely a file missing or corrupt in your WoW install which is not the fault of this addon as those two folders I mentioned are the only two places this addon places information.

We can't "take down" any ticket, it just closed, if you change options from filter to all and you can see it.

http://www.wowace.com/addons/xperl/tickets/1692-no-player-or-taget-frame-after-disable-uninstall/

I can understand why the ticket closed, since it's not possible X-Perl still "affecting" after uninstalled, unless some other addons still try to hide Blizzard default ones.

You can try resetting WTF directory like spiritwlf said... (Deleted anything in the WTF directory will resetting your addons settings, but also resetting some settings on WoW Client, backup them before you try to do that.)

Not sure what's happened on your end, sadly. But it doesn't needed to uninstall your whole WoW installation. Just make sure you're already quit WoW, move out the directory that store all 3rd-party addons(or delete them), then start the game and see what happens.

%WoW installation path%\interface\addons

Remember, you must quit the game before try to move/delete the addons directory to elsewhere(will be reset to default ones unless it's not RIGHT directory), and start the game, the default addons should be back, unless there is something wrong with your WoW installation.

If you were using Curse Client or some sort of integrated packages/tools of addons, try uninstall them all and just manually install addons. (I just guess, if you're install your addons manually already then it doesn't matter.)

If you can see Blizzard ones after you "reset" addons, then something wrong with addons you installed. Are you really sure you're only using X-Perl before you can say "it's fault by X-Perl", your description from ticket #1692 didn't explained what addons you actually installed with X-Perl. Better, please take a screenshot of inside "%WoW installation path%\interface\addons", let us see what addons you actually installed in your WoW.

Since Blizzard default addons SHOULD come back after removing Unitframe addons, so it may something go wrong but unfortunately I never encountered such problems like your, and it should not happens. (I know some of addons can totally disable/hide Blizzard addons silently but it's not in normal case.)

There's a general misunderstanding about add ons and how they affect wow. A lot of times people come here (not mentioning the Recount or DBM ticket trackers) to report their problem with wow. If you say you disabled our add-on and the problem persists, It's a wow problem. Addons are not code mods or cheats like other games have. They are just interface modifications. The game doesn't get changed by any means by the add ons. There is no way we can possibly destroy your game installation, at all. That said, we're a very small team trying to handle a very chaotic add-on used by a lot of people and we don't have time to answer wow support questions. The official wow forums are there for those means. Make sure you read those comments and you clearly understand what we're saying in a short time period, after which this ticket will be closed as Invalid.

Thanks

@Asixandur: Go

Bottom line, at least all ticket are exist since forever, just filtered by default.

And I wonder if d3fc0n1976 still coming back and check this ticket? I hope so. :p

I think he probably won't. He's probably succeeded in fixing his problem.

@Asixandur: Go

Nah, I just hate that.

Well XPerl force hides player frames in the function called "XPerl_BlizzFrameDisable" (moves them outside of the screen (lol)) on it's first run, which gonna be still disabled even when you disable/uninstall the addon, since it's stored in blizzard's code in the "layout-local.txt" for each character. And it's pretty sad the devs don't know that.

@Resike: Go I didn't know about that. Could you help me understand why no-one has ever reported this problem? My unit frames come out if I disable XPerl.

@Asixandur: Go

I had this issue since a long time, but since i know how to fix it and i never wanted to use the blizzard frames, i didn't really cared about it.

Seems like it only happens if the user moved the target/player/focus frame by the default blizzard rightclick unlock move frame mover, or used another 3rd party addon to move thoose frames.

Made some changes with r876 about it, it should work, but better to do some testing. Edit: The repo server seems to be slow today.

@Resike: Go

>Seems like it only happens if the user moved the target/player/focus frame by the default blizzard rightclick unlock move frame mover, or used anther 3rd party addon to move thoose frames.

It does explains why this problem is too hard to found......for me......since I never used Blizzard default unitframe addons, when started to use X-Perl from TBC...wow, that's long time ago...

I would like someone who had this problem to tested the latest alpha version, but...

Whatever.

@PlayerLin: Go

I've tested that and it worked for me, however what needs more testing is that the hider hookscript, like doing bgs, raids, pet battles, entering vehicles or anything else which might reshow thoose frames.

@Resike: Go

Thanks for your help, Resike. We really appreciate that.