
The devs have been removing core buttons of jobs long before 6.1Called it. Not even a passing mention in the LL short of DRG and AST changes being delayed.
Once my sub runs out I'm not re-upping. The games direction is all but cemented in continuing down this awful path. ARR to 6.08 was lightning in a bottle I guess. Oh well, 10 years or so of enjoying a game is better than none I suppose.
Last edited by Katoar; 07-03-2022 at 02:35 AM.


I’m feeling pessimistic about any reversions at this point to be honest; the lack of even a slight acknowledgement of the numerous amounts of feedback that they specifically asked for is unfortunate.
A localization forum thread did get a higher-up response about leftover action description issues, so responding to that response with the restoration of Kaiten as a solution to that raised issue might be more likely to be seen at this point.
I think at this point we can postpone the doomsaying until the next live letter. That will be the moment to make or break us. Feedback has been given, dislike has been said ad nauseum.I’m feeling pessimistic about any reversions at this point to be honest; the lack of even a slight acknowledgement of the numerous amounts of feedback that they specifically asked for is unfortunate.
A localization forum thread did get a higher-up response about leftover action description issues, so responding to that response with the restoration of Kaiten as a solution to that raised issue might be more likely to be seen at this point.
Also, the localization thread is there about translation issues in the game. Grammatical errors. And before you point out, yes I did post there as well, and guess what... the higher-up that responded never responded beyond the grammatical error post. Kindly stop suggesting we go to a different section. They aren't reacting to it like you keep saying they are.


The thread raised a problem with regards to an action having a wrong description; one solution to that would be to revert the Kaiten-related changes so that the description would thus be correct again, so I don’t see that as an unreasonable or off-topic response to the higher-up comment that was left in there.I think at this point we can postpone the doomsaying until the next live letter. That will be the moment to make or break us. Feedback has been given, dislike has been said ad nauseum.
Also, the localization thread is there about translation issues in the game. Grammatical errors. And before you point out, yes I did post there as well, and guess what... the higher-up that responded never responded beyond the grammatical error post. Kindly stop suggesting we go to a different section. They aren't reacting to it like you keep saying they are.
Ok, good luck with that.The thread raised a problem with regards to an action having a wrong description; one solution to that would be to revert the Kaiten-related changes so that the description would thus be correct again, so I don’t see that as an unreasonable or off-topic response to the higher-up comment that was left in there.


I mean, healers have largely limited their continuously ignored feedback regarding consistently limited DPS variety to the Healer forums, but that doesn’t seem to lead to any higher-up forum responses; the General Discussion forums got an official response for Hrothgar hair, which is one more forum response than the Healer forums ever got, so perhaps healers have a better chance there?
More developer responses have happened in the localization and general discussion forums, so that can arguably create an image of some forums being looked at more than others; I’m not saying that’s objectively what’s happening, but that people in this thread were surprised to see a rare developer response somewhere in the forums kind of helps illustrate my point.
Posting about this in the aforementioned localization thread technically isn’t off-topic either since it was talking about a problem that was introduced by the Kaiten changes and thus could also be solved via obsolescence by reverting some changes.
Removing Kaiten was a fundamental mistake. Kenki management has now been criminally dumbed down.
Basically, Kaiten was the only thing that prevented a player from wanting to expend every bit of kenki whenver they had enough to use. The decision making on using abilities is now nonexistent.
My management of Kenki on samurai is now:
Getting a programmable mouse with a large amount of buttons on the side panel (In my case, the razer naga, which has 12 buttons that can be reprogrammed to whatever you want. In my case, I bind them to the numlock 1-10, - and =). The layout of this mouse looks like this:
1 2 3
4 5 6
7 8 9
0 - =
I bind my keys in two separate patterns, one for single target, and one for aoe.
1 is bound to Senei
4 is bound to Shiten
7 is bound to Shoha
0 is bound to Ikishoten
3 is bound to Guren
6 is bound to Kyuten
9 is bound to Shoha II
= is bound to Ikishoten
Whenever I hit 25 Kenki (or just whenever, I basically spam it) I run my thumb down one of these lines, depending on single target or aoe. If I do it in this order, then it will make sure that they are used in this order, depending on cooldown. All of Samurai's class resource abilities, I am able to absent-mindedly ignore, and do on auto pilot. There's no punishment for mismanaging Kenki, besides letting it overflow I guess. But it never WILL overflow, if you just use it as soon as you hit 25.
The removal of Kaiten was such a fundamental mistake, that ripped away at the core of Samurai's meter management. It needs to be added back in, in order to correct this issue. Is Samurai easier to play now? Yes. Is it still fun? Not as much.
I don't know a single samurai player who likes this change. If they really wanted to remove skill bloat, there had to be something better to remove. Without Kaiten, there is fundamentally zero active management of Kenki, that can't be done by rolling your finger down a line, without even paying attention to what you're doing.
Above all, I can tell that the person who decided on this change was not a samurai player. It was someone looking at the raw numbers, and thinking that it was a superfluous skill, when it defined Samurai's kenki usage. Now, the class feels fundamentally incomplete.
I can accept that possibly, with future reworks in mind, kaiten couldve been a limiting factor in job design. Possibly. But to remove a key ability, mid-patch cycle, say nothing and replace it with nothing for "a future rework" is unacceptable. Kaiten was the only thing you had to think about. How easy do they want it to be?
Have you seen SMN? I think that alone basically answers any questions on where they intend to go with job design for future iterations.I can accept that possibly, with future reworks in mind, kaiten couldve been a limiting factor in job design. Possibly. But to remove a key ability, mid-patch cycle, say nothing and replace it with nothing for "a future rework" is unacceptable. Kaiten was the only thing you had to think about. How easy do they want it to be?
Summoner was fun to play before but i dont touch it now cause its braindead and unrewarding. If more of the jobs I like to play get that same treatment I can see myself quitting in 7.0.
|
|
![]() |
![]() |
![]() |
|
|
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.

Reply With Quote



