Originally Posted by jakgrant
Here's a screen shot, just so people know what probs there are, not sure how many in the screen shot and I've listed are entirely Mazzle though.
http://members.dodo.com.au/~jakgrant1/WoW-Mazzle.jpg
1) When you or some enemy is selected, the text and the health bar, etc, are to the left a little not by a huge amount, but enough. Not a big deal but looks a little untidy. I've tried re-mazzifying, and that doesn't correct it.
2) I've noticed Fubar-Topscore doesn't seem to work. I assume this is an issue with 2.4 damage changes ? Not part of mazzle, but just thought I'd query it, so I can go looking for a Topscore update.
3) Forgot to take a screen shot of this one, but the ATSW for trades. Again I'm sure not part of mazzle ? But as a LW-er, it's a little annoying, cos you have two categories someone has called leather, and ones leather type and one's armor, gah :P
Anyway, I'm sure 2 and 3 aren't mazzle, but 1, maybe, so if any tidying up could be done, would be good.
Oh, it's also really only relevant to this week, but how do we change the clock in Mazzle and the time zone ? I've forgotten, because I'm on the Khaz'goroth realm, and Blizz isn't aware, their time is an hour behind, because Australia actually didn't finish DST when they were meant to.
Thanks in advance,
J.
PS. I was looking through bugsack, and understood finally how errors were reported, because I was using an addon outside of mazzle called recipe radar, which kept giving bugsack errors, but that was because it was missing a lib of some sort called astrolabe.
So, I went back and looked at the bugsack errors that keep getting reported from witch hunt. Now I don't know if someone has mentioned this in the post, but I found out the solution and fixed witch hunt. I've now not got a bugsack error immediately from logging into wow from witch hunt. What I did was look for a copy of LibSink 2.0. I couldn't see it on wowinterface, but found it elsewhere, so downloaded the lib, dumped it in the addon folder, and voila. Working witch hunt. Only prob is I have nfi what witch hunt is. LMAO
|
Close... 1 + 3 are WoW client issues.. 2 is a due to Fubar_TopScore being a .svn version. to fix (mayproduce other problems) remove the .svn folder and update w/ jwowupdater
Originally Posted by sethgecko
I seem to be the only one who has issues with antagonist .
I can see the enemy casting bar but thats all. Basically all bars that could be seen on the lower right of the HUD are gone. Does any1 has an idea?
|
A start is to remove the preloader function stuff for now in the same manner as the WitchHunt temp fix in th OP. Lemme know how it works ad I'll look into fixing/replacing the preloader.
Originally Posted by griffin224
Jak, check the OP, the error you are getting is a preloader error, disable the line mentioned in the preloader/toc in the OP and bang, errors gone and witchhunt works again. Hope this helps.
|
It's importatnt for me to note this is a temporary solution that returns those mods to a usable state and shouldn't be considered a final solution.
Originally Posted by jakgrant
No, I know this, and it's been covered. The point I was making, and up above, was that I thought I'd found the witch hunt problem, because the Lib sink 2 library wasn't included in the witch hunt package, and the Lib sink 2 file was what causing some of the initial witch hunt problems. I checked myself through bug sack. But then I got the new errors for witch hunt after I included the lib.
As to OP ? I have no idea what OP is.
|
I was tripped up by that line of thinking at first too. Then I remembered the way other programming languages reports errors, dumping the error stack/trace. If you look at the first line of the error, the originating call is from !!MazzleUI_Preloader/!!MazzleUI_Preloader.lua or something like that... The rest of the info traces the call back to it's origin. the most likely place for the error to have occurred is the line given. Second most likely is within the function called based on the data it was called with. This will be in the code for the called function at the last line given.
Sorry about the OP abbreviation... I forget I've been on the tubes a long time and tend to abbreviate more than I should.
Originally Posted by Llydapdicter
I hate my computer. Cannot open a .toc file =( so cannot use JWow and I really really want too, lol.
Trying it with just notepad.... if this works we know two things, I am lucky and I am not good with computers.
|
When in doubt try notpad. It won't break anything and it may just work.
Originally Posted by griffin224
Don't mean to harp, just offering a suggestion - OP = Original Post. I doubted it at first and tried about 50 different things to get Witch Hunt to work and stop erroring. (I love it for tanking, makes it easy to interrupt that way.) Finally I broke down and removed the line in pre-loader and VOILA! WitvhHunt works great now. I Like you was positive it was a library error, but none of my tinkering worked.
Peneth, did you try deleting the line in Preloader.toc like the OP suggests? Would guess that will fix your witchhunt problem.
Daniel, you are not crazy, well not completely anyways. I have had the same issue for a LONG time. Do a mazzifcation, but try UNCHECKING Discord in the addon update panel, Mazzification should complete, then run just a DUF update, that should work, it is how I have been doing it for awhile now.
|
sounds like you guys are missing bits of DeTards updates/patches... I haven't had any issues with DUF since his updates. Though it's nice ot know the issue isn't new in 2.4...
Originally Posted by Banalina902
I disabled LightHeaded after that last big patch break and learned to live without it. How does that affect the fix shown above?
|
I think the old .svn nQuestLog will still work but you will get errors with any new quest that was added after that version of nQuestlog.
If you update both nQuestLog and LightHeaded as directed, you will regain full functionality in those addons.