Buttons not reacting in PvP and ranking up

[Hazelx3]

Hi everyone.
I am a new player that started in the end of 2025 december.
I have a question for you, today a new season started and I played PvP.
I noticed that my buttons are not reacting, when I press a button I need to press it multiple times until it works.
My internet is fine, so it should not be this problem.
Another issue I had was the ranking up system, I made it from Bronze to Gold with no issues, then I took a break and came back again and lost all my stars from Gold as different people were in queue at night. I was told I should try it next day, because EU PvP has not much players, and some teams constellations are not that good.
Do you have an idea, how I can fix the problem with the buttons not reacting? Sometimes I even press them multiple times and still does not react, only after some time it does.
I would appreciate your help. If the buttons would react after one click it would be much more enjoyable to play PvP and I would make less mistakes (e.g. healing too slowly)
In PvE, for some reason, I do not have this problem, it only occurs in PvP.
I am playing the game on the Steam Deck, but I do not think that it is the issue, because PvE works fine for me.

[Valence]

That's certainly odd. Everything has stupid animation delays that can make everything feel like it plays underwater but what you describe sounds more dire.
Do they only do that when you're in the middle of successive/intensive skill use (where every action has baked in animation delays between each input), or even when you're literally doing nothing, you just press a button and the issue still happens regardless?

[Hazelx3]

It happens sometimes, when the match begins, I want to dash to an opponent, but nothing happens and I have to press the button twice. Its very annoying as I can never be sure, if my character will attack or not. I do not know if the issue is only on the Steam Deck, as I cannot test it on a PC (Only have a Laptop and its too weak for the game) If I am in a middle of a fight, it happens more often

[Mikoko_Miko]

Which job and action did you use when dashing? Some actions allow you to move forward regardless of the opponent's position, while others require the opponent to be within range.

Regarding the rank up issue, could this be related to the 7.5 update?
Patch 7.5 Notes

Players will begin Season Twenty five risers lower than the rank at which they finished Season Nineteen. Rising Stars will be reset to one.

[Hazelx3]

Which job and action did you use when dashing? Some actions allow you to move forward regardless of the opponent's position, while others require the opponent to be within range.

Regarding the rank up issue, could this be related to the 7.5 update?
Patch 7.5 Notes

If I play GNB for example and want to dash to the opponent, it does not happen, instead I have it click it again to make it work, but there is no error message. Same happens sometimes when I want to use my AOE. What I meant that the game lose or win ratio can be completly random, when I first started I made it from Bronze to Gold and then I took a break, wanted to make Platinum and lost all my stars from Gold. Today the same happened, I had a big loss streak, then waited a bit, played again and made it to Platinum. This seems like it depends on the team constellations or how lucky you get as its a 5v5 with completly random people. Also the same happens if I want to heal myself with the potions or use purify, I have to click it more than once midfight even when I am not stunned, to make it work. Could you probably test it and see if the same happens for you? Does the server make a difference? Because I am playing on EU server. I have 30 fps.

[Loggos]

I feel you. It happens to me so often that it genuinely impacts my matches.
I play with a PS4 controller. The issue has occured both on PS4 itself as well as on PC (via bluetooth/DS4Windows and via usb cable/steam controller overlay). My ping is around 17-20ms. I've updated my drivers.

It explicitly happens even when I'm not stunned, silenced or otherwise CCed and when I'm not animation-locked. Often times I'm quite literally just running or standing (without a status affliction/CC) while mashing a button but nothing happens. Oddly enough I DO see the button input (that visual ingame cue on your hotbar when a button is pressed) in those instances. It just doesn't translate into an effect.

It can affect every skill but I notice it particularly often with my

• LB --> Often I have to press 4-5 times before my LB activates (again, even when not stunned/CCed etc.). This is particularly frustrating when you want to time your LB but then you just stand there next to your opponent very un-menacingly for 5 seconds.
• Sprint --> It will sometimes straight-up not activate for the first few presses even when the only thing I do is running.
• Recuperate, guard and purify --> I feel like those often don't go through in particular when I'm under fire so I wonder if the game can't compute/process/[insert correct IT term here] so many actions coming from different players at once.
  It is super frustrating when it happens with purify. Frequently when I'm CCed purify will just not react (and then I die because I couldn't break the CC in time).
• Palette swap (on pct)

Those are the most egregious ones for me. I guess I notice it with those skills the most because it hurts the most when they fail. But it has happened to me across all jobs and all actions.
Valence pointed out it might be when there's a lot going on and I do feel as if those circumstances exacerbate the issue a lot. In very busy moments where lots of players use lots of actions in one spot the reactivity of my buttons gets noticeably worse. But it also happens in "calm" situations in a match (I'm just running without being attacked). It rarely, if ever, happens outside a match on a training dummy though.

I'm begging you SE, please fix this.* This problem has been the number one issue of my frustration with CC. T__T
It's really not fun to lose encounters or even matches because you pressed those buttons, you did the things you were supposed to do (for once), and the game just nopes out repeatedly.

*(Or if anybody has an idea what I'm doing wrong please let me know. :') )

[Hazelx3]

I feel you. It happens to me so often that it genuinely impacts my matches.
I play with a PS4 controller. The issue has occured both on PS4 itself as well as on PC (via bluetooth/DS4Windows and via usb cable/steam controller overlay). My ping is around 17-20ms. I've updated my drivers.

It explicitly happens even when I'm not stunned, silenced or otherwise CCed and when I'm not animation-locked. Often times I'm quite literally just running or standing (without a status affliction/CC) while mashing a button but nothing happens. Oddly enough I DO see the button input (that visual ingame cue on your hotbar when a button is pressed) in those instances. It just doesn't translate into an effect.

It can affect every skill but I notice it particularly often with my

• LB --> Often I have to press 4-5 times before my LB activates (again, even when not stunned/CCed etc.). This is particularly frustrating when you want to time your LB but then you just stand there next to your opponent very un-menacingly for 5 seconds.
• Sprint --> It will sometimes straight-up not activate for the first few presses even when the only thing I do is running.
• Recuperate, guard and purify --> I feel like those often don't go through in particular when I'm under fire so I wonder if the game can't compute/process/[insert correct IT term here] so many actions coming from different players at once.
  It is super frustrating when it happens with purify. Frequently when I'm CCed purify will just not react (and then I die because I couldn't break the CC in time).
• Palette swap (on pct)

Those are the most egregious ones for me. I guess I notice it with those skills the most because it hurts the most when they fail. But it has happened to me across all jobs and all actions.
Valence pointed out it might be when there's a lot going on and I do feel as if those circumstances exacerbate the issue a lot. In very busy moments where lots of players use lots of actions in one spot the reactivity of my buttons gets noticeably worse. But it also happens in "calm" situations in a match (I'm just running without being attacked). It rarely, if ever, happens outside a match on a training dummy though.

I'm begging you SE, please fix this.* This problem has been the number one issue of my frustration with CC. T__T
It's really not fun to lose encounters or even matches because you pressed those buttons, you did the things you were supposed to do (for once), and the game just nopes out repeatedly.

*(Or if anybody has an idea what I'm doing wrong please let me know. :') )

Yes, it happened for me too especially with the sprinting. I think you should normally have sprint all the time without pressing it, would make it so much easier. Sometimes I died, because after pressing a potion or purify, nothing happend and that can mean if you die in a specific moment, the whole match can be over.

[Mikoko_Miko]

Thank you for the information. After the update, I played some Frontline matches as a Sage and used Icarus many times on both allies and enemies to dash to a target. I play on PC via Steam and recorded my matches using the recording feature. Upon reviewing my recordings, whenever Icarus was not working without an error message and I was not affected by a status effect, the target was out of range. I use the JP datacenter, and my ping is usually around 20ms, but it can occasionally be slow. I often felt that actions were not working, but the cases I can think of mostly occur when the network is lagging. There was an exception, but it does not seem to be related to your case. I once experienced an issue where I could not attack an enemy within range and in line of sight, but it turned out that the auto-facetarget option had been disabled unintentionally.

While team matchmaking in Crystalline Conflict is indeed random, I think the mechanic where duplicate jobs are not allowed within the same team could be a contributing factor. For example, if an experienced player keeps playing the same job as me, they will always be placed on the opposing team and never on mine. As a result, I ended up on a losing streak.

[Hazelx3]

Thanks for trying, could you possible try with a class like Viper or Gnb where you have to use your buttons quickly? It will happen a lot, atleast thats what happened to me. On war for example, where I do not have to use a lot buttons, it happened less. For example if you are attacking someone, then you need to switch target and dash (sometimes dash did not work for me, unless I press it multiple times) best if you try it on unranked CC for a few times with these classes, or classes that have to press a lot of buttons. Atleast for me, even when I was not in an animation it often did not work for some reason.

[UseYour]

yup i know exactly what you mean and its not new with any patch. You first need to learn the game servers have big gaps of time between updating info, they do it for security reasons so nobody can give or take info to the server and cheat. What that means for us players is we sit around waiting for the ancient librarian to give the nod for every action we take. Think how many times you can click a button per second, and realize humans reaction time is around 130ms. When the server updates around 2-3 times a second before you even add the there and back again latency for your data to reach the great librarian, get queued, unscrambled, verified, sent back home, and updated on your screen... Some times you can mash a button 5 times before the old bones down at FF14 give the thumbs up. Its also why a lot of other nonsense happens in pvp like elixir cast bar canceling it self 10% into the channel thinking you were still moving etc.

In order to remain in FF14 knowing how flawed the gameplay will be i had to take a whole lot of cope and focus on the MSQ knowing i cant take anything else seriously until they make their game run closer to real time reactions rather than filling in the gaps with predictions of what probably happened, and still punishing us if we didnt. That AOE you stopped an inch away from? Server predicted you kept running forward so you dead now.