Titan issues that need addressing.

[Gyson]

It's fairly simple. The cast bar and the telegraph do not happen instantaneously in the code by logical reckoning. When the cast starts then it triggers the telegraph. This means that the servers send at least two bits of information to the players computer at slightly different times. The route that information takes, along with any packet loss along the way, contribute to the issue.

And that is where we disagree. In reality neither of us can confirm which is correct, but why do you think the server would send two bits of information (the trigger for the castbar and telegraph) separately to the player's client rather than as one single event? To do otherwise would be just asking for problems.

[DragonFlyy]

And that is where we disagree. In reality neither of us can confirm which is correct, but why do you think the server would send two bits of information (the trigger for the castbar and telegraph) separately to the player's client rather than as one single event? To do otherwise would be just asking for problems.

It's more than 2 actually. First Titan starts to cast (server side). Then the game asks the clients (all 8) for a position update. Clients send that back to the server, server calculates WoL locations and transmits to all 8 computers. If any of this was done client side, we could easily capture that event and spoof the server into thinking we are not standing there, thus not needing to move at all. Personally, I have not been hit by WoL since I moved to a closer server (my 1.0 character was placed on a Japan server and they offered free xfers back then.)

[TheRogueX]

And that is where we disagree. In reality neither of us can confirm which is correct,

Well, technically speaking, either one of you could set up a packet sniffer and then analyze all the data to be 100% certain, soooo...