PSA when using your tier token

The heroic PvE tier items and the elite scaleable PvP items are purchased with the exact same currency, have the exact same icon, and exact same name. I made the idiot mistake of buying and equipping the heroic pve gloves on accident, 431 ilvl in pvp btw so it’s worse than even honor gear and now the extremely valuable tier token is completely worthless.

Pretty absurd that there is virtually no difference between the items from a UX or currency perspective that would prevent this easy mistake. In any case, it was a stupid on my part. Don’t be me.

5 Likes

I’m sorry that happened and yes it’s stupid they made it so easy to pick the wrong thing. You probably already have but if you haven’t, I would submit a ticket. I bet they would replace that for you.

Should’ve had two vendors so fewer people bought the wrong piece.

3 Likes

Yeah, I submitted a ticket. It’s such an easy mistake to made given the entire context of the purchasing experience that I wouldn’t be surprised if they were inundated with ticket requests for this right now.

1 Like

Oh no its the case of buying the ring instead of the weapon again. they are gonna remove vendors!

4 Likes

Ion was right about vendors

6 Likes

Please let us know what happens.

I thought Blizzard added the 2-hour window to return items so they wouldn’t have to deal with item tickets anymore.

It’ll be good to know if the GMs still handle them.

I’ve already heard multiple stories of gms just straight up saying “no, too bad” to things related to this tier vendor, so I’d be surprised if this is any different.

The window shouldn’t go away if you equip it, that’s the part of the system that is stupid. But I guess people would just keep buying, wearing for 1.9 hrs, then refunding for some advantage.

2 Likes

Generally if there’s any sort of “Are you sure” popup on purchase and use then they don’t help, yeah.

Yeah. Imagine if the optimal thing was just doing this until your next vault(s) so you can rotate out the tier piece you don’t have, lmao.

Used to rent gear like this back in BC.

But honestly, read things.

1 Like

Yeah, I had to do this in wod to finish my elite set because the conquest rollover was only partial and the elite pieces themselves were expensive and cost conquest so if you started queuing too late you’d be left with half a set.

:dracthyr_blob_dance_animated:

1 Like

Yah so Blizz denied my ticket to have the item refunded. I understand the black and white of the refund window, but I do feel there needs to be at least a little acknowledgment to the fact that the items are the same exact name, same exact item image, bought with the same currency, sold from the same vendor … it’s almost like they’re baiting people to make this mistake. Not the type of user experience or game design you’d expect to see in a nearly 20 year old MMO

1 Like

Are you sure? A guildy of mine reported buying a pvp by mistake and was able to refund it to the vendor.

Should just remove vendors all together so people stop buying wrong pieces and just make every An rng drop

1 Like

I immediately equipped the gloves in front of the vendor and only realized after I equipped them is the problem, which invalidates the refund window

Tragic :frowning:
Good news is you can upgrade them to 441 with flightstones, which isnt that bad!

2 Likes

Actually this is exactly what i would expect. They did this to minimalize the amount of work to optimize the amount of profit they would get from said work by only needing 1 person to create the asset, and maybe, 2 additional person to implement it into the vendor.

Simple reading would fix the problem

They won’t help you lol. They’ll tell you “it prompts you before you buy it and you said ok so sucks to suck”. Watch lol itll take 3 or so days to get that response exactly.

But there is a line between efficiency and practicality, especially when it comes to a product people are consuming. Creating a separate vendor, or even simply a different currency, to avoid players making easy mistakes down the road seems like a very practical thing to do. I’d argue the labor required to perform this simple development task is smaller than the labor required to spend an entire patch having CS reps responding to people making this mistake, so it’s actually a better business decision. Especially in the grand scheme of a major content patch, such a simple task is surely a tiny fraction of development time.

Simple reading would fix the problem

Yeah, no one ever denied that. It’s about the flawed design enabling such an easy mistake when there are easy alternatives available