Lost gold purchasing arena tickets. No tickets

“You want to buy this thing? okay pay us right now” -Blizzard
“You need us to pay you back for this thing that we messed up on?
Okay wait a very long time with little or no confirmation” -Also Blizzard

where’s the update??

1 Like

I lost 300 gold and haven’t tried to buy more arenas yet, waiting for some news before trying again and to see what will happen with what was lost

1 Like

Been over 8 days and still no refund.

My post of when my error occurred is linked below.

1 Like

@ BLIZZARD this is beyond a joke its been like 6 days , , , , , do you want to lose your player base? keep being as useless as you are and you will.

Chumps

1 Like

Absolute and pure cinema. grabs popcorn

Yeah this happened to me too about a week ago, the game froze while it was processing the transaction, so I closed it and when I logged back in the gold was gone and I had no tickets, I’m not trying to talk down on any devs or employees or anything, but I’m just curious as to if we are going to be able to get our gold and/or tickets back and if not, why?

It just really sucks because I can only usually get around 2 tickets a week which is just one underground run and so it’s a little upsetting to have the time I spent farming the gold wasted, and the very few arena runs I get to do taken away, I’m not sure how difficult it is for you guys to look up transactions with in game gold or to refund gold to people, or if there’s some sort of policy that doesn’t let you guys do that, but to be told “we’re aware of the bug and we’re working on it!” instead of “Hey sorry about that here’s your gold/tickets back” makes me feel worse about the whole thing to be honest, can you at least let us know that you’re working on giving/are going to give us the gold/tickets back?

Hey, so I just logged in and got 300 gold, thank you for listening and following through, Blizz

Yup, same here. Got it all back. Thanks!

Finally got it back, it was a long wait

Glad to hear the gold came through already – known issues thread has been updated here:

Thanks everyone who took the time to follow up and for your understanding while we got this sorted!

I ran into this issue last week.