Thread: Welp, 2.1 is going ot be a happy time for warriors!

if i understood well they are gonna change the kick so its works like the PLD and buff Inner beast so when we use it while a heal has alrdy launch a heal the overheal will not be lost. Like a shield same as Scholar or a %reduction of incoming damage thats all we need.

Thought the frontier of Opness is close so i hope they wont cross it ^^
But id love the idea of double inner beast that shields me for 3k.

awesome , I have both lvl 50 paladin and warrior so any changes to make one better is good .

Warrior does slightly more dps than paladin so I would rather play warrior as tank if they were as good as paladin .

So whatever they do is good.

From my understanding of the letter Warrior's Brutal Swing will be getting a lower cool down in favor of making fights like Ifrit where the tank should be responsible for completely negating eruption, as the cool down really prevents a warrior from also legitimately stunning targets for unclear reasons which they want to get rid of.

He's also mentioned that the Warrior's utilization of Wrath's bonus to healing because healers can't heal their additional health pool sufficiently because warriors use their Inner Beast inappropriately. From the allusion it looks as though they're planning on addressing the bonus to healing on wrath without anything on Inner Beast itself.

In summary: lower CD on Brutal Swing and they're going to change how our bonus to healing handles *after* Inner Beast. Anything within these bounds won't be "game breaking" as it sounds as little more than a crutch for warriors with timing problems.

The only "problem" with Yoshi's thought on how WAR should have utilized IB is that the timing becomes critical on some fights. Simply waiting for cures with any poor timing on the mage(s)'s part (and with very little in the way of meaningful preemptive cool-downs) can easily lead to death; imo, this is a big oversight when WAR's most notable action (Inner Beast) is a reactive ability that is capable of defying a deadly spike in damage.

Originally Posted by Skull_Angel

Simply waiting for cures with any poor timing on the mage(s)'s part (and with very little in the way of meaningful preemptive cool-downs) can easily lead to death;

This is a very good point, and thank you for bringing it up. Factoring in latency and reaction time given the mere seconds one has to finish casting a heal on top of any dodge work needed to stay alive- it's clear the problem wasn't solely on the warrior or the healer(s) as the level of understanding of the boss mechanics and timing would have to rival that of dev and alpha testers which is something few possess. It's a clear and present need and I'm glad they're addressing it for the majority of players.

Originally Posted by Exrage

Anything within these bounds won't be "game breaking" as it sounds as little more than a crutch for warriors with timing problems.

Apparently the money from those WARs with timing problems are worth A LOT more than those of a WAR without such problems if they're implementing such a change.

y; once the boss has 3 buffs stacked up the tank won’t be able to pass
y; it’s set up that way

Surviving 3 stacks wasn't intended. I'm sorry SE, but did you even test this fight? It wouldn't have taken long to see that DL PLD could survive more than 3.

Great news.

But where are all the people who were sure that both PLD and WAR were perfectly balanced with one another, and everyone just needed to L2P? Do the developers need to L2P now too?

Originally Posted by BadRNG

Great news.

But where are all the people who were sure that both PLD and WAR were perfectly balanced with one another, and everyone just needed to L2P? Do the developers need to L2P now too?

busy trying to process how (in their mind) a forum troll could be right about devs being wrong

that or they never really cared in the first place/were just fed up with anti-class bias and just wanted people to stop complaining