[SAM] I hate the change to Tsubame-gaeshi

[Akava]

Its far too restricting compared to how it was in Endwalker.

1. I used to split Meikyo Shisui and Tsubame usages between AoE packs. Now I can't.
2. If a pack dies after using Tenka Goken, I lose Tsubame. So now its better to Hagakure instead of using Tenka
3. If Meikyo is about to cap but I'm holding burst, I now have to always hold Meikyo instead of making my own decisions

The gist of it is, the change makes several assumptions about when I'll want to use Tsubame and its not always right. Not to mention it gives me a buff to use Tsubame and we're seeing buff cap issues more often lately. Why add yet another buff when it wasn't needed before?

[AlgrenH]

from what i gathered from the samurai channels in the balance this is a pretty widespread opinion. The change basically removed any flexibility or variance to the job rotation aswell as kneecapping any "adhoc" style of gameplay.
If only we had a oGcd we'd press before every iaijutsu we could use instead of meikyo to enhance our midare and tenka goken casts. perhaps removed in 6.1? /s
but seriously, who actually wanted and asked for this change? the job worked perfectly fine in Endwalker up untill 7.0 release. Stuffing everything on meikyo was a big misstep, in the direction of the BLM changes.

[ShadowyZero]

agreed this change seems wholly unnecessary an i'm just as confused as to what the thought process was behind it. hopefully in the .5 or 7.1 patch it gets reverted back

[Brownondorf]

Yes, that change is horrible.
In theory, the change doesn't matter all that much for trials/raid fights BUT, it is so bad for dungeons/casual play. zero flexibity anymore.
What were they thinking? They better revert this ASAP.

[nguyentri11]

My 2 reasons for hating this change are:

1. Meikyo has to be used before Iai or you delay the Tsubame and likely miss a raid buff window.

2. Before this change if you forgot to Tsubame after an Iai all it did was delay when your next Tsubame will be. Now if you Meikyo then Iai and forget to Tsubame you lose that Tsubame because the Iai has already consumed Tsubame Ready. In this aspect I feel like it's actually less forgiving for casual players.

There's too many downsides for their reasoning of "streamlining CD management". And I don't understand why you need to streamline the CD management of Meikyo and Tsubame when both of these CDs are on a 2 charge system. I think they tried to shoehorn this change because they needed a way to force you to do Meikyo before Iai -> Tsubame for their "upgrade" conditional buff to Iai/Tsubame.

[Shurrikhan]

I do not understand the point of the change at all.

The skills weren't necessarily, or even all that often, paired in their use, let alone in the set order of Meikyo -> Tsubame.

And even if they were, they've applied no button-consolidation to make use of that. It's purely loss of flexibility... at no gain.

[red_fang]

Tsubame change is clunky and makes the job feel even worse, didn't think that was possible but here we are.

Please revert it and go back to stacks that I can use at my discretion. Also stop the person at Square that is making these poor design decisions on SAM, as this change feels almost contemptuous in nature.

Is there anyone in this company that even reads feedback on this job, or gets why people liked past versions of it?

[Miki_L]

This change was really misguided. I wonder if it's the last change they did and assumed it would work? If they are willing to remove kaiten mid expansion then I would hope they are willing to simply revert this change in a later patch like 7.1. This is not something that I think can be fixed. If their issue was that noob samurais would drift their tsubame, then why not make the cooldown 55 seconds instead?

It feels horrible in any content that is not single boss training dummy. And it seems their intentions this expansion is to release less content that fits that mold, so what gives?

[Wyssahtyn]

Agreed, it's a pretty bad change and just makes things feel clunky. Think it's increasingly clear that whatever dev(s) keeps pushing changes on this job doesn't even play it.

[Valence]

The point of the change is to constrain rotations to a rigid script that should deviate even less from their burst alignment meta and doesn't tolerate any "freestyling" to make sure players play it "correctly". With that in mind every raid burst relevant button should be tied to the rest and lock every big attack behind.