So here's a list of my known 2.0.3 issues. These are problems that I experienced myself and my guild members and raid members reported as well. Also a few issues others on the forums have reported to me.

1.) Target Unit Frame goes missing occasionally.
2.) Target of Target Unit Frame not always displaying.
3.) Raid leader commands affecting wrong raid member.
4.) Players selecting wrong raid members from Blizzard's raid UI.
5.) After login, Character Selection Screen is delayed in displaying.
6.) Battlegrounds Scoresheet alignment is off.

During our two raids last night, Onyxia and Zul'Gurub, there were many people reporting issues of their target unit frame not displaying. You would be targeting the mob and attacking, but you couldn't see who your target was or it's health/mana. Naturally since your target frame was missing, you also could not see your target of target. A few people have reported this issue being caused by CTRA, but I haven't been able to confirm yet.

Even when your target's unit frame was displaying, occasionally the target of target icon would not display. Though this problem was reported before 2.0.3 (I'm glad they didn't "fix" it though, who knows what they would brake in trying.)

I signed up for a PuG Onyxia raid when I logged in last night. Shortly later I was promoted to raid leader... by accident. When in a raid, if you select players from the raid list in the Social Menu window, and right+click their name you are given several options as a raid leader--promote to new leader, promote to assistant, remove from group, etc. They also added main tank and main assist options this patch (Here was your mistake Blizzard. Don't fix what isn't broken. CTRaidAssist is greater than any thing you can hope to do.) Anyways, when you chose to promote a new leader, remove someone from the raid, assign an assistant, or basically any raid leader command , the command does NOT affect the player you intended. Instead someone else in the raid gets leader or kicked or what have you. Needless to say, this is a very annoying issue.

Healers have also reported targeting the wrong raid member when selecting targets from the pull-out raid party frames. Wow, that has to suck for big raids. "Heal the MT!" "Who do I select to target him?!?" I haven't confirmed if this problem is affecting CTRA raid bars or not.

After entering my account name and password on the login screen, there is a small delay as the character selection screen fades in. It was about 3-4 seconds for me, but others report as much as a 10 second delay. Not a huge issue, just not a needed one.

Deedlít of Crushridge Realm reported the Battlegrounds Scoresheet has an incorrect alignment.

Arkadi of Hyjal Realm reported issues with the Quest Log UI. It's now collapsed by default. This is also affecting mods that use the quest UI. I have not looked at my quest log since patch though. In light of other reports, this issues seems only to be affecting those with quest related addons.

Blizzard, I'd have to say you get a 3 out of 10 for execution of this patch. I'll give you a tip to avoid issues in the future. Don't try to fix what isn't broken. CT_RaidAssist has always been our favorite raid mod and all your attempts to match it have been failures. (Though I do give you mad props for the Lucky Charms icons.)

Considering this is the last patch before Burning Crusade, I am very worried about your ability to implement the expansion on launch day. What should we expect? A week or two of server crashes from the flood of players into a few zones? A month or so of buggy and faulty code that requires a few patches that brake other things?

Oh... here's your grade this semester.

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFF
FFFF
FFFF
FFFF
FFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF
FFFF

Thanks for putting that revenue to good use.

-Doc



Edit: Original post has been moved to the more appropriate UI forums.
Edit: Added Quest UI issue reported by Arkadi of Hyjal Realm.
Edit: Added BG Scoresheet issue reported by Deedlít of Crushridge.
Edit: Quest UI issues appears to be addon related.

Another obscure one I ran into yesterday.

I joined a group that was doing SM previously on Heroic, we then tried to enter Uldaman and it gave an error saying there was no heroic version of Uld, and the option to change it to normal was no where to be found.

The /target Name command was obviously malfunctioning last night.
Examples I recall for certain...In an Onyxia raid:
/tar Asana targetted Arrtoo
/tar Arrtoo targetted Deetoo (yes they're geeks, and that particular bug is very odd)

Many others tried /tar name commands, and most (possibly all) targetted the wrong person - consistently across attempts and players. (ie Asana repeatedly targetted Deetoo by typing /tar Arrtoo as well)


CTRA raid frames seemed properly aligned, but all I was doing way buffing, so combat might have caused trouble. Blizzard raid frames have always had a bad time about updating to raid changes after they're pulled out.

/target command issues confirmed and addressed in another thread. Thanks Slouken and Rislyn.

But! On the positive side, the modifier key binding issue affecting built in Self Cast has been fixed as promised!

/cookie Slouken

<3

---

Q u o t e:
/target command issues confirmed and addressed in another thread. Thanks Slouken and Rislyn.

---

And that thread is ... ?

I'll go looking for it but a link would of been way cool.

... still would be =)

---

Q u o t e:


You are an ungrateful little puke, you know that? You oughtta be thanking blizzard's employees for dedicating the time necessary to keep 8 million people happy every freaking week, not boo hooing your whiny emo ass off every time some new stuff comes with some bugs attached. FInd me another example of $15 a month for as many hours of entertainment and as much new content on a regular basis as WoW.

QUIT CRYING, QUIT BEING AN UNGRATEFUL PUKE, QUIT EXPECTING NEW FEATURES TO NOT USHER IN NEW BUGS

ie: GROW UP

---

I'm having a hard time deciding who's crying more, the original poster or you. Why do you care what people think? It's his right to criticize. I'm sure that you're so holy that you've never complain about anything, right? Go outside hypocrite and join the rest of the world.

---

Q u o t e:


You are an ungrateful little puke, you know that? You oughtta be thanking blizzard's employees for dedicating the time necessary to keep 8 million people happy every freaking week, not boo hooing your whiny emo ass off every time some new stuff comes with some bugs attached. FInd me another example of $15 a month for as many hours of entertainment and as much new content on a regular basis as WoW.

QUIT CRYING, QUIT BEING AN UNGRATEFUL PUKE, QUIT EXPECTING NEW FEATURES TO NOT USHER IN NEW BUGS

ie: GROW UP

---

I rather have them charge $20 a month and be actually able to play this game.. bugs like a complete unit frame missing, unable to promote and remove in a raid, is completely unacceptable, Blizzard employees dont even read the forums, they don't see read or care what we post, it's only the moderators at the forums who reads these posts and they have nothing to do with the developers, at all. so it really doesn't matter what he posts, this is the place for us to vent and he is using it appropriately

Error: Target not showing or hidden.

Ok here is the breakdown, this is not a new problem people in beta have been complaining about this for a while, we have pinpointed the problem to errors happening between certain mods and the target frame.

Whenever you go into combat or switch targets these mods taint the target frame and it doesn't display properly. I have tracked this bug in beta for a while and posted to different forums about it especially in wowinterface.com. Some authors have worked on thier mods others have just ignored it.

If you want to see what I am talking about install bugtracker which basically captures all the errors.

Uninstall (switchoff) all your addons except one.

Ex: Ctraid + ctmod or itemrack or trinitybars.

Go fight a couple of mobs.

You will notice bugtracker going off, and the frame error occuring on occassion.

Now uninstall all the addons - except for bugtracker - you will notice bugtracker not finding errors and your target display doesn't get hidden.

In the wowinterface forums and many of the other forums which exist we have tried to point this out to mod authors such as "cide" and some have actually been working at it....however the authors of ctmod and ctraid stated in wowinterface that tainting the frames is normal. Now I am not sure what that means but honestly if I see an error I point it out and hope the authors fix it because I like their products.

Ctmod
Ctraid
itemrack
Trinitybars

Are just a few of the mods that I know that do this.
(Titan not so much - however trinity and item rack give errors.)

The author of trinitybars is awesome (Maul) he is always updating his addon so I am sure he will sooner or later remove the taint, also the itemrack authors are working on the problem. That leaves the most popular raiding mod out....hopefully they will fix the issue as well.

Hopefully this isn't an issue that is being caused by wow itself because it will be around for a while.

this patch blows

---

Q u o t e:


What am I? Chopped liver?

---

At least you are Kosher? ;)

---

Q u o t e:


What am I? Chopped liver?

---

kek.

If only we could get the blue responce that we get on the UI boards on other boards. :P


Anyway, I've got a quick question, but don't feel like starting a new thread and can't find one. What's the deal with the "cant selt owner to self" errors. It's not a big deal, the only thing that has seriously broken is Poisoner, but I'd like to not have Improved Error Frame barking at me every few minutes.

---

Q u o t e:


kek.

If only we could get the blue responce that we get on the UI boards on other boards. :P


Anyway, I've got a quick question, but don't feel like starting a new thread and can't find one. What's the deal with the "cant selt owner to self" errors. It's not a big deal, the only thing that has seriously broken is Poisoner, but I'd like to not have Improved Error Frame barking at me every few minutes.

---

Means the writer missed some old code when he updated the mod :P