Buttons not reacting in PvP and ranking up

at the end of the day its up to you how much you trust a game company and if you really think they are honest or good.

For example, the starting gear for animal people is thong bikinis, they allow people to buy dozens of mansions on multiple accounts and turn them into erotic clubs and casinos because if they skip a single monthly sub its all gone. They also allow house owners to avoid millions in market transaction taxes and break the trade limit with mannequins. People with dozens of market alts blatantly using third party programs to undercut you by a single gil the second you post an item, with a dozen different accounts. For years the gold selling bots standing under the map 24 hours a day with the exact same website spammed, in every main city on every server of every data center, same with the underground bots farming level 10 materials in every starting zone. If it brings in more money through subs they aint quick to stop it. Lets not forget the forums for FF14 where you can seek an in-game marriage partner where lots of the users are just seeking kink stuff. By my standards theres a lot of corruption, so when i watch 50 people use forbidden third party tools for yojimbo event, bean race, pvp, or even reducing server input delay, its not surprising they turn a blind eye there too. Just go look at the win trading forums.

I wish they would revisit improved hit detection. It really ruined the gameplay feel for a lot of classes and I think it's made everything feel like it has huge input delay and a feeling of unresponsiveness (this is after a year plus of getting used to it)

If they do, I hope it's not in the form of totally walking it back. I'd really like to keep being able to reactively parry skills vs. pure guesswork. It also works the other way around, with being able to preload fresh out of guard bombardment. For the jobs right now that concern me, I'm not having too many hiccups.

It just has trouble working out like it could since skill animations are built around spectacle and definitely not with this change they implemented much later, as evidenced by further damage-timing tweaks that followed. Once you learn those timings it's fine regardless though, it's sort of like picking up an alpha test stage fighting game, or rather looking at the frame data. :)

They just need to make sure that stuff like MCH LB displays with "Some" graphics setting on now.~ (<sigh>)

I play on PS5 and this also happens with me. I have to mash that guard button like it owes me money and then of course it pops on a second too late. Same with purify. No no, we have to wait until bard does his little song and dance animation (sigh)

Quote:

---

Originally Posted by Hazelx3

Thanks for trying, could you possible try with a class like Viper or Gnb where you have to use your buttons quickly?

---

I've played these jobs and occasionally felt as though my inputs weren't registering even after pressing a button. However, after reviewing my recordings, I found no cases clearly attributable to a system-side issue. The cause was most often the target's position. The remaining cases were due to animation lock duration and the fact that Limit Break cannot be queued. There were also cases where I was KO'd after pressing a button before the action went off, but I believe this was due to animation lock rather than missed input. As noted in the thread below, animation lock is ping-dependent. This behaviour has not been changed and appears to be intended, so it is unlikely to be addressed in the future.
https://forum.square-enix.com/ffxiv/...onse-is-ignore

I normally use macros for attacking actions and Recuperate, and since macros cannot be queued, I tend to mash the button. But on these jobs I used macros only for targeting and XHB switching, leaving PvP actions as non-macros. One interesting thing I noticed is that I had occasionally been cancelling one macro by triggering another immediately afterwards unintentionally. For example, if I took damage immediately after pressing an attack button and then mashed Recuperate, the attack would still execute when using the non-macro action. With the macro version, however, the attack would fail and Recuperate would activate instead. I'm aware that macros have the disadvantage of requiring repeated presses, but if non-macro actions also require button mashing, that disadvantage is effectively diminished.