BlizzBugsSuck : Miscellaneous : World of Warcraft AddOns

(6 Kb)

Download

Updated: 03-31-13 03:24 PM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Thunder Isle (5.2)
Updated:	03-31-13 03:24 PM
Created:	06-28-10 03:31 AM
Downloads:	4,477
Favorites:	107
MD5:

BlizzBugsSuck

Version: 5.2.0.2

by: Shefki [More]

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 PlayerTalentFame is nil error with the GlyphUI.
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 in 4.0.1)
REMOVED: A fix to 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 with 4.0.1)
REMOVED Fix for minimap ping not updating as you move making the ping appear to move locations as you move. (Fixed by 4.0.1)
REMOVED: Block the exploit that allows AddOns from getting your Real Name from the Real ID system. (Fixed by hot fix 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)

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.

5.2.0.2
- Add fix contributed by Phanx to avoid the DEATH popup when reloading.

5.0.4.1
- Fix the PlayerTalentFrame nil error in the GlyphUI for 5.0.4.
- Remove some obsolete fixes.

4.3.4.1
- Fix a bug in the whisper menu and chat links for cross-realm players in LFR and BGs.

4.0.3.2
- Fix an error in the sort code for the map fix.

4.0.3.1
- Fix for the poiButton error when opening the Map.
- Avoid infinite loops with the InterfaceOptions_OpenToCategory fix.

4.0.1.1
- Disable the bugs that were fixed in 4.0.1.

3.3.5.9:
- Add fix for minimap ping not updating as you move making the ping appear to move locations as you move.
- Minor code changes.

3.3.5.8:
- Remove an unnecessary anonymous function.
- Fix InterfaceOptions_OpenToCategory to not complain when people use a table as the parent.

3.3.5.7:
- Fix a leaked global variable that was intended to be local.
- Remove workaround for BNSendWhisper leaking Real Names.

3.3.5.6:
- Forgot to change the warning strings when renaming thhe addon.

3.3.5.5:
- Rename addon to make Cairenn happy.

3.3.5.4:
- Make the warning when an addon tries to get your Real Name identify the addon that triggered it.

3.3.5.3:
- Add the block to stop addons from getting your Real Name.

3.3.5.2:
- Fix a typo that prevented the oneletter abbreviation fix for deDE from working for minutes.

3.3.5.1:
- Initial Release.

Archived Files (10)

File Name	Version	Size	Author	Date
BlizzBugsSuck	5.0.4.1	3kB	Shefki	09-05-12 09:05 PM
BlizzBugsSuck	4.0.3.2	3kB	Shefki	11-28-10 10:39 AM
BlizzBugsSuck	4.0.3.1	3kB	Shefki	11-28-10 03:23 AM
BlizzBugsSuck	4.0.1.1	2kB	Shefki	10-11-10 07:33 PM
BlizzBugsSuck	3.3.5.9	2kB	Shefki	07-17-10 12:50 AM
BlizzBugsSuck	3.3.5.7	2kB	Shefki	07-10-10 02:31 PM
BlizzBugsSuck	3.3.5.6	2kB	Shefki	07-07-10 04:59 AM
BlizzBugsSuck	3.3.5.5	2kB	Shefki	07-07-10 04:47 AM
BlizzSucks	3.3.5.3	2kB	Shefki	07-07-10 02:50 AM
BlizzSucks	3.3.5.3	2kB	Shefki	06-28-10 03:31 AM

Comment Options

Page 1 of 3

06-28-10, 04:56 AM
Noxarious Premium Deadmeat Forum posts: 4 File comments: 60 Uploads: 1	Great idea, awesome addon

06-28-10, 08:20 AM
Dragoen A Kobold Labourer Forum posts: 1 File comments: 5 Uploads: 0	what about "memory" errors? my game crashes a lot since last tuesday's update. Most of the time the error references MapMem.cpp trying to request a huge block of memory. I do run a lot of addons so I know blizz will blame them, but the game ran fine with the same addons up until blizz released the update last tuesday. I've seen this situation on many of the previous updates too over the years and after a month or so of blizz bug fixes and new releases of addons the problem mysteriously goes away, but I never know what really fixed the problem. If it is indeed an addon that is no longer compatible with the new game code, what is the best way to identify which addon to stop using? I already use !DamnBlizzardErrorFrame and will stop using any addon's referenced in errors displayed by that. any ideas?

06-28-10, 12:02 PM
Shefki An Aku'mai Servant Forum posts: 31 File comments: 171 Uploads: 9	This addon is intended to fix bugs in the WoW UI, which is implemented in Lua on top of the game engine. The memory errors are caused by an issue where the game is using more memory than it can allocate. Most of that memory is used by the game itself and not addons. WoW is a 32-bit app and generally that means it is limited to using 2GB of RAM (even if the system has more than that). As the game grows more and more complex and more and more things have higher quality textures, WoW is running into this more and more. This isn't something that I can do anything about. It's entirely up to Blizzard to fix this one. There's a thread here on the official forums with some discussion and posts on this: http://forums.worldofwarcraft.com/th...52505632&sid=1 DamnBlizzardErrorFrame isn't something that we'd likely include in this addon since it's purpose is to enhance not fix any specific bugs.

06-30-10, 02:31 AM
Dragoen A Kobold Labourer Forum posts: 1 File comments: 5 Uploads: 0	thanks for your feedback - i really didnt expect this addon to fix my problems, just wanted some info which you provided nicely. Amazingly after today's bug fix update from blizz all my addon problems went away ... hmmm thanks again

07-07-10, 09:55 AM
Beliablue A Kobold Labourer Forum posts: 1 File comments: 28 Uploads: 1	Many Thanks! Many thanks Shefki for the work of integrating the RealID name fix into this; it is so much handier to only need one addon to fix all Blizz's bugs instead of three or four. One quick question on the RealID name fix, will this "play nice" with chat addons, or is it going to interfere with RealID whispers and conversations there? I don't necessarily have a problem with it if it does, I just wanted to expect it if if was going to happen. I'd much rather have the extra level of blocking and a little bit of hassle with a chat mod than not.

07-07-10, 11:37 AM

Shefki

An Aku'mai Servant

Forum posts: 31

File comments: 171

Uploads: 9

Re: Many Thanks!

Originally posted by Beliablue
Many thanks Shefki for the work of integrating the RealID name fix into this; it is so much handier to only need one addon to fix all Blizz's bugs instead of three or four.

One quick question on the RealID name fix, will this "play nice" with chat addons, or is it going to interfere with RealID whispers and conversations there? I don't necessarily have a problem with it if it does, I just wanted to expect it if if was going to happen. I'd much rather have the extra level of blocking and a little bit of hassle with a chat mod than not.

It will not interfere with any addon that's doing anything reasonable. The only thing it blocks is the ability to send a Battle Net whisper to yourself. There's no way to do this from the normal UI of the game, it has to be done with a Lua script. If it happens you will get a message in red text in your chat box telling you that it was blocked and what addon did it (if we can detect that).

07-08-10, 01:30 AM
Angrysteel A Murloc Raider Forum posts: 6 File comments: 204 Uploads: 0	Did this addon used to be named Blizz Sucks? Or something similar?

07-08-10, 01:32 AM

Shefki

An Aku'mai Servant

Forum posts: 31

File comments: 171

Uploads: 9

Originally posted by Angrysteel
Did this addon used to be named Blizz Sucks? Or something similar?

Yes.

07-08-10, 04:53 PM
Dominia A Kobold Labourer Forum posts: 0 File comments: 5 Uploads: 0	In the comments here you say: "The only thing it blocks is the ability to send a Battle Net whisper to yourself." In the Addon Info you say: "Block the exploit that allows AddOns from getting your Real Name from the Real ID system." Basically, I want to know if any Addon I install will be able to grab the RealID from my account and display it for OTHER people to view? That's not the same thing as blocking me from whispering myself. Sorry for my confusion. My head is spinning from all this RealID crap.

07-08-10, 05:07 PM
Dkatt A Kobold Labourer Forum posts: 1 File comments: 3 Uploads: 0	Is there a way for you to include a fix to prevent RealID friends of friends from being broadcast at all?

07-08-10, 05:09 PM
Shefki An Aku'mai Servant Forum posts: 31 File comments: 171 Uploads: 9	Dominia, The method of getting your RealName from the game is to whisper yourself. Outside of an event that very rarely fires, there is no other way to my knowledge to get your own real name. If an addon can get the name it could send it to other players via the addon communication system. AddOns can hide whispers that you are sending or receiving, so it'd be trivial for an addon to make it whisper yourself, get your name from that, and then whisper it to someone else. That's the concern.

07-08-10, 05:22 PM

Shefki

An Aku'mai Servant

Forum posts: 31

File comments: 171

Uploads: 9

Originally posted by Dkatt
Is there a way for you to include a fix to prevent RealID friends of friends from being broadcast at all?

No, those are directly accessible via an API. Blizzard intended addons to have access to that. If you don't like that, my only suggestion is to not use RealID.

Any attempt to try and hide that information would have to equally break Blizzard's own UI from getting it in order to be effective. Which is outside the scope of what I intend to do with BlizzBugsSucks.

I've add the criteria for inclusion to the addon description now as well.

Last edited by Shefki : 07-08-10 at 05:32 PM.

07-08-10, 06:02 PM
PingHansen Guest Join Date: Not Yet Forum posts: 0 File comments: 0 Uploads: 0	Regarding the nil error I reported on the 5th: It happened again today, same error, same line numbers. The auras persisted for quite a while after the target was dead, but eventually disappeared. I have noticed that unused combo points usually persists on the target after it is dead - or at least the auras do. If you select the target again for looting, the auras pop up again. This behavior is the same on rogues and druids. My thinking is that this could be the root cause of the error. Perhaps a check for whether the target is alive?? Just guessing.

07-08-10, 06:59 PM

Shefki

An Aku'mai Servant

Forum posts: 31

File comments: 171

Uploads: 9

Originally posted by PingHansen
Regarding the nil error I reported on the 5th: It happened again today, same error, same line numbers. The auras persisted for quite a while after the target was dead, but eventually disappeared.

I have noticed that unused combo points usually persists on the target after it is dead - or at least the auras do. If you select the target again for looting, the auras pop up again. This behavior is the same on rogues and druids. My thinking is that this could be the root cause of the error. Perhaps a check for whether the target is alive?? Just guessing.

Umm what nil error you reported on the 5th? I'm guessing you posted this on the wrong addon.

Edit: Looking at your posting history, I think you meant to post this on PowerAuras-Classic

Last edited by Shefki : 07-08-10 at 09:15 PM.

07-11-10, 12:14 PM
ricks322 A Chromatic Dragonspawn Forum posts: 154 File comments: 159 Uploads: 1	RealID name fix?? You said the RealID problem had been fixed by a Hotfix, where did you find this out? I have looked (although maybe not deep enough), but I can not find any mention of a Hotfix to solve the problem...

Page 1 of 3

Report this File

Category Jump: