Alphascape as a whole

As the content slowly or acutely for some ramps up, there is an inherent problem with doing this content and content that is going to be hard like it or even harder. And before someone on here, and there will be plenty state "git gud" or something like that. Please read the whole post. As I don't care that the content is getting harder but it is something that SE's development team should look at is how much they have ramp up content.

So while there are some moments in Alphascape v1.0 and v2.0 that are fine. When getting to Alphascape 3.0, is where I start having my reservations on the content as a whole. The reason isn't for just me but it is for everyone in the community. Running into 3.0 and having perhaps a second and a half or so or less for telegraphs...I don't necessarily worry about but the problem isn't the mechanic as much as it is the server stability. Ramp up the difficulty...fine but there needs to be reliable server stability for all the players that are running the content. I saw people lagging bad there that these 1 1/2 second or less mechanics will ALWAYS kill those people because they can't react that fast as the lag is an issue.

The backbone that SE uses for some of the North America servers are somewhat stable but when the higher end content is address...it's not stable enough to really have those types of mechanics in it. If the servers aren't lagging and connections are 100% efficient or even 99% efficient, I am all but certain it's not a problem. However, there are multiple people that are suffering through and flustered that there is real lag happening and unable to properly address the mechanics as a whole because what they see isn't happening as they are dropping data packets...not just from their system but the datacenter isn't getting them either and poof, they are low on HP or dead the next moment.

So the temporary solution I would mention is to possibly allow these mechanics to be a dash more forgiving until you can address the backbone issues and datacenters to make sure they are stable. And while people are reading this, there will be some that will ask. But have you ran new lines or had someone out...used a new router or modem/connection...or any other possible explanation to make sure that the connection is solid from the house. And I will say that I have done that all. For 1 1/2 weeks I have talked with and worked with technicians to make sure my lines are fine to spending money and even port forward...vpn or whatever situation that has been suggested and it's NOT my system, or my connection. All I ask is for a small respite in allowing perhaps some of the virtually instant mechanics be given a little more lag time as there are others that are in my situation. Once the SE FF14 servers are more stable with handing the people on them, then ramp the difficulty back up to how you had it.

It isn't really a hardware or connection issue.
The instance servers are just heavily used in the first days of a major patch bc a lot of people return and everyone and their mothers are doing the new raids/dungeons/primal. It will somewhat settle when content gets older and the rush is over.


Besides people still have to get used to the mechanics and learn the rotations. Once they are familiar with the content there is no problem even when there are lags. Just give it some time, it's just day 3.

Quote:

---

Originally Posted by AmeliaVerves

It isn't really a hardware or connection issue.
The instance servers are just heavily used in the first days of a major patch bc a lot of people return and everyone and their mothers are doing the new raids/dungeons/primal.

---

This.

To add onto this, the only noticeable problem I see is in o12 with serious frame drop. But I haven't experienced any lag outside of Savage in o10s. There are times where GCD's don't go off or the animation is suspended.

"Fast" telegraph mechanics are meant to be handled differently from "slow" telegraph ones. The fast ones want you to pay attention to what the boss is doing since the safe zones will be decided before the telegraph even appears.

Once the cast bar appears, you should start moving to the safe spot. Ideally, you'll be there before the telegraph even shows up. If you wait until you see the red on the floor, you're probably going to get nailed, lag or no.

That said, yes, sometimes there's enough lag that nothing is going to save you from needing a raise.

Quote:

---

Originally Posted by Ryphen

"Fast" telegraph mechanics are meant to be handled differently from "slow" telegraph ones. The fast ones want you to pay attention to what the boss is doing since the safe zones will be decided before the telegraph even appears.

Once the cast bar appears, you should start moving to the safe spot. Ideally, you'll be there before the telegraph even shows up. If you wait until you see the red on the floor, you're probably going to get nailed, lag or no.

That said, yes, sometimes there's enough lag that nothing is going to save you from needing a raise.

---

Yeah, the fast ones aren't really for 'see the aoe, move out of it' moves. I mean if you're right on the edge you MIGHT escape it but probably not. They're more markers to show you the pattern so that you know where the move is hitting. Take everyone's favorite example, starboard and larboard cannons. The aoe is there to show you the blast zone so that you can learn the pattern and avoid it next time.

There are no "virtually instant mechanics". Everything has a telegraph and/or timing associated with it. There are certainly legitimate occasions where Lag plays a role in whether you complete a mechanic or not, but for the vast majority of players it's nothing more than crutch to escape criticism. A few years ago when Lag was actually bad for everyone, it was still possible to compensate by anticipating what was coming up. Haven't had to deal with that sort of lag since then so I'm not sure if it's still the case, but it was rarely a factor that couldn't be overcome by planning.