#FFXIVHEALERSTRIKE

[Aravell]

are we on the same forum? i mean it's really funny. i'm talking to you and then someone else is giving me the answers i expected from you. so i named them "aravell". and i still find it funny that someone feels like they almost have to speak on your behalf because you didn't say anything.

The sad thing is that, in addition to the technical aspect, you are also accusing Square Enix employees of things that you can't even justify.
You just make claims without any basis and when asked for more information, you change the subject or look for another reason to end the conversation.

These are real, living people that you are talking nonsense about.

Real, living people that made mistakes. Mistakes which they admitted to. You would know this if you played the jobs when they were broken and if you read the patch notes.

Being human does not absolve someone of criticism. I also never said anything bad about the employees, I only said they're fine with releasing things in a broken state, which is a statement of fact, not an insult.

You should stop holding the dev team above criticism when you seem clearly ignorant of all the mistakes they've made and admitted to making.

That's why I brought up history btw, not to deflect or whatever you accused me of. The dev team has a clear history of making very bad changes with little thought about how it affects everything else, they've even apologised for some. Like how removing ED from SCH broke their resource generation and removing Hagakure broke SAM's loop. You can't seriously tell me those 2 changes were well thought out, considering thar they broke the job's gameplay loop.

Also, your little joke is unamusing, I didn't respond to you immediately because i have a life to live outside of the forum.

[sharknado]

I feel like that should be celebrated as an achievement ?

Creates player perception and player perception is the hardest to balance jobs for. The game doesn't really need reasons to break intended compositions for real or perceived gains to then sprouts asking which job they should pick when moving after free trial because they are white mage and healers aren't used in whatever streamer, static they are fans of.

[SamLeens]

On this specifically, I think there is a point to be made about testing in that if SE did test it they really screwed it up with having jobs that were MP negative. Other issues we have seen are with little things like the 7.0 MNK launch having potency issues, DRK and GNB gap closers having no enmity when they removed potency, when SE buffed Glare in EW and made Afflatus Misery a DPS loss. It's just a concerning trend that SE is missing pretty obvious things that you would notice either through reading tooltips or testing it for a little bit.

I can completely understand what you are saying. I accept and agree 100%. Something has gone very wrong.

For me, there is just a big difference between saying "they never tested any of the changes" without providing any more facts, or saying "they screwed up somewhere, look into it" and then facts follow.

Thanks for the clarification.

[SamLeens]

Real, living people that made mistakes. Mistakes which they admitted to. You would know this if you played the jobs when they were broken and if you read the patch notes.

Being human does not absolve someone of criticism. I also never said anything bad about the employees, I only said they're fine with releasing things in a broken state, which is a statement of fact, not an insult.

You should stop holding the dev team above criticism when you seem clearly ignorant of all the mistakes they've made and admitted to making.

That's why I brought up history btw, not to deflect or whatever you accused me of. The dev team has a clear history of making very bad changes with little thought about how it affects everything else, they've even apologised for some. Like how removing ED from SCH broke their resource generation and removing Hagakure broke SAM's loop. You can't seriously tell me those 2 changes were well thought out, considering thar they broke the job's gameplay loop.

Also, your little joke is unamusing, I didn't respond to you immediately because i have a life to live outside of the forum.

i read all the patch notes and played ast and drk first. That doesn't change what you said and the fact that you don't give me any answers and probably never will. You could have just said you didn't want to answer or ignored me. That would have been fine too.

So when you say "they never tested any of the changes" as if that was a fact and not just your interpretation, do you mean that in a positive way?

No, don't get me wrong. I don't care if it's about the developer or another player. Statements thrown out without facts as if they were true when in reality it's just what the person is feeling at the time are too often misleading.

Your first reaction was to talk about history. you decided what kind of text you wanted to write so i don't know what that has to do with your everyday life, but i'll just leave it as it is.

[Aravell]

Snip

You keep saying I won't give answers when in the first post which you quoted, I already gave 2 examples of jobs not working, indicative of a lack of testing. In a subsequent post, I gave one more example.

All 3 of those examples led to a change/reversion later on btw, so it's not a new direction they were going for.

There's also the very recent example in 7.01, where the dev team oversight led the MNK rotation to be DK>BS>repeat, that's something which the community caught in the patch notes but somehow the dev team didn't catch before release.

Also a very old example was that old unintended interaction where WAR got 100% critical heals from the back during RI, that also shows they didn't test thoroughly.

But you can also choose to pretend that I haven't given any answer, it's no skin off my back.

[ForsakenRoe]

Here, I'll do it myself (from the Patch 5.05 notes):



AST was so bad on SHB release, that some of its actions had to be doubled in strength AND doubled in how frequently they were up (looking at Celestial Opposition)

[Shurrikhan]

Your first reaction was to talk about history. you decided what kind of text you wanted to write so i don't know what that has to do with your everyday life, but i'll just leave it as it is.

They left you to Google any of the expansions' x.05 or x.1 patch notes, which takes all of 3 minutes to scan the relevant sections of fully across ARR and every expansion since, seeing as you seemed unable to make use of the prior examples yourself.

You then used wording that would reasonably be taken as an accusation of sock-puppeting to dismiss the information granted you when someone did that for you, all because you needed the... what... satisfaction(?) of the same person asking you, in effect, to do your homework to then do it for you? And immediately, at that, as if they were obliged to be terminally online?

So when you say "they never tested any of the changes" as if that was a fact and not just your interpretation, do you mean that in a positive way?

No, don't get me wrong. I don't care if it's about the developer or another player. Statements thrown out without facts as if they were true when in reality it's just what the person is feeling at the time are too often misleading.

To give an another example, see Bow Mage, which did not even work in the way they thought it did, and started off as a literal DPS loss because they hadn't accounted for the loss of auto-attack damage, something clear to players within a single run using it.

While "released without any testing" could already have been reasonable discourse in the vein of slight hyperbole (for "there was *seemingly*/"effectively" no testing"), there's also a few places to point at for decent evidence of it (where going untested would have been a less egregious error than having tested the fundamentally broken thing and thinking, even after that testing, that it was fine).

[SamLeens]

You keep saying I won't give answers when in the first post which you quoted, I already gave 2 examples of jobs not working, indicative of a lack of testing. In a subsequent post, I gave one more example.

All 3 of those examples led to a change/reversion later on btw, so it's not a new direction they were going for.

There's also the very recent example in 7.01, where the dev team oversight led the MNK rotation to be DK>BS>repeat, that's something which the community caught in the patch notes but somehow the dev team didn't catch before release.

Also a very old example was that old unintended interaction where WAR got 100% critical heals from the back during RI, that also shows they didn't test thoroughly.

But you can also choose to pretend that I haven't given any answer, it's no skin off my back.

Okay, wait. There were two things i was questioning.
1) how do you know that "they never tested any of the changes"?
and
2) where? when? how do you know that "they're perfectly happy with massively changing jobs with little to no warning"?

did i miss the answers to these questions? if so, i don't mind reading through both forum pages again. i'm going to take a little break soon anyway.

[Aravell]

Snip

1) Can you say with 100% certainty that they did test anything when there's been so many bugs and oversights?

2) If they haven't changed the job again, then it stands that they're perfectly happy with what they did.

Anything else?

[Sharawiwi]

It's so so weird how the people trolling and dismissing this strike are never healers, always tanks or dps, but are trying their darnest to keep healers in their sorry state.

I do wonder what their stances on social strikes or minority rights are in real life, truly a mystery, guess we'll never know...