You don’t promise something “significant” and then fail to deliver something “significant”. Just saying
"Significant" is very much a matter of opinion.
I'm not a liar if I say I'll make you a yummy pie, then you don't like the pie.
We aren’t talking about individual taste though. We are looking at that word in a specific perspective. Significant in this case was said to imply One of these definitions mentioned earlier:
Having nothing to say is not the same as ignoring the situation.
There's really nothing they can say to these torches and pitchforks except for, "Noted."
Nonsense.
We've had hotfixes applied in no amount of time when things have accidentally been to the players advantage.
We've had far higher amounts of crystals granted as apologies for brief outages that affected few players. Thats good. It keeps your customers happy.
This was supposed to be a makegood for a series of mistakes, bugs and errors. Some are happy with what they got, but many were expecting far better, particularly with use of the word significant.
When you very quickly get feedback from your customers that your apology (and that is what this was supposed to be, an apology for the bugs and broken territory battles) falls far short of expectations you back peddle and improve your offer ASAP.
They misjudged. That's ok. We gave this feedback. Then they should have fixed it. We're talking about virtual rewards here. The mechanisms are there to push rewards to all players. Give something significant.
It absolutely could have been done. Ignoring it doesn't make the problem go away. It makes your customers go away.
A "noted" or "We're listening" isn't good enough... but the thing is, we haven't even had that!
An "oops, sorry, here's some more crystals/currency" would have stopped this in it's tracks. They've totally dropped the ball on this one. Why on earth they would want this continuing to fester away is beyond me...
"Backpedal and improve your offer," is not a wise course of action, because it gets the player base accustomed to a structure of, "Kvetch loud enough, and they will cave and give us more stuff."
Revising the offer after it's been announced is one of the worst PR moves they could make long term.
"Backpedal and improve your offer," is not a wise course of action, because it gets the player base accustomed to a structure of, "Kvetch loud enough, and they will cave and give us more stuff."
Revising the offer after it's been announced is one of the worst PR moves they could make long term.
So is continually going back on their word.
See here’s the the thing. It’s not as if they gave say....2500 crystals, 5000 GET currency and a full carbantis to everyone. Had they done something like that, and people complained that it wasn’t “significant” enough then you’d be 100% correct. Giving more in the face of complaints and uproar would be foolish.
However, in this case the makegood was grossly underwhelming. Adding more now is not setting a bad precedent. It’s showing responsibility by fixing a mistake. Whether it be this makegood for all the recent TB issues, the raid reward structure for HST, ships gameplay, or whatever; admitting a mistake and then fixing it to what’s expected is not bad business. In fact it’s quite the opposite. They’d be showing their customers and player base that they can uphold their promises (better communication and game play). That they can take responsibility for mistakes and missteps (see above). That they are in touch with their playerbase, listening to feed back and putting pride aside and making this the best game out there.
Nobody expects daily updates or massive communication like we saw in April after CaPsGate. They even explicitly told it it wouldn’t continue as such. Nobody expected it anyway. But a middle ground of addressing serious issues? That’s not unreasonable. In fact, that should be their priority.
"Backpedal and improve your offer," is not a wise course of action, because it gets the player base accustomed to a structure of, "Kvetch loud enough, and they will cave and give us more stuff."
Revising the offer after it's been announced is one of the worst PR moves they could make long term.
Kudos, you've made me laugh.
Describing an effective and positive response option to a bad situation that they made worse as being a worst PR move... in the context of a game publisher with a stellar track record in PR decisions...
Too right people are going to keep complaining. And don't doubt that this will keep going until radio silence is lifted and an apology and/or actaully significant makegood occurs.
That's not caving in. That's recognising that the only positive PR solution to keep your customers happy is to apologise and do what you said you would; provide a significant makegood. It doesn't matter if some people are content with what they got. Enough aren't and that makes this enough of a problem that it wont just disappear of its own accord.
Personally 20 shards is more significant than the 2 my guild normally gets.
While I'm not upset at the makegood, it's fair to point out that the more your guild missed out on to begin with, the more upset you probably are.
I don't blame them for being upset, we really should've been given the same shards as we got last time. Unfortunately, complaining about things doesn't seem to work as well as it once did.
Just bumping this back up so @CG_SBCrumb and @CG_Carrie don't think we forgot about it.... its 11AM PST, how bout some kind of response to this ridiculousness?
Seriously how bugged is TB atm.
Multiple fights this time bugged out after a couple waves and meant i couldn't continue.
Costing the guild points and as a result TB stars...super frustrating and i'm not the only one this has affected in our guild. Don't even wanna know how many people in other guilds are having the same problem
Seriously how bugged is TB atm.
Multiple fights this time bugged out after a couple waves and meant i couldn't continue.
Costing the guild points and as a result TB stars...super frustrating and i'm not the only one this has affected in our guild. Don't even wanna know how many people in other guilds are having the same problem
What do these squads have in common? Characters with counter-attack abilities. I could be wrong, I suppose it's possible that CHOLO is somehow causing this due to some special code that was added for his kit which is somehow always active even if he isn't present in the encounter, but this really doesn't seem plausible to my defective brain.
I have yet to see this happen to a squad that has 0 counter-attackers. Doesn't that seem odd? Sure, my sample size is limited. But there is certainly ample evidence to suggest this is an area that should be studied.
Why did I not receive any notifications about this?? I've kept telling you guys I never received any message now any rewards.
Are you now not honoring posted tickets about this problem you did not know about until I opened 3 different tickets?
What a rip-off and not the first time you've screwed me over
Replies
Actually you kinda are because you set the expectations and did not deliver. But hey CG probably would promjse us a yummy pie and bring us Kale.
While I'm not upset at the makegood, it's fair to point out that the more your guild missed out on to begin with, the more upset you probably are.
More like you said you make me a yummy pie, but gave me a stale muffin.
Free? It wasn’t even as much as some people missed due to the bugs.
We aren’t talking about individual taste though. We are looking at that word in a specific perspective. Significant in this case was said to imply One of these definitions mentioned earlier:
So using common knowledge in this frame of discussion you can’t really leave it open to interpretation.
Agree, not a liar. That implies a wilful intent to mislead.
But... you'd be incompetent if you promised a "yummy" pie and it turned out to be poor.
And... you'd be rude to then ignore a paying customer when they tell you the "yummy" pie fell far short of expectations of what they consider "yummy".
There's really nothing they can say to these torches and pitchforks except for, "Noted."
Nonsense.
We've had hotfixes applied in no amount of time when things have accidentally been to the players advantage.
We've had far higher amounts of crystals granted as apologies for brief outages that affected few players. Thats good. It keeps your customers happy.
This was supposed to be a makegood for a series of mistakes, bugs and errors. Some are happy with what they got, but many were expecting far better, particularly with use of the word significant.
When you very quickly get feedback from your customers that your apology (and that is what this was supposed to be, an apology for the bugs and broken territory battles) falls far short of expectations you back peddle and improve your offer ASAP.
They misjudged. That's ok. We gave this feedback. Then they should have fixed it. We're talking about virtual rewards here. The mechanisms are there to push rewards to all players. Give something significant.
It absolutely could have been done. Ignoring it doesn't make the problem go away. It makes your customers go away.
A "noted" or "We're listening" isn't good enough... but the thing is, we haven't even had that!
An "oops, sorry, here's some more crystals/currency" would have stopped this in it's tracks. They've totally dropped the ball on this one. Why on earth they would want this continuing to fester away is beyond me...
Revising the offer after it's been announced is one of the worst PR moves they could make long term.
So is continually going back on their word.
See here’s the the thing. It’s not as if they gave say....2500 crystals, 5000 GET currency and a full carbantis to everyone. Had they done something like that, and people complained that it wasn’t “significant” enough then you’d be 100% correct. Giving more in the face of complaints and uproar would be foolish.
However, in this case the makegood was grossly underwhelming. Adding more now is not setting a bad precedent. It’s showing responsibility by fixing a mistake. Whether it be this makegood for all the recent TB issues, the raid reward structure for HST, ships gameplay, or whatever; admitting a mistake and then fixing it to what’s expected is not bad business. In fact it’s quite the opposite. They’d be showing their customers and player base that they can uphold their promises (better communication and game play). That they can take responsibility for mistakes and missteps (see above). That they are in touch with their playerbase, listening to feed back and putting pride aside and making this the best game out there.
Kudos, you've made me laugh.
Describing an effective and positive response option to a bad situation that they made worse as being a worst PR move... in the context of a game publisher with a stellar track record in PR decisions...
Too right people are going to keep complaining. And don't doubt that this will keep going until radio silence is lifted and an apology and/or actaully significant makegood occurs.
That's not caving in. That's recognising that the only positive PR solution to keep your customers happy is to apologise and do what you said you would; provide a significant makegood. It doesn't matter if some people are content with what they got. Enough aren't and that makes this enough of a problem that it wont just disappear of its own accord.
I don't blame them for being upset, we really should've been given the same shards as we got last time. Unfortunately, complaining about things doesn't seem to work as well as it once did.
Yep, sure is. I thought this had been fixed by taking CHolo out of TB. Looks like JTR needs to go as well.
@CG_Carrie. Maybe the real makegood will come when they finally fix this code..... so never.
Multiple fights this time bugged out after a couple waves and meant i couldn't continue.
Costing the guild points and as a result TB stars...super frustrating and i'm not the only one this has affected in our guild. Don't even wanna know how many people in other guilds are having the same problem
What do these squads have in common? Characters with counter-attack abilities. I could be wrong, I suppose it's possible that CHOLO is somehow causing this due to some special code that was added for his kit which is somehow always active even if he isn't present in the encounter, but this really doesn't seem plausible to my defective brain.
I have yet to see this happen to a squad that has 0 counter-attackers. Doesn't that seem odd? Sure, my sample size is limited. But there is certainly ample evidence to suggest this is an area that should be studied.
Are you now not honoring posted tickets about this problem you did not know about until I opened 3 different tickets?
What a rip-off and not the first time you've screwed me over