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 the API to open to an addon's configuration category to actually open to it and scroll to it.
  • Fix the PetJournal drag buttons cannot be clicked to link a pet into chat
  • The translation for time abbreviations for a single letter in the German Locale is wrong and are 3 letters. Put them back to a single letter. (Half fixed by 4.0.1)
  • Fix taint caused by the Chat Frames use of UIFrameFlash (LibChatAnims).
  • 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)
  • 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 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)
  • Fix the PlayerTalentFame is nil error with the GlyphUI. (Fixed in 5.2)
  • Fix reagent buttons in the TradeSkillUI not providing links when shift-clicked. (Fixed in 5.3)
  • Fix the DEATH popup showing when reloading the UI even if you aren't dead. (Fixed in 5.4)

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 this criteria is to limit the fixes to things that everyone universally will want.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Quaiche Quaiche Aug 24, 2010 at 07:14 UTC - 0 likes

    @Freydis88 I found I could get links working again when I made sure the ChatFrame was not set to "Noninteractive". Try that.

    Last edited Aug 24, 2010 by Quaiche
  • Avatar of Shefki Shefki Jul 20, 2010 at 19:52 UTC - 0 likes

    @Freydis88, There's insufficient traceback in that for me to even begin trying to figure out what addon is causing that.

  • Avatar of Freydis88 Freydis88 Jul 17, 2010 at 20:29 UTC - 0 likes
    @Shefki: Thanks... actually I hoped, there would be a fix, that helped me get rid of that bug without an addon update, since the author seems to have abandoned it. I keep on getting this message in BugSack: ["message"] = "Interface\\FrameXML\\UIParent.lua:2567: attempt to compare nil with number:\n\nLocals:|r\n\n ---", ["type"] = "error", ["time"] = "2010/07/14 00:26:46", ["session"] = 20, ["counter"] = 22438, }, -- [19] Do you know by any chance which addon may be causing this? Greetings and thanks, Freydis EDIT: Advanced Tradeskill Window has NOT been abandoned, as I found out...
    Last edited Jul 17, 2010 by Freydis88

    George Orwell:


    "Political language is designed to make lies sound truthful and murder respectable,

    and to give the appearance of solidity to pure wind."

  • Avatar of Shefki Shefki Jul 17, 2010 at 06:45 UTC - 0 likes

    @Freydis88, the addon should be updated to fix that. It's not really a Blizzard bug that they changed the API when doing a massive overhaul of the chat system.

  • Avatar of Freydis88 Freydis88 Jul 16, 2010 at 06:28 UTC - 0 likes

    Since the latest patch, it is not possible to link items or recipes to the chat anymore, when running certain addons, for example Advanced Tradeskill Window. http://wow.curseforge.com/addons/advanced-trade-skill-window/

    Is it possible to fix this with BlizzBugsSuck?

  • Avatar of Shefki Shefki Jul 16, 2010 at 00:11 UTC - 0 likes

    @Citlalin, Messaged the author to ask for permission to merge his code.

  • Avatar of Citlalin Citlalin Jul 15, 2010 at 23:37 UTC - 0 likes
  • Avatar of mysticalos mysticalos Jul 13, 2010 at 05:16 UTC - 0 likes

    i did report it on bug report forums when i discovered it. maybe they took it serously even though they didn't reply? i'll disable addon on my end and see if i can reproduce it anymore.

    as for shadowed's fix. I agree that clearning it on zoning, or on combat end etc isn't good for users. he clears it pretty accessively wihch does clear it when you don't need to and has adverse effects. but if you ONLY clear it when it's simply not working after UNIT_SPELLCAST_SUCCEEDED from player, at this point i don't think anyone would be upset they cleared it if they want to recieve any future combat events. otherwise, what's the point of a combat filter or addon that uses cache like HitsMode5 if there will be no new items added to cache or combat log at all. It does seem like a moot point to try not to break addons or users settings if those settings/addons themselves are rendered useless by the bug (preserving the last fight by giving up any log on next one, an eye for an eye either way. Just picking your poisen, do you want the last fight, or the current/next one). I just suggest you don't go to extreme of clearing it for "good measure" approach like what shadow does on zone change etc.  But at same time i see your point too. If the issue is even debatable then it isn't 100% to liking of everyone, which is what you want. But if it was in blizzbugssuck, and addon gains more and more momentum, it would be more presssing for blizzard to fix such an old and crappy bug ;)

    Last edited Jul 13, 2010 by mysticalos
  • Avatar of Shefki Shefki Jul 12, 2010 at 20:37 UTC - 0 likes

    @MysticalOS, I tried duplicating the AFK issue with battle.net and I couldn't. Seems like this was some sort of server side problem and your Synchronize call was coincidental to when they fixed it on their side.

    As far as the combat log fix, the problem I have with including it is that it causes the in game combat log window to be empty when you change filters. It's easy to argue that it's better to have a working combat log, but this fix has a negative user facing behavior. So users need to be knowledgeable about what it does and possibly have configuration options to change the behavior to suit their preferences. Which puts it outside the scope of this addon.

    Last edited Jul 12, 2010 by Shefki
  • Avatar of mysticalos mysticalos Jul 10, 2010 at 22:13 UTC - 0 likes

    Bnet has a tendancy to kick you for being afk much shorter periods of time than actual realm allows. As little as 5 minutes of afk can cause you to become perminently disconnected from battle.net even when you return to your char. It's annoying when you got to fix a dinner plate, or let the dog out and come back to "battle.net is not currently available" cause you got afk kicked from it barely being afk that long. I came up with a way to prevent this. If you execute SynchronizeBNetStatus() every few min, for me i scheduled it to execute every 4 min, you can be afk until the realm actually kicks you offline, without ever losing battle.net functionality. Pretty much works like a connectoin keep alive to battle.net to keep it from giving you the boot. I'm just not sure if this is a blizzard bug/oversight or intended design. I asked on forums but didn't get an answer yet. But throwing this out there :) No more relogging completely just to get bnet back all the time. :)

    in regards to combatlog fix. It doesn't really need options. if it beaks clear entries. All the extra stuff in shadowed's mod is pointless. I do agree that it is a blizzard interface bug. combat log is part of blizzard interface and if it's failing to a blizzard bug then it fits the purpose of blizzbugssuck. Personally i wish blizz would fix it though but considering they've let it exist since 2.x they are in no hurry.

    Last edited Jul 10, 2010 by mysticalos

Facts

Date created
Jun 25, 2010
Category
Last update
Dec 15, 2013
Development stage
Release
License
All Rights Reserved
Curse link
BlizzBugsSuck
Downloads
44,301
Recent files

Authors

Relationships

Embedded library
LibChatAnims
LibStub