BlizzBugsSuck
After every patch there are often a variety of bugs that crop up in the WoW UI. Many of them go largely unnoticed by users. AddOn authors have often made small addons to fix these problems. This addon intends to create a single installation for users that include whatever fixes the community can come up with for UI problems. As new issues and workarounds are discovered they will be added. As old issues get fixed they will be removed. Users benefit by having a single addon they can just keep updated to get the fixes. Blizzard benefits by having a single addon to look for our workarounds to their problems and hopefully things get fixed sooner.
Current fixes include:
- Fix an error when shift-clicking on category names in the tradeskill recipe list (new in 7.0)
- Fix an error when mousing over the Nameplate Motion Type dropdown in Interface Options (new in 7.0)
- Fix an error when scrolling the in-game addon list
- Fix the addon list sometimes incorrectly toggling the enable state of addons for other characters
- Fix the missing bonus area effects on the garrison shipyard map in non-English locales
- Fix the Interface Options window not always opening to the requested addon's options panel
- Fix taint caused by the Chat Frames use of UIFrameFlash (LibChatAnims)
- Fix the German localization using a whole word for the one-letter "day" abbreviation
- Fix the pet journal team buttons not being clickable to link a pet into chat
Previous fixes have included:
Fix category labels in the Interface Options and other windows wrapping and overlapping(Fixed in 6.2.2)Fix the German localization using the same word for the "Uncommon" and "Rare" item qualities(Fixed in 6.1)Fix the error in Traditonal Chinese clients that occurs inwhen the guild UI is first loaded(Fixed in 6.1)Fix the DEATH popup showing when reloading the UI even if you aren't dead(Fixed in 5.4)Fix reagent buttons in the TradeSkillUI not providing links when shift-clicked(Fixed in 5.3)Fix the PlayerTalentFame is nil error with the GlyphUI(Fixed in 5.2)Fix the poiButton error when opening the the map(Fixed in 5.0.4, possibly earlier)Fix whisper menu options and chat links for cross-realm players in LFR and BGs(Fixed in 5.0.4, possibly earlier)Block the exploit that allows AddOns from getting your Real Name from the Real ID system(Hotfixed on July 10th, 2010. BNSendWhisper now shows character name when whispering yourself.)Fix the buttons for DropDown Menu items being behind the background, making it impossible to click them (only happens to submenus and usually only for ones with a large number of menu items).(Fixed by 4.0.1)Fix for minimap ping not updating as you move making the ping appear to move locations as you move.(Fixed by 4.0.1)
Criteria for inclusion of a fix:
- Be identifiable as a bug as opposed to an intentional design. We will use the FrameXML source code to help determine this and the behavior of the UI to help determine Blizzard's intentions.
- Be transparent for users and not break any other UI element or addon (exception being malicious addons taking advantage of Blizzard UI bugs).
- Not require configuration options. If it's something some people might not want, it's not a candidate for inclusion.
The purpose of these criteria is to limit the fixes to things that everyone universally will want.
Just a few minutes ago, I installed your BlizzBugsSuck Addon for the distinct purpose of getting around the unclickable reagents in the tradeskill window. I still cannot click them to enter them into the AH search. Was told your addon would fix this, but it doesn't. If you need more info, please contact me. ty
Added a fix for the issue in 5.2 that causes reagents in the tradeskill UI to be unclickable (eg. for getting a link) due to GetTradeSkillReagentItemLink always returning nil.
@Shefki
Seems to work, thanks!
@cremor
Give the alpha a try. Should resolve the issue.
Is it possible to fix the GlyphUI bug that came with 5.0.4?
http://us.battle.net/wow/en/forum/topic/6470967787
Please see the Blizzard Bug Fix Addon Pack on Curse, which contains this and several other related addons that fix bugs in the Blizzard UI.
yeah, BUGGY secure code. the entire compactUnitFrame is a pile of crap. hundreds of taints per night, and no addons even touching the damn thing :\
There's not going to be a way to fix that from our side. Unit frame creation/display is all from secure code.
I'm loving the new compact raid frames. Unfortunately they are rather prone to bugs :( E.g. when using them in a 5-man group and someone joins (mid-combat or not), they do not update properly. Sometimes, a new unit frame pops up (as it should) but does not get colored properly, the name is "Unknown" or just the same as another party member's but I've also had situations where the unit frame would not pop up at all. Rather troublesome for a healer ;)
thanks for pointing me in the right direction! didnt know its intended to work like that however link you provided does what i need so all good :)
@sammael666, That's not a bug fix that's a feature enhancement. There are already addons that provide that feature as well. http://wow.curse.com/downloads/wow-addons/details/better-blizz-options.aspx
hi i recently discovered this and wanna say thanks, it was driving me crazy that i clicked on addon config only to have it find manually in the list in the end.
i recently noticed i am unable to drag and move the whole Options window, would it be possible to add a fix for that into this addon?
thanks and keep up the great work !
Fixed in 4.0.3.2, really not sure how it manages to get to that point in the code with that condition.
Lotsa of errors after last update, similar to this one :
3x !BlizzBugsSuck-4.0.3.1\BlizzBugsSuck.lua:140: attempt to compare two nil values <in C code>: in function `sort' !BlizzBugsSuck-4.0.3.1\BlizzBugsSuck.lua:171: in function `QuestMapUpdateAllQuests' Interface\FrameXML\WatchFrame.lua:1375: in function `WatchFrame_GetCurrentMapQuests': Interface\FrameXML\WatchFrame.lua:282: in function <Interface\FrameXML\WatchFrame.lua:239>: <in C code>: in function `SetMapZoom' TomTom-v40000-1.0.5\libs\Astrolabe\Astrolabe.lua:1075: in function `activate' TomTom-v40000-1.0.5\libs\Astrolabe\DongleStub.lua:78: in function `Register' TomTom-v40000-1.0.5\libs\Astrolabe\Astrolabe.lua:1127: in main chunk
Locals: (*temporary) = <table> { 1 = <table> {} 2 = <table> {} } (*temporary) = <function> @ !BlizzBugsSuck\BlizzBugsSuck.lua:124: (*temporary) = <table> { } (*temporary) = <table> { }
-and another right after: Date: 2010-11-28 11:19:17 ID: 2 Error occured in: Global Count: 1 Message: ..\AddOns\!BlizzBugsSuck\BlizzBugsSuck.lua line 140: attempt to compare two nil values Debug: [C]: ? !BlizzBugsSuck\BlizzBugsSuck.lua:140: !BlizzBugsSuck\BlizzBugsSuck.lua:124 [C]: sort() !BlizzBugsSuck\BlizzBugsSuck.lua:171: QuestMapUpdateAllQuests() ..\FrameXML\WatchFrame.lua:1375: WatchFrame_GetCurrentMapQuests() ..\FrameXML\WatchFrame.lua:282: ..\FrameXML\WatchFrame.lua:239 [C]: ? [C]: SetMapZoom() ...AddOns\Broker_Wintergrasper\Broker_Wintergrasper.lua:291: UpdateIcon() ...AddOns\Broker_Wintergrasper\Broker_Wintergrasper.lua:204: ...AddOns\Broker_Wintergrasper\Broker_Wintergrasper.lua:202 (tail call): ? [C]: ? [string "safecall Dispatcher[2]"]:9: [string "safecall Dispatcher[2]"]:5 (tail call): ? Ace3\AceTimer-3.0\AceTimer-3.0.lua:164: Ace3\AceTimer-3.0\AceTimer-3.0.lua:138
This one just poped with newest version, when I delivered cooking daily in SW: Date: 2010-11-28 11:15:02 ID: 1 Error occured in: Global Count: 1 Message: ..\AddOns\!BlizzBugsSuck\BlizzBugsSuck.lua line 140: attempt to compare nil with number Debug: [C]: ? !BlizzBugsSuck\BlizzBugsSuck.lua:140: !BlizzBugsSuck\BlizzBugsSuck.lua:124 [C]: sort() !BlizzBugsSuck\BlizzBugsSuck.lua:171: QuestMapUpdateAllQuests() ..\FrameXML\WatchFrame.lua:1375: WatchFrame_GetCurrentMapQuests() ..\FrameXML\WatchFrame.lua:249: ..\FrameXML\WatchFrame.lua:239
you should add the cogfix to this. it is after all the definition of a serious UI bug with 1 line tooltips inside instances. which is exacty what fix is, just check for isininstance and if true then disable 1 line tooltips.
@Freydis88 I found I could get links working again when I made sure the ChatFrame was not set to "Noninteractive". Try that.
@Freydis88, There's insufficient traceback in that for me to even begin trying to figure out what addon is causing that.