Party order in random dungeon finder (might not be nUI bug)?
 

I'm running into the following issue. In patch 3.3.3 Blizzard made this change:

"Parties randomly created via the Dungeon Finder will always be arranged in the party interface from top to bottom in the following order: tank, healer, damage, damage, damage."

However, when I join a random dungeon group, sometimes the tank shows up in the top left frame, other times in the top right, and I could swear (although I'm not 100% sure) that I've seen the tank show up in one of the bottom frames of the 5-man frames.

Is this an nUI issue, or is the Dungeon Finder just not working the way Blizzard reported in the bug fix? Anyone else seeing the same issue? A google search didn't find anything except for a single altered version of the 3.3.3 patch notes specifying that addons or custom UIs could change the order.

Presuming you're talking about the party unit frames and not raid unit frames, then nUi organizes the frames from party1 to party4 and does not "sort" them. I don't know if Blizzard solves the problem by sorting the units into the frames or assigning the tank to party1, healer to party2, etc. So... if Blizz is sorting the unit frames, then the issue is that nUI does not do that. If Blizz is assigning the tank to party1, healer to party2, etc. then it's a Blizz thing.

That said, nUI does display icons to tell you which unit is which, so you will see the shield icon on the tank, cross on the healer and so on.

I think the way it's supposed to be is that tank is party1, healer is party2 and so on. As far as I can tell, this is broken in current WoW. Now that I mention it, I think I saw the same problem before I started using nUI. Sigh - if this worked the way Blizzard says it does I could get rid of LiteAssist. My other option is to set focus on the tank, but that clobbers my minimap. I'll just have to wait for nUI 6 I suppose :)

Interesting little mod that is.... I'll keep it in mind for nUI6

Blizzard does actually assign party unit IDs in order, by "tank, healer, dps, dps" ... but it still makes the party leader party1 regardless of roles. As long as the tank checked the "Leader" box in the LFD tool, he'll be the leader, but if he didn't, then someone else will be the leader and the tank will be party2.

Darn. That makes the feature pretty useless for what I wanted - macros using

[target=party1]

instead of

[target=focus]

for assisting and misdirecting onto the tank. Maybe I'll look at the LiteAssist code and add my own options so it will work the way I want.