I was wondering if anyone from the beta had any confirmation on which "oddities" from the current live build (being behind the times) are actually here to stay, and which will thankfully be fixed come 2.0.3 TBC or whatever. Here's what I've noticed:


1) When you disconnect or log off in a 5man instance currently, you immediately leave group, and for some reason also leave your instance tag. This causes you to log back in solo, in your own copy of the instance. This causes serious issues for groups without warlocks, and a fun bonus of Live Strat being you can't zone back out, so you get to die just so you can get back to your group's instance. Please tell me this is bugged in this old incarnation of the build?

2) In-combat lockdown of certain functions, disallowing you to perform certain actions. Things of note are not being able to open your spellbook while in combat, and not being able to open the raid tab (sometimes), and never being able to alter raid-group composition while in combat. This is especially crippling for Horde right now, due to the nature of Shamans and their totems. Is this here to stay?

3) The Hit/Miss system in pvp (and possibly elsewhere) seems changed for physical. Pre 2.0, only magic users were the ones who had the disadvantage of a hard-coded 1% minimum miss rate with their spells. Since 2.0, I've noticed a lot more missing on several of my physical dps classes in PvP. I do realize there are new talents that give you avoidance to damage under certain circumstances, but I'm 99% certain that I have experienced several misses on classes who dont have available talents to account for this (while carrying enough +hit to nullify misses previous to 2.0). Has the system been changed, and if so, is it bugged or here to stay?


Please post any information you have on these particular issues, and if you have any other experiences, please post those as well. I'm curious what is temporary and what is not. I really dont want to have to do TBC raids without the ability to change raid-group composition mid-combat, for example.

Not sure about the others but #2 is caused by one of your addons (for me it was CT_Raid), not the patch. Get rid of the out of date mods and this should fix itself.

#1 is currently fixed on Beta. I assume that BC will update it.

#2 is a mod problem on your end, except the last bit. You are unable to change groups once combat is initiated on beta, I assume that it is an intended function. I can't quote any blue on that, though.

#3 I have no idea. I have not been noticing it, but I have been primarily playing my druid in a healing fashion since the patch change.

To summarize, same thing the guy above me said.

I've actually moved people around in groups on live; though that's obviously a somewhat outdated build. Moves them around fine in Grid display wise and targeting wise as well.

If I remember what the dev said about beta/tbc live regarding groups, is the raid tab itself, coding wise is getting overhauled. One of the side effects is you will not be able to use the raid tab in the social panel, while in combat.

Wait, you can't drag new spells to your bar in combat, or you can't open your spellbook at all?

Hmm, strange, I wonder which addons are doing this then (the raid group thing), as it has happened both before and after installing CTRaid, and on top of it im mostly certain that a guildie also had the same issue, with zero addons installed on day 1 of 2.0's patch.

Also, you guys have given conflicted information. One of you says its intended and still happens in beta, others say you can alter group composition just fine.

In live you can alter it just fine. In tbc/beta the intention is for the raid panel to not work during a fight, from what I remember a dev saying. I can use my spellbook, move people in the raid to diff groups, on retail right now.

It seems that mid fight group changes, for us at least, only happen when a key shaman or imp dropping warlock dies. Within a few months of TBC hord side should be getting raid level paladins so that would mean that only dumb warlocks dieing early in boss fights would really cause raid leaders to curse this change. Still, I cant think of a reason why the devs would want to get rid of this ability. Was their a way to exploit something (party buffs..?) in an unfair way?

Whats wierd is I dont think they said they wanted to disable moving members during combat, but they wanted to redo the raid panel with secure frames, which had a side effect of making it impossible to move members in combat.

On TBC beta moving people around to different groups is certainly possible while in combat using only the built in UI. If they really wanted to lock that functionality down I think we would see it implemented already and the key functions for changing group members changed to protected.

On the subject of specific mods causing issues I know that ag unit frames as of Dec 6 was causing issues with the built in raid UI but as that version is quite old this may no longer be the case. My best guess as to the cause of these problems is that some old code is spreading taint to functions that must now remain secure for the raid panel to function properly. Once all the bugs are sorted out with mods there should be no such problems.

Being unable to change raid configuration in combat using social tab and your mouse is a bug.

Being unable to change raid configuration in combat using the function is NOT a bug. There was a post about this on UI forums.

Perhaps someone was making mods that would float certain raid members throughout X number of parties. For instance, If party A has a certain number of members below a thresh hold hp, then the highest life member would be switched out with the shadow priest/imp LotP druid to heal them up. That would be unbalanced.

Is that what they are trying to prevent?

Things like that or having one person spam-click dispel magic on one raid frame, and some script just cycles members into that spot (aka: decursive)

What about the warrior's Weapon Mastery talent? On live it only prevents players from disarming you, not mobs. Is this bugged or intended?

I can't find the Blizzard post on this but this is a confirmed bug, I think they said it would be fixed next patch (expansion release).

This is a bug, blizzard has fixed it but it will take a while for the fix to hit the live servers.
http://forums.worldofwarcraft.com/th...geNo=1&sid=1#7