No discussion on fixing Blu?????

[Kabooa]

It takes time to develop content.

It takes 5 seconds to say "We have heard your feedback."

[Brightamethyst]

It takes time to develop content.

It takes 5 seconds to say "We have heard your feedback."

While I agree that more communication with the community would be appreciated, that's often a no win scenario for the devs in cases like this.

People tend to assume that any official non-negative response is automatically a positive one. A dev saying "we heard your feedback" doesn't mean anything is going to change. It just leads to eventual "they said there were going to fix it but never did!" posts, even though no one ever actually said that.

[Kabooa]

While I agree that more communication with the community would be appreciated, that's often a no win scenario for the devs in cases like this.

People tend to assume that any official non-negative response is automatically a positive one. A dev saying "we heard your feedback" doesn't mean anything is going to change. It just leads to eventual "they said there were going to fix it but never did!" posts, even though no one ever actually said that.

No, given all recent feedback and changes we hear, the pattern is "bandaid fix" to "system change later". Generally speaking, having feedback acknowledged is favorable.

It's just Warrior set a bad precedent where feedback is given radical change in a quick response.

So in regards to blue mage, a "Bandaid Fix" is Synced Full Blue Mage parties give 100% learning rate for dungeons and trials, and allowing them to participate in up to level 50 duty finder. No one's going to complain that Satasha got a random Blue Mage in it to speed things along.

[Lambdafish]

It takes time to develop content.

It takes 5 seconds to say "We have heard your feedback."

Does it? The devs won't say anything until they have figured out a strategy for implementing the feedback. Its really bad business to publicly take a stance on feedback without a plan to address it.

[Phoenicia]

Does it? The devs won't say anything until they have figured out a strategy for implementing the feedback. Its really bad business to publicly take a stance on feedback without a plan to address it.

Why not? It's not "taking a stance" when you say "We received your feedback, we will see what we can do about it."

[Mito123]

It takes time to develop content.

It takes 5 seconds to say "We have heard your feedback."

Haha you said it. All I'm asking is then to just say we aren't listening or acknowledging. I just don't want Blu to die off

[Mito123]

Outside for outlandishly poor designs that should have been caught even before, say, a public test server release (e.g. original Wanderer's Minuet), I can scarcely think of a change according to feedback that didn't take a step in a new poor direction in addition to however few steps it took forward or towards a direct, non-errant solution.

If one causes as many problems with the alleged 'solution', I can't exactly exactly say their procedures share a vessel with the complaints that solution claims to originate from.

Yeah......... Come again?

[Neela]