They need to find a way to detect XIV Alexander and ban people

[Packetdancer]

Winning comment - "You can reduce your ping to 'zero'. While I'm at it, I'm going to look for a car mod to reduce my distance to work to zero. No mod changes the time it takes a packet to travel to instant. Sorry to tell you.

To be fair, they're not entirely wrong, albeit they phrased it wrong.

So far as I know (without digging too deeply into the game's netcode to verify this), the client wants an acknowledgment that the packet saying "I weaved this ability" got there before it lets you weave another ability. So if you have a 100ms ping time to the server, you can weave an ability and the client sends that to the server and it takes 100ms to get there, and the server goes "Okay, ability received" and it takes 100ms for that to get back, and the server goes "Cool, excellent, now you can weave another ability." So you'd have 200ms after one weave until you could get your double-weave in.

If you have a 500ms ping time, however, now you have to wait an entire second after one weave before the game will accept the second, which means people with a terrible ping are at a massive disadvantage when it comes to jobs that have a weave-heavy playstyle.

My understanding is that -- and I'm vastly oversimplifying here -- XIVAlexander doesn't actually reduce your ping time, it just tells the client "Yeah the packet got there" so that the client goes "Cool, you can weave your next ability now." Meaning someone with a 500ms ping could have XIVAlexander go "Tell the game the packet got there after 200ms" and instead of having to wait an entire second to weave, they can now do so after 200ms, just like the person who has the non-terrible connection. Meaning that now they can double-weave effectively, putting them on an equal footing. But so far as I can see from skimming the code for this thing, you could hypothetically tell it to reduce your perceived ping time to 0, meaning the instant the packet was sent it's treated as received and you can weave another ability.

However, when you move past a reasonable number of abilities sent in a given amount of time, one assumes the server goes "yeaaaah that's not right, we're gonna flag this" and you might (quite rightly) get banned.

So, like, someone in Argentina using XIVAlexander to reduce their perceived round-trip time to something akin to mine, to account for a terrible ping preventing weaving? I'm not gonna really begrudge them leveling the playing field. Someone using XIVAlexander to lower their perceived round-trip time to something where they can consistently triple-weave, that I feel is way less cool and deserves a ban.

Hence my "I have mixed feelings on that tool" position.

[Lunalepsy]

Stay tuned for more posts!

[BaconBits]

They need to find a way to detect your mom so they can tell her how proud she should be of you.

[Shougun]

To be fair, they're not entirely wrong, albeit they phrased it wrong.

So far as I know (without digging too deeply into the game's netcode to verify this), the client wants an acknowledgment that the packet saying "I weaved this ability" got there before it lets you weave another ability. So if you have a 100ms ping time to the server, you can weave an ability and the client sends that to the server and it takes 100ms to get there, and the server goes "Okay, ability received" and it takes 100ms for that to get back, and the server goes "Cool, excellent, now you can weave another ability." So you'd have 200ms after one weave until you could get your double-weave in.

If you have a 500ms ping time, however, now you have to wait an entire second after one weave before the game will accept the second, which means people with a terrible ping are at a massive disadvantage when it comes to jobs that have a weave-heavy playstyle.

My understanding is that -- and I'm vastly oversimplifying here -- XIVAlexander doesn't actually reduce your ping time, it just tells the client "Yeah the packet got there" so that the client goes "Cool, you can weave your next ability now." Meaning someone with a 500ms ping could have XIVAlexander go "Tell the game the packet got there after 200ms" and instead of having to wait an entire second to weave, they can now do so after 200ms, just like the person who has the non-terrible connection. Meaning that now they can double-weave effectively, putting them on an equal footing. But so far as I can see from skimming the code for this thing, you could hypothetically tell it to reduce your perceived ping time to 0, meaning the instant the packet was sent it's treated as received and you can weave another ability.

However, when you move past a reasonable number of abilities sent in a given amount of time, one assumes the server goes "yeaaaah that's not right, we're gonna flag this" and you might (quite rightly) get banned.

So, like, someone in Argentina using XIVAlexander to reduce their perceived round-trip time to something akin to mine, to account for a terrible ping preventing weaving? I'm not gonna really begrudge them leveling the playing field. Someone using XIVAlexander to lower their perceived round-trip time to something where they can consistently triple-weave, that I feel is way less cool and deserves a ban.

Hence my "I have mixed feelings on that tool" position.

Yeah the tool doesn't actually do anything to your 'actual' ping (doesn't magically make your internet better), which I agree is messing with the whole conversation lol.

What is changing if I can read right is a hard coded 500 ms delay that everyone has. When you have a bad ping on top of this, then it obviously puts you at a disadvantage than one who has good ping. So you can count 500ms as the 0 starting point in a situation without this tool and therefore ping is the ping.

Now though you introduce the ability to change that though and 0 is no longer simply 0. Of course laws of physics still apply :P, and it's still not magically making your internet better (but it does do stuff).

The developer says themselves:

Reduces the negative effects from playing with high latency (ping).

When you use an action, the client will apply 500ms animation lock, which will prevent you from using next action for a short amount of time. When the server processes the request, it will give your game client instructions about the supposed duration of animation lock (usually 600ms). Ideally, you should be able to use next action 600ms after the previous action, but the game client will let you use next action 600ms after server response, meaning that you're waiting for time taken for server response + animation lock time. Ideally, XivAlexander would simply get rid of time taken for server response part, but the server will rarely respond immediately even on sub-1ms ping, so you are given choices on how to make time taken for server response exclude your ping.

WARNING: Because of how it works, this addon is only a step away from flat out cheating. Changing temporal constants in code below the limit means you're effectively claiming that your latency is below zero, which is just impossible. Do NOT modify temporal constants in code, or you ARE cheating. You have been warned.

Example
[0.0s] Action A Request
[0.5s] Action B Request
[0.6s] Action A Response (1.0s lock)
[1.1s] Action B Response (1.0s lock)
By default, the client will let you input at 2.1s.
This addon will force the next input to be accepted at 2.0s.


Subtracts the round trip time measured from ICMP ping (or TCP_INFO_v0 if unavailable) from animation lock information response from the server.

When your ping fluctuates, it might take more than 500ms to receive a response from server, in which case, by game design, you are allowed to use next action regardless. Your client will receive two responses from the server, and only the latter animation lock information will take effect. Mode 2 and 3 will compensate for that by adding up animation lock information received.

Mode 2: Simulate RTT (75ms)
Simulates the environment where you would be receiving server response exactly 75ms after you use an action. From testing on sub-1ms connection to server, responses often took somewhere between 50ms and 100ms. Sometimes it takes less or more, but in any case, 75ms is the average.

Mode 3: Simulate Normalized RTT and Latency
Same with Mode 2, but will sample time taken for server response - round trip time measured from ICMP ping values, and use stabilized value in place of 75ms.

Which does read to me that even people with decent ping could use the tool for better responsiveness, but if you had king ping or truly truly god awful ping then there isn't too much the tool could do.

Not that I'm suggesting I think it's some great evil people with bad ping are getting to enjoy combat better (in general I think addons is a sign of strength of game, and often a symbol of stuff Devs themselves may better understand their player's desires), this tool allowing some a situation similar to those with great ping, but I do like the conversation not to be "it does nothing and has no impact on the game bro, don't complain about it" or "it literally bends warp space time to make you a better more fit human player" .

[Packetdancer]

The developer says themselves:

And with better detail than I did in my hasty post, so thank you for tossing that one in there.

[Mezzoforte]

What the title says. I just found out that it literally tells you things in the game that you shouldn't know prior. For example. WHen you do the Gold Saucer Mini Cactpot, it will LIGHT UP the ones you want to click for the highest reward... That's absurd.

Further. If any contest comes back like the Firmament, it will literally tell these people what to use each step to get the best quality. It can also adjust their ping to be near zero, allowing them to hit skills/nodes much faster than others. This doesn't need to be allowed and there has got to be a way to detect it. Clearly it's reading something in the game files to allow it to tell you what buttons on the mini cact you wanna click. Which is against ToS.

The minicacpot solution is a 3rd grade tier solution. If you are always solving for the two highest rewards you do it the same way, every single time, with every single ticket. The mod doesn't do anything you shouldnt already be doing yourself. So its not really relevant. Adjusting peoples ping isn't an issue as that is more helpful than bad. Some people have bad ping and if it helps them more power to them. People already use crafting macros and flowcharts to tell you how exactly to craft everything optimally. The mod isn't doing anything that you aren't already doing unless you intentionally do stuff suboptimally then that is your choice. I don't use any mods myself and I think it is fine. I don't understand why it even matters? Yoshi has said time and time again its ok to use third party shit if you dont use it to harass people, you dont talk about it constantly, and you arent using it to make the game look worse to media like screenshots, nudes of lalas, etc. If you want a solution to what you view is a big problem send Yoshi a personal email.

[Shougun]

The minicacpot solution is a 3rd grade tier solution. If you are always solving for the two highest rewards you do it the same way, every single time, with every single ticket. The mod doesn't do anything you shouldnt already be doing yourself. So its not really relevant. Adjusting peoples ping isn't an issue as that is more helpful than bad. Some people have bad ping and if it helps them more power to them. People already use crafting macros and flowcharts to tell you how exactly to craft everything optimally. The mod isn't doing anything that you aren't already doing unless you intentionally do stuff suboptimally then that is your choice. I don't use any mods myself and I think it is fine. I don't understand why it even matters? Yoshi has said time and time again its ok to use third party shit if you dont use it to harass people, you dont talk about it constantly, and you arent using it to make the game look worse to media like screenshots, nudes of lalas, etc. If you want a solution to what you view is a big problem send Yoshi a personal email.

Yoshida plz become my penpal :3


Also just on the last bit, technically, as far as I can remember, he never said using third party tools (those particularly that read game memory) are okay.

In fact I clearly remember him saying those are not allowed, some are worse than others but they can't sit and pick and choose so none of them are okay. However they're not reading your memory, nor performing witch-hunts on the more benign systems, so harassing people is a surefire way to get in trouble vs not.

So it's more "wont ask, don't tell" than he says it's okay. If you say here you use xivalexander I'm assuming someone could report you and you could be punished (I mean this has happened for other things in game, in situations that weren't harassment). Particularly they use their own systems for this, as it seems if you did a youtube hunt on people it wont have much impact if any so long as there isn't harassment they can't verify on their own end. So going on twitter to say you use it wouldn't really do much unless you harassed someone, but saying you used it inside the game would be an issue.

Just want to make sure people aren't going around saying Yoshida greenlit third party tools so long as you don't say their name three times lol.

[Packetdancer]

Just want to make sure people aren't going around saying Yoshida greenlit third party tools so long as you don't say their name three times lol.

There are a handful of exceptions; they did actually more-or-less greenlight ReShade (and its derivatives). This forum's search engine is godawful, so I don't want to go try to find the thread right now, but there's a thread here in the English forums from several years back where they detailed their position; I've linked it before, so presumably it can be located again if anyone's really determined.

Admittedly, it wasn't so much "we give this our blessing" as they said that while technically it would be against a strict reading of the TOS they would never enforce it, since ReShade provides no gameplay advantage -- save maybe "increasing contrast to help colorblind folks see mechanics" -- and generally just gets used artistically, and so to feel free to enjoy it.

And they actually gave Nvidia's ReShade fork (Freestyle) the blessing officially; if you go to the Freestyle page on Nvidia's site, you'll see FFXIV listed in the officially-supported games for Freestyle. So if you have Nvidia Experience installed, you've already got ReShade -- or Freestyle, anyway -- active while running FFXIV right now; just hit Alt+F2 to bring it up in-game!

[Shougun]

There are a handful of exceptions; they did actually more-or-less greenlight ReShade (and its derivatives). This forum's search engine is godawful, so I don't want to go try to find the thread right now, but there's a thread here in the English forums from several years back where they detailed their position; I've linked it before, so presumably it can be located again if anyone's really determined.

Admittedly, it wasn't so much "we give this our blessing" as they said that while technically it would be against a strict reading of the TOS they would never enforce it, since ReShade provides no gameplay advantage -- save maybe "increasing contrast to help colorblind folks see mechanics" -- and generally just gets used artistically, and so to feel free to enjoy it.

And they actually gave Nvidia's ReShade fork (Freestyle) the blessing officially; if you go to the Freestyle page on Nvidia's site, you'll see FFXIV listed in the officially-supported games for Freestyle. So if you have Nvidia Experience installed, you've already got ReShade -- or Freestyle, anyway -- active while running FFXIV right now; just hit Alt+F2 to bring it up in-game!

That's true, though in context of this thread specifically we would both agree it's not the case aye?

I mean if we were going for most accurate I probably should have mentioned reshade, I do recall they said that 'one' is fine lol, but certainly in case of this thread saying you use any one of the tools mentioned is grounds for punishment.

[Koldan]

How do you know they set their parameters to match yours? How do you know they dont reduce it to negative to tripple weave (you can see plenty of parses where DRG tripple weave jumps)? It all creates unfair environment. All tools that improve game client and game functions do that, expecially for console players. All of that should be disabled on dev lvl or made baseline simple as that (hide game packets or something, its not our job to figure it out)