Reconciliation Plan!?

"RandomSithLord;c-1987648" wrote:

"LastBucsfan;c-1987643" wrote:

"RandomSithLord;c-1987637" wrote:

"LastBucsfan;c-1987632" wrote:
My original plan was to farm gear for Malak over the next several months it would take to obtain enough GET. So when I get him earlier than expected I plunk down money to gear him right away and now thats getting rolled back? CG better roll my god **** money back. I don't need the gear to sit in my inbox during a time a could have farmed it all.

But why were you in a rush to gear Malak? Could you not wait another half of a day for the announcement whether shards being given out is intended or not? Did you need to buy all that gear to be more competitive in arena a few hours earlier?

Because, you know, TW and GAC lock already happened, there was no immediate benefit, just a rushed choice on your part.

Am I supposed to play the game under the assumption that rewards are glitched or working as intended? There were TWs and GAs coming up.

You are not supposed to live under that assumption, but both the experience from the previous 'replay' snd the wording of the event ('first time' rewards) were clear signs that this is not a previously announced nice surprise. It was clear there will be an update regarding the intention.

TW didn't lock until another ~36 hours, GAC won't lock again for over 4 days (6 at the time of the bug). Are you saying that if you could pay to rush Malak to 13 in a few hours/minutes, you couldn't have done that half a day later, when you know clearly whether you are supposed to have the shards or not?

I got Malak on the 2nd event. I had never seen the rewards for playing through with him already at 5*. A reddit post saying that we receive shards for doing the event again was at the top of my phone banner that morning. You assume I stay more up to speed with events than I do. I thought the game was working as intended. Perhaps it was an attempt to help the guild currency with GAS being in GET now. I have never seen an online game blow such blatantly obvious QA errors before.