Thread: .3 Second Positional Update Delay (Requesting Dev Response)

I wish we as gamers and customers would stop complaining about the possibility of fixing this and whether or not it is an issue. It is obviously an issue that MANY of us experience and have hinder our gaming experience. It is very much possible to have a more responsive positional check system as it is displayed in working order on lesser funded games. I think SE isn't willing to respond to this as it will probably take a lot of restructuring of their code, which is another step backward. I hope it isn't being responded to as it is something they are being cautious about, and not that they are just ignoring it and hoping it goes away.

It wont.

What bothers me the most is that Square comes off as actually thinking that saying absolutely nothing and pretending that issues don't exist is a viable and professional method of handling customer complaints. They 'may' read everything. But the simple fact that they never respond to these issues creates a logical and clear sense that we as customers are ignored and low priority.

Agreed, the way they managed everything is very, very strange. Almost everything in this game is linked with the server time which is odd, and frustrating. DoTs, HoTs, enemy cast times, AoE's, position updating. All of these things need to happen on our end to minimize the impact of latency issues.

Originally Posted by TheRac25

i can easily calculate a box that you should not be able get out of by the next pos update you send me

Yeah, that's the sanity check. Problem is you don't have to move very far at all to stay within sanity check bounds. If your box is less than 30y, then the moment you get hit by Landslide you'd not only die but you'd get flagged as a teleporter, because you sure moved very far suddenly! There are also player abilities that move that kind of distance (BLM teleport to ally, for example). Also, this routine would have to be updated each time there are new abilities that faciliate movement, and every enemy that has an ability to move you has to be accounted for. Teleport is usually caught because you've to temper with game data to send the fake coordinates, but catching it in real time, let alone correcting it, is very difficult.

Originally Posted by Knosis

I think SE isn't willing to respond to this as it will probably take a lot of restructuring of their code, which is another step backward. I hope it isn't being responded to as it is something they are being cautious about, and not that they are just ignoring it and hoping it goes away. It wont.

The problem apears to require a complete rewrite of the server software, SE is cheap and lazy, you do the math on when it will get done.

The decision to do most things server-based as opposed to client based is not laziness or cost. Honestly it's probably more expensive overall to have the server do these things instead of just letting the client handle it. The problem is that SE apparently think this model totally makes sense despite them being the only company that runs such a model, and that's why this problem is serious. It's not that they don't want to or lack the resources to fix the problem. They clearly think the game is perfectly as is. This is a design issue. It'd be like how SWG originally by design does not allow most players to ever become a Jedi. The devs aren't getting extra money out of this. They simply believe that is the way the game ought to be.

Originally Posted by TheRac25

i know how fast landlside moves wich is something i allready knew thus has no impact try again
never mind the fact that i told you where you were gonna be after landslide and this has nothing to do with the client sending me position update

You're basically proposing a function like:
Flag player if he change of position of more than X
Except when it's the result of Landslide
OR Great Tornado
OR Teleport to ally
OR (start listing the hundreds of abilities that can move you a significant distance in the game)

Pretty much every game does check to see any unusual amount of change in position, but they can't take action solely based on that because otherwise you'd end up flagging people as cheaters for clicking on a teleporter that you forgot to add to your 'except' clause.

Originally Posted by Astarica

You're basically proposing a function like:
Flag player if he change of position of more than X
Except when it's the result of Landslide
OR Great Tornado
OR Teleport to ally
OR (start listing the hundreds of abilities that can move you a significant distance in the game)

Pretty much every game does check to see any unusual amount of change in position, but they can't take action solely based on that because otherwise you'd end up flagging people as cheaters for clicking on a teleporter that you forgot to add to your 'except' clause.

There are ways to intelligently exclude things while using minimal processing power. For example in titan I'm pretty sure there is no frog to lick suck me to it, so knowing that cannot possibly happen it doesn't have to be checked. Binary searches are prime examples of intelligent exclusion.