This is an ongoing issue that they're trying to resolve as they come across these situations. Basically, we believe the client is programmed to expect some kind of ACK from the server that it's not getting, and when that happens, the client sits there perpetually waiting for an ACK that will never come.
Examples of where it needs an ACK are when you loot. As you try to pick up each item in the loot window, the client expects the server to send a packet back stating that either you are clear to pick up the item, or for some reason (duplicate lore, or otherwise) you aren't. If that ACK/NAK never came, then you might be able to close the loot window and start running around again, but the client will be hung on waiting for that ACK and not pay attention to any of your other actions until it gets it. That's not to say that looting is the cause of the issue; I'm just giving one example of the many places the client needs an ACK/NAK, and evidently in some areas the server either isn't giving one or the data in its packet is not what the client was expecting.
The best thing you can do is try to see if there's some pattern to all this -- do you seem to get hung up after you do *this* or *that*? That will better help them chase down where the missing ACKs are.
PS: From a fellow luclinite, I'd like to say, welcome.
__________________
<idleRPG> Rogean ate a plate of discounted, day-old sushi. This terrible calamity has slowed them 0 days, 15:13:51 from level 48.
|
Linear Mode
