Quote:
Originally Posted by Treats
[You must be logged in to view images. Log in or Register.]
I think it is just you lagging, happens sometimes.
|
To clarify, I think that is what happens when your packets get out of order. So your client is told that you were hit by X but X is already dead, so when it can't find X in some internal hash table it says pain and suffering. AFAIK EQ uses its own custom TCP stack that never backs off and probably doesn't preserve windows completely.