hopefully in the future SE stops releasing glorified latency tests and labeling them

[Tupsi]

And the problem with the community is that when you bring up legitimate points of criticism

Indeed - But you also forget the flip side:

The ones who don't have issues but the said person stating it as fact that there are issues for everyone/the game itself. Why brush them aside? If it's a "legitimate point of criticism" you have to take into consideration that not everyone is having those issues.

[Jinko]

Ahh its this old chestnut. (it's starting to look mouldy)

Something needs to be done, it should be, it won't though.

[Estellios]

The problem is the tanks I'm with too often Stun other things and resistance gets built up. Same applies to Copperbell last boss. As for Bards and Monks, I rarely get paired with them in Haukke. It's usually a Summoner or Black Mage, and the Bards either Silence the "wrong" abilities or just don't try at all while the Monks forget they can silence to begin with.

It's not that we forget. It's that we have to be in a specific stance when we usually have to cycle through stances quickly or else greased lightning drops off and our DPS goes to crap while we build it up again.

[Sunarie]

At this point in time, if you're having latency issues and they are frustrating you enough... you really should move on :/ The only way SE is going to fix the root cause of them would be if it was more profitable to do so, which isn't going to happen unless the issue actually causes people to quit. Sounds harsh and all, but it's true. I've done the whole fighting to get it fixed thing, and we did get an increased positional check time.. but fixing the root cause would cost a ton of money, and take probably a year to actually re-code and implement. It's just not likely to happen.

[Estellios]

At this point in time, if you're having latency issues and they are frustrating you enough... you really should move on :/ The only way SE is going to fix the root cause of them would be if it was more profitable to do so, which isn't going to happen unless the issue actually causes people to quit.

Really the best we can do is convince them to stop making fights with insta-kill mechanics on extremely strict timings. Weight of the Land was already super wonky for a ton of people so I can't really understand why they decided to make it even worse in the EX version by a) requiring you to stack up so that it is more likely to be an insta-kill move which led to b) You can't memorize the pattern and pre-move to avoid it like many people needed to for HM as you will likely get several people killed.

[Heroicbandit]

It's not just boss encounters. Have any of you ever noticed a buff or debuff counter actually count up? I see it all the time where my client will say I have 9 seconds left on say for example, Vengeance, and then when checked against the server, it pops back up to 10 seconds.

My latency is decent but if I haven't started moving within the first 25% of the cast bar, I'm eating whatever it was. Of course, I have also experienced instances where I'm still very clearly in a plume because I didn't react fast enough on my end and it still passes the server check so I avoid it.

The issues vary from person to person. Some have no issue at all. Others can't do Titan as a result. The inconsistency is what's most troubling.

[Jinko]

At this point in time, if you're having latency issues and they are frustrating you enough... you really should move on :/ The only way SE is going to fix the root cause of them would be if it was more profitable to do so, which isn't going to happen unless the issue actually causes people to quit. Sounds harsh and all, but it's true. I've done the whole fighting to get it fixed thing, and we did get an increased positional check time.. but fixing the root cause would cost a ton of money, and take probably a year to actually re-code and implement. It's just not likely to happen.

I don't think client side checks would take a great deal of coding or cost, the problem is it "could" open up the game to cheating which is probably why they won't consider it.

[MANTASTIC]

"Don't stand in stuff" as a mechanic is so new and interesting, and flawlessly executed in 14, am I right? The case of Titan HM/EX is used repeatedly to illustrate how fucking awful position poling is, but an equal annoyance I personally have is how fucking boring the strategy is. I won't say its easy to execute, but most of the difficulty is artificial. The tension for me comes from wondering whether or not that AOE I moved out of on the ground will still hit me. In a perfect world where if you're not standing in Titan's piss meant you absolutely wont be hit by piss, you'd be left with an extremely boring, unoriginal design that has been around since at least the "Don't stand in the fire" days of WoW, etc.

Until SE finally un-fucks the hit detection from telegraphs, they should probably think up some more interesting boss mechanics. Or, brace yourselves, think up more interesting boss mechanics AND implement actually good hit detection. Crazy talk, I know.

[Tupsi]

The inconsistency is what's most troubling.

It's because we know the issue lies within the route inbetween you (player) and the game's servers - Something SE actually can't fix as it's not their company having the issue. Whether people want to admit it or not, the fact XI doesn't have constant time outs, disconnects and unplayable lag (and yes if you lag in XI everything around you freezes just like in XIV) means the route where you go to XI isn't having issues.

We know the problem lies mainly with Tata Communications and Level3.net. Some even report Sky having issues. SE doesn't own those companies.

[Jinko]

"Don't stand in stuff" as a mechanic is so new and interesting, and flawlessly executed in 14, am I right? The case of Titan HM/EX is used repeatedly to illustrate how fucking awful position poling is, but an equal annoyance I personally have is how fucking boring the strategy is. I won't say its easy to execute, but most of the difficulty is artificial. The tension for me comes from wondering whether or not that AOE I moved out of on the ground will still hit me. In a perfect world where if you're not standing in Titan's piss meant you absolutely wont be hit by piss, you'd be left with an extremely boring, unoriginal design that has been around since at least the "Don't stand in the fire" days of WoW, etc.

Until SE finally un-fucks the hit detection from telegraphs, they should probably think up some more interesting boss mechanics. Or, brace yourselves, think up more interesting boss mechanics AND implement actually good hit detection. Crazy talk, I know.

You make a good point, the Teratotaur boss in Temple of Qarn is a much better kind of mechanic for this game considering its limitations, in fact that whole dungeon has some really cool mechanics which could be applied to more end game content.

It's because we know the issue lies within the route inbetween you (player) and the game's servers - Something SE actually can't fix as it's not their company having the issue. Whether people want to admit it or not, the fact XI doesn't have constant time outs, disconnects and unplayable lag (and yes if you lag in XI everything around you freezes just like in XIV) means the route where you go to XI isn't having issues.

We know the problem lies mainly with Tata Communications and Level3.net. Some even report Sky having issues. SE doesn't own those companies.

Thing is I can see massive latency issues in FFXIV and have next to none in WoW, yes I am in Europe so there is that .. but its pretty obvious FFXIV's net code is not as robust as other MMOs on the market.

Of course it doesn't help that they expect their EU Players to connect to a server half way across the world especially with some of these boss fights.

I am interested to see what they have done with the Leviathan fight to see if they even considered this whilst making it.