Samurai Sword Pressure/Shoha Stacks

[Lersayil]

I agree with the others, Shoha is just the symptom, Tsubame Gaeshi is the culprit. I would prefer adjustments to Tsubame over Shoha. If they want to stick to their guns, maybe a single extra Shoha charge, just to avoid that one Shoha between Midare and Tsubame.

[Eliadil]

I agree with the others, Shoha is just the symptom, Tsubame Gaeshi is the culprit. I would prefer adjustments to Tsubame over Shoha. If they want to stick to their guns, maybe a single extra Shoha charge, just to avoid that one Shoha between Midare and Tsubame.

I mean, they already touched Shoha enough, I think that any more tinkering with the skill will not change the main issue anyway. I'm against the idea of an extra stack since this would be completely different from the mentality they have about overcapping ressource. With Bard you cannot stack Bloodletter procs so you have to use it on cooldown. Machinist don't have an extra 20 to their gauge to prevent overcapping... Every class demands that you prevent overcapping by using the ability, not by giving you some extra gauge to avoid overcapping.
In fact, the current design makes samurai quite akward when it comes to this, looking at how we have to completely twist our basic rotation to use Tsubame on cooldown. The flaw in the design lies within Tsubame from the beginning.

[SpeckledBurd]

I mean, they already touched Shoha enough, I think that any more tinkering with the skill will not change the main issue anyway. I'm against the idea of an extra stack since this would be completely different from the mentality they have about overcapping ressource. With Bard you cannot stack Bloodletter procs so you have to use it on cooldown. Machinist don't have an extra 20 to their gauge to prevent overcapping... Every class demands that you prevent overcapping by using the ability, not by giving you some extra gauge to avoid overcapping.
In fact, the current design makes samurai quite akward when it comes to this, looking at how we have to completely twist our basic rotation to use Tsubame on cooldown. The flaw in the design lies within Tsubame from the beginning.

Actually most jobs and gauges prevent overcapping, the cost and the maximum capacity of a gauge usually has an overhead of two times whatever the most expensive skill for it is. The only exception to that is Monk, which doesn't have any flexibility on using its gauge because its gauge is and always has been terribly designed. You're either full on Chakra and can use Chakra or you aren't full and can't use Chakra skills. Monk/Chakra is actually worse than Samurai/Meditate in this regard though because procs are random so we can't plan around it even in the worst case like having 2 meditation going into a Midare>Tsubame, you'll just cap on Chakra when you're already committed to a different oGCD and you'll just lose an additional random proc if you crit on the GCD after.

We've been complaining about it for years, but we've been complaining about a lot of things for years. They changed Shoha within a patch for you though so they're more likely to listen to Samurai.

[Eliadil]

*snip*

Well technically procs for chakra are based on GCDs, so you can technically predict them. Brotherhood makes it kinda difficult that I agree, but due to standard party composition not being 8 physical class you often don't have five chakras proc at once. The fact that monks GCDs are the fastest of the game also enables more windows to used oGCDs like forbidden chakra. But I do understand the issue with the gauge as it is.

Still they reduced the rng factor of most class by a lot this expac, dancer being kinda the only exception and peoples hate this aspect of the class. Maybe with 6.0 random chakra procs will be only but a memory.

I'd like to agree about the "listening" part, but I think they just figured out that the skill was crap or not used properly (peoples fishing for meditate procs wasn't what the devs wanted, just like they didn't want anatman fishing) so they reworked both Meditate and Shoha.

We all know anyway that a handfull of jobs needs a rework on some specific skills to be truly enjoyable. SE showed us however that they weren't afraid of reworking entirely jobs that needed it, so my guess is that they will eventually change individual skills too so that jobs are more enjoyables.

Efficient is nice. Fun and efficient is better. Currently a lot of jobs lacks some fun factor. No job has less right to ask for that than another one.

(Since they don't listen anyway lmao )

[Shurrikhan]

Well technically procs for chakra are based on GCDs, so you can technically predict them.

Yes, but not to a degree that is terribly useful. They come up so late that you have to be pre-spamming Meditate/TFC at 4 Chakra to possibly get TFC off before costing you uptime, which then risks the abomination that is using Meditate during melee uptime if you have any latency. Because of that delay, which initially seems faint, but at GL4 is punishing, this gets increasingly problematic with lower GCD speeds.

[Lersayil]

I mean, they already touched Shoha enough, I think that any more tinkering with the skill will not change the main issue anyway. I'm against the idea of an extra stack since this would be completely different from the mentality they have about overcapping ressource. With Bard you cannot stack Bloodletter procs so you have to use it on cooldown. Machinist don't have an extra 20 to their gauge to prevent overcapping... Every class demands that you prevent overcapping by using the ability, not by giving you some extra gauge to avoid overcapping.
In fact, the current design makes samurai quite akward when it comes to this, looking at how we have to completely twist our basic rotation to use Tsubame on cooldown. The flaw in the design lies within Tsubame from the beginning.

Its was an example in case they really want to keep Tsubame as inflexible as it is. Personally I don't care much about the how, as long as I don't have to cram in that odd Shoha between the Midare and the Tsubame anymore.

Even if I pay attention, thats a pretty narrow window for an oGCD.