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

Modern MMORPG don't use predicative rollback or anything fancy. All it does is ask the client to make decision where it'd know best (like where the player is). Client reports something like: "Player was at position XYZ and totally dodged that", and server acknowledges it. If you somehow hacked your client to always say 'totally dodged that', it still reports back the position XYZ. The server, which also knows the radius of all AEs, is going to realize this position is suspicious and make note of that. If you do that too many times you'll likely get banned for hacking as the server can conclude you didn't actually move. But the server isn't going to try to catch let alone correct your cheating behavior on the fly.

Originally Posted by Sunarie

Snip

My problem is the other way around. The server is not sending positional data to my client - at all. Either that or location data packets get lost on their way to my client for very specific targets. For example, the boss may not be in the correct location, but all the adds will be. If only there was a way to ensure location data finds it's way to the location of my client... :P

You've got my support OP +1

I don't experience this as often as my boyfriend but I know it's there.

I think bare minimum they should re time the aoe hit detection to line up with when the actual hit goes off in the animation, and not the start of the animation. it was one of the odder things to adjust to. the fact that even if you stand there and eat an aoe, it can take a good second for the attack animation to actually trigger the strike, it just amplifies the wtf I was no where near that problem and makes the whole thing feel clunker then it should.

Originally Posted by Tolka

I think bare minimum they should re time the aoe hit detection to line up with when the actual hit goes off in the animation, and not the start of the animation. it was one of the odder things to adjust to. the fact that even if you stand there and eat an aoe, it can take a good second for the attack animation to actually trigger the strike, it just amplifies the wtf I was no where near that problem and makes the whole thing feel clunker then it should.

This. If you're going to project with animation, and calculate damage after animation - the casting bar should be in-sync with this. Other wise the system is disjointed and clunky by design.

And it ain't no lie
Baby Bye Bye Bye























Yes I just referenced NSYNC.

^ This cannot be allowed to fall into obscurity.

I have this happen all the time. Not only is it very frustrating, but it is even more frustrating to been constantly told its my fault, and l2p by people who don't experience it.

The lag actually double dips. An ability like WotL almost certainly is just cast at your character's current position, but if you've a running start you'll notice the AE is placed considerably far away from where you're if you started out moving at full speed. So this means your client is receiving the information late. All abilities basically have 2 times the lag factor subtracted from the time you're supposed to have, though the first half (the start) can be dealt with by memorization. That is, if you're running the whole time then you're already on your way getting out of the AE even though you can't actually see it.

Just bumping this back to the first page to make sure it still gets a visual, and hopefully a response someday. As I've said before, I would at least like to know whether it's something they plan on addressing or if they're treating it like all the players just need to get better.

+1 for this issue. On really good days I'll have 200ms and everything will be fine, but most nights during peak hour I'll be between 300-350ms, and I will get hit by absolutely everything. Titan is simply out of the question for me during peak hours, which is really disappointing as I'm trying to help others in my FC get their relics.

Would love if this issue is investigated even if there is no simple solution.