when will this lazy devs fix the alliance roulette?

[IDontPetLalas]

snip




SNIP"

Maybe it's time we decided what we want and then structure it in such a way that SE can turn it into a well defined feature requirement that they can implement? Instead of one group shouting over another into the aether and the one that screams loudest gets to have their moment of glory?

Let's look at this point "Time and effort are finite resources on a project. A project needs a way to streamline their processes in order to achieve all their features. "

Streamlining, or optimizing, of Square's development processes - is not (the player's community's) problem. This should is typically not visible to any customer, we're talking about software development, but it would be no different if we were discussing car manufacturing or any other industry. it's on the manufacturer.


"The game has a lot more to deal with, than just jobs. It doesn't help matters when they're feedback is thrown around willy nilly from just anyone, without proper requirements, needing to spend time filtering out the noise and find the root cause of an issue."

True, however this again is just 'a day in the life" of a community manager and, in turn, a product manager. This is real life. Requirements will be often be ambiguous, contradictory, poorly formed, and chaotic. These people spend their working lives filtering and refining them.

Lastly, the piece de resistance "Tank and Healer anxiety is a very real thing. So much so, that many players who might gravitate toward those roles can avoid playing them for fear of being called out and labeled. The homogenisation and simplification of those jobs serves more than just balancing. It also ensures that more players will play those roles, reducing queue times in the Duty Finder for everyone else. If the jobs were more complicated, a DPS' queue time might be even higher than it is now. It's one of those consequences that the community brings on itself."

Sure, some players do have anxiety when they pick up these roles. getting "called out" may happen, however both tolerance of sprouts and the TOS generally prevents this. However, it is entirely possible to balance jobs without homogenizing them. In addition, if we look at queue times before some jobs were simplified and post simplification, there doesn't seem to be any complaints. Not to mention, I would say that it is unreasonable to expect that by level 90, a healer or tank job design cannot expect to have more complexity than at (let's say ) Satasha.

[Erzaa]

Let's look at this point "Time and effort are finite resources on a project. A project needs a way to streamline their processes in order to achieve all their features. "

Streamlining, or optimizing, of Square's development processes - is not (the player's community's) problem. This should is typically not visible to any customer, we're talking about software development, but it would be no different if we were discussing car manufacturing or any other industry. it's on the manufacturer.


"The game has a lot more to deal with, than just jobs. It doesn't help matters when they're feedback is thrown around willy nilly from just anyone, without proper requirements, needing to spend time filtering out the noise and find the root cause of an issue."

True, however this again is just 'a day in the life" of a community manager and, in turn, a product manager. This is real life. Requirements will be often be ambiguous, contradictory, poorly formed, and chaotic. These people spend their working lives filtering and refining them.

Lastly, the piece de resistance "Tank and Healer anxiety is a very real thing. So much so, that many players who might gravitate toward those roles can avoid playing them for fear of being called out and labeled. The homogenisation and simplification of those jobs serves more than just balancing. It also ensures that more players will play those roles, reducing queue times in the Duty Finder for everyone else. If the jobs were more complicated, a DPS' queue time might be even higher than it is now. It's one of those consequences that the community brings on itself."

Sure, some players do have anxiety when they pick up these roles. getting "called out" may happen, however both tolerance of sprouts and the TOS generally prevents this. However, it is entirely possible to balance jobs without homogenizing them. In addition, if we look at queue times before some jobs were simplified and post simplification, there doesn't seem to be any complaints. Not to mention, I would say that it is unreasonable to expect that by level 90, a healer or tank job design cannot expect to have more complexity than at (let's say ) Satasha.

Alright. I've said all I had to say. Let's just keep going as we are, it's clearly worked for us so far. *shrug*

[IDontPetLalas]

Alright. I've said all I had to say. Let's just keep going as we are, it's clearly worked for us so far. *shrug*

You stated your opinions on a a diverse number of topics and decided to walk away, which is always your right. I have no idea of which subjects you have any experience with, nor in which context, however what I can say is none of them are simple, some of them aren't necessarily quick to resolve, but none of them will get resolved by avoiding them.

[Erzaa]

snip

Well, no. I've brought up various points to assert my argument that SE does listen to feedback and do try to make us happy. But, our feedback is scattered, with vague examples of what's wrong and often times with poorly thought out solutions. They'll do their best to address the issue a group is being the loudest about in the moment, then inadvertently cause issues for another group. Reason being, one group only thought of how the problem affected them, while the other group probably hadn't been suffering from any issues so they didn't have any reason to complain. When the new group suffers, they come and scream the loudest now about new problems.

We're giving them mixed signals about what the problem is because we can't decide what the problem is, only that there's a problem.

Example: CT is the most common raid that pops, it needs to be locked to the job's ilvl. They added an ilvl lock and wouldn't you know it, people who never complained before now can't queue because they're overleveled. Enter a 40 page thread. And being drowned out by people telling them to just go buy gear off the MB. Players who had no reason to complain in the past had something taken away from them that was working, and the response from another group is, well it works on my machine.

Is it possible to make classes distinct while maintaining balance? Probably, of course it is. But what kind of change does the community want? Do we even know?

Personally I'd like it if they trimmed abilities down to a single hotbar or less and every job played differently. I'm also not a fan of the memorise fight design with insert weird symbol here I've never seen before that FFXIV has, it makes things artificially hard in the beginning and then a joke once you know what those weird new symbols mean. That's just my own opinion and preference. I'm not going to force it down someone else's throat though.

Is that what everyone else wants? What if a player wants additional complexity and more things to press? What about player really likes the way FF fights are designed? For that matter, how should each job play? How do you balance all the different numbers so that no job ever falls behind?

We as a community need to reach a consensus on what we want, keeping in mind many of us are casual players and many of us are hardcore players and find the middle ground and propose it to SE.

But it doesn't seem like we're willing to do that. We'll attack and jump on each other for proposing something we don't like or disagree with, even if it has merits.

If we can't reach a consensus on what we want the game to be, how will SE make a game that makes us all happy.

There's not much else that needs to be said. Clearly the way things are going now are causing aggravation for alot of people, but we're unwilling to reconsider how our complaints and suggestions impact others, exacerbating the problem.