Kousagi, on 13 November 2012 - 08:14 AM, said:
Thats the thing, they DO think about how their changes effect people. You just think they don't cause you think you got hit with a negative side of things, when really you got the positive side of it. Theres more to the sides then just you. They thought that pure 2.0 double would cause a grave imbalance in mech builds, so they acted accordingly. Much the same way they did with the LRM buff, it was hotfixed in 2 days with a nerf, cause it was ruining the game. So they do care, you just think they don't.
I've never had to deal with their custorm service, but I think they are pretty smart to turn you away on that refund. As others have said, if they gave you that, it would open the flood gates. Thats something they just can't do. So what is there to improve?
I am sure they do think of customers and how things effect people. As for improvements they could not charge us for features considered to be in testing. I really don't get why you people have a problem with asking them to give us a break. It is beta for them and us and balance issues should not always fall on the shoulders of the customer. They have a great customer service team, they are responsive and nice.
If you add a new feature, you could intially make it free for it's testing phase, then reverse the feature such as upgrades and begin charing CB or MC for it after it is proven stable and balanced.
Very simple example of how it could be done putting customer satisfaction first:
Patch Notes
1. New DHS patch comming.
2. Initial deployment will be free for a test period.
3. Once DHS are stable and balanced we will reverse all DHS's upgrades and begin charging CB and MC for the upgrade.
Very simple example 2 of how it could be done putting customer satisfaction first:
Patch Notes:
1. New LRM patch comming.
2. Initialy LRM's will be free for a test period.
3. Once LRM are stable and balanced we will reverse all LRM purchases mods and begin charging CB and MC for the LRM's.
This prevents customers from buying one thing only to wake up the next day to find a patch changed the item or service they purchased. Pretty simple really.
The point is to make the least negative impact on customer game experience while in a test phase of development. That is all I am suggesting they do.
They not demanindg they do it the way I propose but they have room for improvement in my opinion. Thats all.
I don't feel I am entitltled to have them do it my way or they have to make me happy or that they are commiting fraud or what ever. I just proposing to them they could improve their methods to ease the impact on the customer base.