Psa - uncollected only option in ah dont care about armor type

Community General Discussion
1

so example, bloodfist vambraces and patterned bronze bracers, same model but different aromr type, u can’t cross-mog armor type without learning it

so if u learn the plate one, u cant mog it on mail character, u have to learn the mail one too, ok makes sense, always been that way

but in the AH, if u learned the plate only then searched uncollected only filter on mail, the mail one wont show up

i saw this on other armor types that share same appearance across types

the uncollected filter only cares if appearance learned on one armor type only, it doesnt care if ur other toons armor type cant mog it

why blizzard, ugh, makes mog hunting in ah abysmal

2

…click useable only.

3

huh

u dont understand

if u learn same appearance on one armor type, it gets hidden from uncollected on other armor type with same appearance

4

I haven’t had this issue. I’ve bought different appearances across armor types with the default AH.

I also use the addon Collectionator, which scans the AH for you and makes it easier.

5

but the issue is same appearance across armor, not different, thats why i example gear in op

6

Yes, I know what you mean. I haven’t had that issue. I browse the AH periodically for appearances and have never had that situation happen.

7

yeah you wouldnt know unless u browsed mogs without uncollected on and all the things said ‘not collected’, then u look at source and see u learned that appearance on different armor type, but checking ‘uncollected’ will then hide it on unlearned type

so the example gear i gave - does ur plate toon know bloodfist vambraces and mail know patterned bronze bracer? if not u can try urself

the collectionator addon does same thing if unique appearance is checked

expedition boots=leather, talhide-lined boots=mail, durable bracers=cloth, all 3 share same appearance

i already know talhide and durable, not expedition. if i turn on unique, expedition goes away, if i turn off unique, it then shows, and all the thigns verifies its not already learned, so i cant filter out by unique model with it

so the problem shows in that addon too, its something wrong with blizz’s end probably