Patch 2.4 bugfix thread

[Aethenelle]

Post problems you are having w/ the mazzifier and MazzleUI here. I will try to fix them as soon as possible.

If you get errors please list what you were doing and post the error message from the bugsack (it's on one of the FuBar bars at the top or bottom). If the error is during mazzificaion, the mazzification step it occurs in would be helpful. These are printed out to the chat window as they are performed.

A bunch of people have asked when a new release will be made. To answer, I will take a page from the Book of Blizzard(TM) and say, "When it's done." With the combat log changes came quite a bit more work than I had anticipated. At this time three mods need to have their configurations changed and Mazzifier code updated. This will take some time. For now, we can put out fires so MazzleUI is usable but after the fires are out theres a bunch of rebuilding to do so full functionality can be restored.

First... the CVar UnitNamePlayer was removed. Addition CVars were added to replace it and increase functionality. This creates an error on mazzification where UnitNamePlayer is not found.

Fix:
Full instructions here

Second... Combat Log changes... the second chat window (Private) is the only location for the new combat log and Simple Combat Log has not yet been updated. This will cause windows 6 adn 7 to be empty. Unless SCL is updated we will have to move some windows around and setup the new log, but for now I'm going to see if SCL gets updated. If not I will post code to mazzify the new log.

edit: SCL, it appears, will NOT be updated for patch 2.4 and the old combat log windows *will* remain mostly empty until a patch is made. (SCL still picks up loot messages) Due to the way the new combat log works the fix will involve placing a single window in the old windows' location, setting up appropriate filters and removing SCL.

Edit further: fire up WAU or JWoWUpdater and install CombatFilter. You'll have to set it up manually to send data to chat windows 6 and 7 using /cfilter for the time being. It's a pretty shiny (and almost transparent) replacement for SCL

Another Edit: If you remove SCL do not mazzify it. Uncheck the box to update it's settings on the last addon page of the mazzifier.

Third... Bongos3... Still working on it... It will take some more time but the new features in Bongos3 at least match the functionality of the Mazzle version of Bongos1. however I will have to change a couple functions w/in Bongos3 so we'll still have our own version of Bongos but the changes are far fewer and we should be able to easily implement them in the new and updated versions of Bongos3 as Tuller fixes bugs and things. for now it's also still in beta but I hope to have the mazzifier and Bongos3 ready for our purposes in the next week or two.

Fourth... Witchhunt... This is an error in !!MazzleUI_Preloader... for now disable witchunt... I need to poke through the code here to see what's going on... Turns out WitchHunt is dependant on the combat log. As such, it's been largely recoded. Good news is getting rid of the errors is easy. Bad news is: It will take me a while to straighten out all the changes and return it to it's former Mazzified look.

Temporary workaround to get rid of the errors is to remove or comment line 23 of !!MazzleUI_Preloader/!!MazzleUI_Preloader.toc (reads: Mods\WitchHunt.lua) or disable WitchHunt.

Fifth... Scrolling Combat Text... another combat log based mod... Options UI placed in new interface panel old options seem to have been lost. No erors (woot!!) but mazzification probably needs to be updated. For now any settings probably have to be done manually. If you disable SCL make sure you don't try to mazzify it, uncheck the setup box on he addon selection page of the mazzifier.

Sixth... Lightheaded/nQuestLog/Cartographer_Waypoints... these are listed together because the problems is a mix of all three... The added feature of being able to link quests caused LightHeaded to be largely recoded this is causing at least two problems:
1. nQuestLog no longer properly opens Lightheaded when you select a quest.
2. Lightheaded doesn't properly create a waypoint in cartographer when a location is clicked.

Temporary solution:
remove the .svn folder from the nQuestLog folder
make sure WAU or JWoWUpdater are set to not split addons (this was the part breaking cartographer)
update from wowace.com (JWoWUpdater or WAU)
set the frame anchor for the nquestlog minion to TOPLEFT using the icon in FuBar
reposition to the corner it was in manually

UPDATE: It seems mazzification for the new nQuestLog already works fine. Can someone verify this on a clean install?

Seventh... SuperInspect... Actually this has been broken for a long time (since 2.3 i think) due to +dmg being added to +heal gear. It's now even more broken and just plain doesn't work. I've heard Examiner is a good replacement for this mod. (I tried it out... Kinda shiny)

Eighth... TopScoreFu... Has not been updated for 2.4 yet... Don't know if it will...
EDIT: It was updated... should be working now

Ninth.... DUF.... If you are having issues mazzifying related to DUF look here for instructions to update DUF. This hasn't been fully vetted as a solution to all DUF problems but should work for those wanting to help test.

I'll try to get most of these rolled up into a workaround/fix patch file sometime this week.

[Aygen]

Thanks for the updates !

[Rollered]

Nice work, good to see there is progress for fixes.

[alenda]

I found three instances of UnitPlayerName in the Mazzifier.lua, but I was wondering if it occured anywhere else? .lua's and linenumbers would be appreciated. ^^

[Dridzt]

I'm not a MazzleUI user but I'm posting here to tell you that SCL will not be updated for 2.4,
as it has - in essence - been included to the default client.

[Aethenelle]

Originally Posted by Dridzt I'm not a MazzleUI user but I'm posting here to tell you that SCL will not be updated for 2.4, as it has - in essence - been included to the default client.

Good to know, I will work on moving window positions around and setting up the correct filters for the new combat log. I will say however that SCL did have one function over the new one in the default client: the ability to have more than one combat log window. (or at least thats how it worked on the test realm.. I'll check again once I can log into the new live servers)

[VincentSDSH]

Originally Posted by alenda I found three instances of UnitPlayerName in the Mazzifier.lua, but I was wondering if it occured anywhere else? .lua's and linenumbers would be appreciated. ^^

Mazzifier.lua around lines 387, 389, 409
Mazzifier_Configs.lua around lines 348, 3382

[Viciusan]

Can i run WAU tomorow.
And if i then aply these fixes , will the Mazzle UI work ?

Ofc exept the combat logs

- ViCi -

[VincentSDSH]

No, Mazzle itself has to be updated, as would DUF I expect, neither are part of WAU.

[Crenthius_UB]

Running wowaceupdater isnt a bad idea to update those ACE addons, but it wont magically fix all of mazzle. Some coding changes will have to be manually made unless you want to wait a few days for a patch compilation to be posted.

[bothersome]

To summarize: Changes need to be made to the following files at the following lines.

Mazzifier.lua around lines 387, 389, 409
Mazzifier_Configs.lua around lines 348, 3382

Replace all lines that contain

SetCVar("UnitNamePlayer","1" or "0")

with the following:

SetCVar("UnitNameFriendlyPlayerName", "1")
SetCVar("UnitNameEnemyPlayerName", "1")
SetCVar("UnitNameEnemyPetName", "1")
SetCVar("UnitNameEnemyCreationName", "1")
SetCVar("UnitNameFriendlyPetName", "1")
SetCVar("UnitNameFriendlyCreationName", "1")

If the number at the end is a 1 in the original UnitNamePlayer line, then use a 1; if it is 0, use a 0.

Use notepad to edit the file. Turn on the status bar in notepad to enable line numbers. Line numbers will change as you add lines. Begin with greatest line to be modified on each file to minimize confusion.

Hopefully, the rest of the fixes are this easy.

Also, in addition to SCL, Damage Meters is not being updated for 2.4. Suggest using Recount as replacement.

[Llydapdicter]

Originally Posted by Crenthius_UB Running wowaceupdater isnt a bad idea to update those ACE addons, but it wont magically fix all of mazzle. Some coding changes will have to be manually made unless you want to wait a few days for a patch compilation to be posted.

May want to run JWowUpdater-1.87 as well.

[bothersome]

Originally Posted by Llydapdicter May want to run JWowUpdater-1.87 as well.

If you run any other updaters than WAU, make sure you want and like and don't mind reconfiguring the new Autobar. It is completely different (read: easier to use, but very different from previous versions), but after some configuring it will work in the current position. WAU keeps this locked and doesn't update it.

[Thoragh]

ADDON UPDATED

[2008/03/25 17:32:56-351-x7]: FuBar_NameToggleFu\Core.lua:113: Couldn't find CVar named 'UnitNamePlayer'
FuBar_NameToggleFu\Core.lua:113: in function `OnTooltipUpdate'
FuBarPlugin-2.0-63898:369: in function `runChildren'
Tablet-2.0-64130 (TabletLib):2356: in function `children'
Tablet-2.0-64130 (TabletLib):2400: in function `Open'
Tablet-2.0-64130 (TabletLib):2534: in function <Interface\AddOns\TabletLib\Tablet-2.0\Tablet-2.0.lua:2528>
FuBarPlugin-2.0-63898:418: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:417>

  ---

This is the line it is referencing in the LUA

"text2", GetCVar("UnitNamePlayer") == "1" and L["tipshown"] or L["tiphidden"],

Not sure if you want errors in here but this one is another error about unitnameframe and the addon hasn't been updated in over 90 days according to WAU

[SilentBeast]

Since it's not on the first post and noted and I know I saw it in the thread at one point. Dr. Damage isn't showing information on my bar buttons. Can't remember if it was because the author was working on it or if it was yet another conflight like the pet bar of bongos. If anyone has a workaround or such let me know otherwise I guess it's just gonna have to stay that way till Anth get's the new version out for the bongos3 changes.

Other then that I haven't had to many issues except an error with the bag mod when closing out of the bank.

One more quick thing how do I purchase and equip bank bags with the bag mod turned on?

[DocEVL]

Originally Posted by SilentBeast Since it's not on the first post and noted and I know I saw it in the thread at one point. Dr. Damage isn't showing information on my bar buttons. Can't remember if it was because the author was working on it or if it was yet another conflight like the pet bar of bongos. If anyone has a workaround or such let me know otherwise I guess it's just gonna have to stay that way till Anth get's the new version out for the bongos3 changes.

The new Dr. Damage does not workj with bongos1 that comes with Mazzle. You will need to wait for the bongos3 upgrade. Unfortynately I know of no other way, short of installing bongos3 and manually configuring.

One more quick thing how do I purchase and equip bank bags with the bag mod turned on?

In the baggins configuration you can specify an option to display normal bank in addition to the baggins bank tab. You can then purchase additional bank slots and add your bags.

[WoWUIUser]

I see SimpleCombatLog is not usable in 2.4
The combat logs in mazzle are completly black.I hear there is not going to be an update..hopefully that changes..but if no update comes can anyone figure out another way to fix the combat logs?Such as changing words in files etc.
Thank You!

[sabias]

Mazzle.. pls help.. I am close to the point of breaknig my Pc.. I just wanna play WoW now.. nothing is working.. I installed MazzleUI just like the install guide says to.. did everything the way I was told. wel. everything but the skins are saying there is dependacey missing. now my fonts are all weird looking. my UI looks odd and coverd by other non moving UI.. Help me DL MazzleUI correctly.

[Banalina902]

See the thread that's just 3 above? With the link on how to download correctly? Go there and make sure you're doing it that way. You're obviously missing something as there should be no missing dependencies if you downloaded correctly.

And remember to extract into the WorldofWarcraft directory only. Do not copy and paste.

[Aethenelle]

Originally Posted by sabias Mazzle.. pls help.. I am close to the point of breaknig my Pc.. I just wanna play WoW now.. nothing is working.. I installed MazzleUI just like the install guide says to.. did everything the way I was told. wel. everything but the skins are saying there is dependacey missing. now my fonts are all weird looking. my UI looks odd and coverd by other non moving UI.. Help me DL MazzleUI correctly.

Manually reinstall BanzaiLib from wowace.

The updaters don't look to see a non wowace mod is using a library before deleting it.