The server tick problem in O7S is an issue.

It really sucks when a perfectly good O7S run is ruined by SE's horrid servers.

The abandonment mechanic is a nonfactor to the fight, but lousy servers can still wipe a group because of it.

Here's a Reddit thread explaining the issue:

https://www.reddit.com/r/ffxiv/comme...7z&sh=67c4e9df

I have a feeling that this doesn't really affect JP players. I'm just glad that our AU raid member isn't a melee, or else we would never pass it.

I'd really like to see this fixed, but I'd settle for a "We'll never implement a mechanic like that again. It doesn't require much thought or skill to pass, so it really should just be done away with. There are ways to make virus phase "difficult" without having the BS that is tethers.

Thank you.

My group actually had this happen in our first clear: https://youtu.be/5yH-8uz4e7M?t=313

It happens mostly with our DRK, it is hard to see cause of my camera angle but we stood right next to each other, but when we got pushed back together he immediately got hysteria and then caused me to get hysteria even tho we had been right next to each other. Luckily we didn't run into the walls. It seems like it was because I was pushed back quicker than he was due to my ping?

If our WAR is in middle for virus then we just do the same thing and both get knocked back next to each other and it always works and never triggers abandonment. So yeah it seems really finicky.

Have you also found the Damage from the DoT (Prey marker) is also afflicted by this? I feel like usually it's fine, but every now and again it will seem to apply the damage at inconsistent times (I think the last tick of dmg usually applies at 3 seconds, but here and there it might apply at 1 second)?

Quote:

---

Originally Posted by Niqote

Have you also found the Damage from the DoT (Prey marker) is also afflicted by this? I feel like usually it's fine, but every now and again it will seem to apply the damage at inconsistent times (I think the last tick of dmg usually applies at 3 seconds, but here and there it might apply at 1 second)?

---

Yeah...the prey DoT also is based on server ticks so sometimes like the prey marker gets hit by the missile and the DoT immediately ticks bringing them down to very low HP due to both of the damage hitting them at the same time basically. While other times there is some time between the damage. It would be due to simply where the server ticks were when you initiated the boss I think and also which of the two scripted patterns the boss ends up doing.

Best way to deal would be to shield the prey target for the initial hit I guess or time a direct heal to land just as the prey target gets hit by the missile. Also the pattern he uses for Prey then Shockwave can be a real pain in the butt....since the shockwave damage and prey DoT I swear I've seen them both hit together and cause the prey target to get one shot if no shields or not full HP. Just what I've observed...I am unsure if there are other factors or if sometimes the prey target maybe made a mistake and hit the wall.

I lost the account how many missiles I eat.

Yes, i never thought about creating a thread on forums about this but...

The problem is real and something really should be done =/
We had so many maintenance this 4.2 and none of it fixed that.

I'm really fortunate neither of my groups encountered this x-x

If they're going to have mechanics like this, there needs to be leeway if only for the network.

Quote:

---

Originally Posted by Curcio

There are ways to make virus phase "difficult" without having the BS that is tethers.

Thank you.

---

The tethers part is fine enough, the only real problem from this is the abandonment. Ditch that and things would be a lot better.

So if i read it right,you must do o7s with people who have the same time line or you're fucked ?

Quote:

---

Originally Posted by Gleipni

So if i read it right,you must do o7s with people who have the same time line or you're fucked ?

---

Something like that. If one melee, tank, or healer has more latency than another, they will be knocked back at "separate" times; just long enough for abandonment to trigger Hysteria. I can respect the idea behind the mechanic, but the server's latency should have been considered first and foremost.

They should just increase the amount of time it takes for Abandonment to trigger by a second or two.

I've also gotten killed by latency several times due to a delayed tether.

Oh wow.. I didn't know this was a thing for this tier..
I am a raider but just PF'd last tier, and haven't been motivated to try this tier..

However as an Aussie who plays melee primarily, I am absolutely glad I didn't bother as this just sounds rubbish.. I would literally never be able to beat that mechanic..

Quote:

---

Originally Posted by Gleipni

So if i read it right,you must do o7s with people who have the same time line or you're fucked ?

---

One time it "glitched" for us I ended up passing rot to the other melee just by chance.

Of course that's not something to rely on; it was just funny when it happened.

How is this game so popular and yet the servers are abysmal?! I know it didn't used to be this bad, but wow it's bad for this expansion. Maybe if we pray hard enough, Bahamut will come back? :<

Tested fine in Japan, how dare you imply SE should care about their western pigdog audience and give them good servers.

Another issue is the Saintly Beam in Phantom Train. I could be out of that AoE for around a second or two, but still get hit because reasons. The interesting part about this is that it's not just me who is getting this issue (I'm Australian playing on an American server), but other American friends are as well.

Getting some Titan HM and ADS flashbacks.

Quote:

---

Originally Posted by Fourbestintoner

Tested fine in Japan, how dare you imply SE should care about their western pigdog audience and give them good servers.

---

I'll have you know I'm only half pigdog, thank you.

Cleared with no issues. I'm sorry this is happening to people D: Good luck

Quote:

---

Originally Posted by Nestama

Another issue is the Saintly Beam in Phantom Train. I could be out of that AoE for around a second or two, but still get hit because reasons. The interesting part about this is that it's not just me who is getting this issue (I'm Australian playing on an American server), but other American friends are as well.

Getting some Titan HM and ADS flashbacks.

---

See, it's weird because the way that particular AoE's damage ticks is the damage is registered as "gone out" before the animation finishes. If you're not hightailing it out of that aoe the second it lands, you'll probably get caught in it.

Oh, myself and my friends drop everything and make a mad dash out of the light the SECOND they're done 'locating' their target (once they flash and then have the beam of light shine down three seconds later). It's just that sometimes we still take damage despite being out of the lights for roughly one-two seconds (long before the beam shines down).

Quote:

---

Originally Posted by Nestama

Oh, myself and my friends drop everything and make a mad dash out of the light the SECOND they're done 'locating' their target (once they flash and then have the beam of light shine down three seconds later). It's just that sometimes we still take damage despite being out of the lights for roughly one-two seconds (long before the beam shines down).

---

Might be a weird technical problem related to the mechanic since it is a tracking circle that homes in on the player. I've experienced the same problem. Maybe latency causes the client to draw the circle slightly off so it isn't painted properly on the client and on the server it is actually slightly over than where the client says it is. Maybe if you dodge just enough to be out of it like you can for the rest of the circles you are still standing in it on the server.

Don't know for sure but it could be that or they made it more unforgiving since they tuned it based on the player being constantly in motion to dodge it (basically always being slightly ahead of the light) or something which is weird because people wouldn't bother doing that if they want more uptime.

Let's not forget those retarded bomb mechanics lol our healer had to run through his three times before it disarmed like come on SE do better

Quote:

---

Originally Posted by Aomine1992

Let's not forget those retarded bomb mechanics lol our healer had to run through his three times before it disarmed like come on SE do better

---

With those, you have to stand on the wire. The mechanic is you "cutting" the wire with your feet, and when you run over it you run the risk of server not registering you touching the wire.

Quote:

---

Originally Posted by Dualgunner

With those, you have to stand on the wire. The mechanic is you "cutting" the wire with your feet, and when you run over it you run the risk of server not registering you touching the wire.

---

Ah, I haven't had an issue with this one personally and my ping is between 190-240, I just run through it.
Saintly beam (much like the original Titan Ex landslide hahah) does require you to move your tail asap or you are going to be hit without mercy.

I am glad that someone else could confirm that people with prey can up and die almost as if they were one shot, I thought I was going a tad crazy when I saw it happen.
Like a few of the fights in this game, OS7 is certainly not undo-able for we with higher pings; it just takes a higher degree of accuracy from us >_<

Tried to clear this weeks o7s with a spanish pug grp today and this just happened to us too - 4 times in a row, and some more times in between! We wiped sometimes, and sometimes someone was lucky enough to pass the rot before it exploded, but mellee still died in most cases.
One time we even took the time to stack exactly on each other, but still got feared. Looked kind of like this, except we ran into the wall:
https://gfycat.com/ThoroughDearAustralianshelduck

This mechanic is so damn broken and needs to be changed asap! I hate this fight just because of this mess.

Dear SE, not everyone has a 1 ms latency like you have in Japan. FIX THIS BROKEN MECHANIC PLS!

I don't know if they can fix it or if they even want to fix this, but here's a push vor visibility!
New patch out, but issue was not addressed.

All they really need to do is replace Abandonment with something else.

Extreme Caution, Forced March and Cursed Voice come to mind.

Just make it a stun like Spellblade: Holy in O3S, and lock everyone in place until the knockbacks/pulls get resolved! Add a stack marker to the abandonment players that indicate it must be shared by at least one other player (the person getting knocked back with them). Make the stack marker hit a bit after the knockback occurs to make sure people's pings have time to adjust.

SIMPLE FIX!

Or just extend the time (that you need to be apart to be feared) for 1-2 more seconds.

We just started passing before the knockback. It's dumb because the mechanic is clearly designed to allow for passing after it but you're screwed if the server tick gets you.

I get hit by that ridiculous NTT lag that happens every night. And when it hits me during raid. I fear for the virus phase. I don't get pushed back if the client doesn't communicate with the server and then my partner and I gets Hysteria because of it. Completely our of my control.

The servers and the location they are in are a total mess and a joke when it comes to quality.