- Reason
- The affirmation wasn't worth the time.
Player
Are you honestly claiming that lingering Sen between pulls was the only thing that ever made ShB SAM clunky? That's all currently Hagakure is "good" for, after all, and it's a damage loss even then.
The only reason for Shoha not to be used is if people were literally never touching Meditate, even to weave it. And that's simply not the case.
Then you should open your eyes. It's been frequent complaint since ShB release ("Somehow even more constraining than Hagakure and a hell of a lot more clunky"). And if your "literally no SAMs" isn't hyperbolic then you need look no further than... this thread.
Akhem, hagakure is actively used in rotation if you opt for 29 or 30 gcd rotation as you will have time for 2 or 3 filler gcds
Which is a far greater loss than simply using Yaten-Enpi 2-3 times to reach the same rotational length. Each Yaten-Enpi costs 20 potency.
On the other hand, every 3-sen Hagakure has an opportunity cost of a Kaiten Midare (1200) - 4/5ths of a Shinten (256) - one average GCD of potency (426)--or 518 potency--just to gain 192 potency, reaching a net value of - 326 potency. Yes, negative 326. Every time you use Hagakure, you may as well have done absolutely nothing for 77% of a GCD.
Player
So, if I'm correct you're just saying that Samuraï has a smooth rotation if played properly, and saying that keeping uptime and avoiding downtime because it does enable a cooldown drift is the real issue. So, a Rotation where missing a GCD due to mechanics makes our burst drift away from the buff window is a correct rotation ? And the fact that the new Haga is a dps loss when you erase the filler Sen is a good idea ?No, the clunkyness came from either a) drifting CDs or b) Over-writting Sen. Haga took care of that and made the feel of the class so, so much better, along with ending the actual clunkyness in rotation and during downtime. Those were the 2 biggest feel and performance issues with 5.0 SAM. So ya, I am claiming that. But please, tell me more about how a class you barely play is "clunky."
Keeping uptime and keeping the loop going after downtime is a real issue. The real issues are talked about.
SAM's rotation is fine. Tsubame is fine. The class, PLAYED PROPERLY, is silky smooth and lacks clunk.
Even when the rotation forces you to use a filler (so a somewhat dps loss) in order to make Tsubame line up correctly ?
Furthermore, you're also advocating that the rotational issues are talked about. Seeing the 5.1 changes announced, except if they make Shoha a Weaponskill, I doubt we'll see a decent filler which will make the rotation not require wasting a spell in order to line up Tsubame, so I hope you'll pardon me for doubting about that part
Even tho it means that you've played Stormblood Sam, so you do know that there is a huge, huge difference between 4.X sam and 5.X, which is the reason why we are sad about this, because we lost every tiny bit of flexibility since we have to line up a GCD that is the end of our 9 part combo, every minute without missing any GCD otherwise we're just losing damage and drifting away our burst.
Before, you could just line up whenever your group used a burst window because you do not lose dps for doing so. Now if you're out of it because you had to step out (let's say because a sad mechanic forced you to stand away from the boss to avoid an aoe like in E4S Phase 2) then you're just screwed. This, is what I define as "clunky", when you have to stick to the strict 60sec loop and you're getting punished by a dps loss if a mechanics forces you to drift cooldown. Because yeah, Hagakure is a dps loss atm, I think Shurrikhan explained it well. My point is that even tho you're using Haga to burst in time, you're still losing way too much damage in using Hagakure because you did a mechanic properly.
And I hope nobody here will ask you about your savage clears. We're here to talk and exchange ideas and opinions. Not compare the size of our katanas.![]()
Still not sure if Samurai's a tank who forgot that aggro was a thing or a dps that's way too much into it.
If "optimal play" involves taking what would be a 326 potency loss if TG had even just a 5-second grace period, just to meet the rigid constraints of that skill, that is clunky. It'd be far better instead to simply remove the limitation that enforces the loss and then balance around that removal.No, the clunkyness came from either a) drifting CDs or b) Over-writting Sen. Haga took care of that and made the feel of the class so, so much better, along with ending the actual clunkyness in rotation and during downtime. Those were the 2 biggest feel and performance issues with 5.0 SAM.
Think about it in terms of any other job, such as if Warrior had a skill which increases Critical Strike bonus damage by 20% (e.g. from 50% to 60%), but deals no damage. The skill would be obligatory for Berserk/Inner Release, but an absolute trap otherwise. And that still wouldn't be as convoluted of design as what TG-Hagakure applies to SAM's toolkit.
Put simply, we shouldn't need to use an anti-potency ability just to use our strongest ppm increase. I'd much rather, say, have Hagakure be potency-neutral (worth +362 potency) and Tsubame-Gaeshi be affectable by, but no longer benefit automatically from, Kaiten (worth -256 potency). Heck, that resulting +106 ppm would be almost exactly what we need to hit MNK rDPS. That way, TG does not require Hagakure and Hagakure does not require TG. Both skills would be smoothly usable in their own rights, and at a much wider span of SkS breakpoints.
Last edited by Shurrikhan; 10-22-2019 at 06:38 AM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.