A possible linkdeath fix

**trevius** · #1 07-04-2008, 05:24 AM

Just wanted to mention that 2 of my players that have had this bug chronically have just posted saying that they haven't seen it happen a single time since this code was added about a week ago.

**trevius** · #2 07-25-2008, 05:57 PM

This one definitely needs to be added in the next release! It is a verified fix as far as I am concerned. Still have not had a single player report this bug since I added this on my server.

**KLS** · #3 07-25-2008, 06:14 PM

It should be in atm.

**trevius** · #4 07-25-2008, 06:22 PM

Sorry, just saw that lol. Didn't see you already just put a release out. Going through and posting in the others I think should be in the next one.

**Congdar** · #5 09-09-2008, 11:12 AM

I'm still seeing this error... Did this fix make it in? If it did, it wasn't the final solution :(

Tried to write a packet beyond the end of the queue!

This is filling up log files. I could just rem out the line in the code, but that doesn't fix whatever is wrong, only hides it. Maybe somebody can convice me that this isn't really an error?

**trevius** · #6 09-09-2008, 05:16 PM

This fix doesn't stop out of order packets from coming in, it just gives the server a way to handle them.

The out of order packets issue that fills the log files is something different. I find that it is normally caused by players with high latency, like from China. I don't think there is really any possibly solution to it, since it seems to be network related. Of course, I could always be wrong :P

**cavedude** · #7 09-09-2008, 05:37 PM

Quote:

Originally Posted by trevius

Of course, I could always be wrong :P

I believe you to be correct. The packets are coming in out of order so it is a network issue. There isn't anything EQEmu can do besides deal with it. PEQ too sees the logs fills up from people that are in Asian countries, where there are fewer links to the rest of the world.

irv0 · #8 09-10-2008, 10:40 AM

Quote:

Originally Posted by Congdar

I'm still seeing this error... Did this fix make it in? If it did, it wasn't the final solution :(

Tried to write a packet beyond the end of the queue!

Unfortunately the change I made won't (shouldn't, anyway!) have an effect on the issue you are seeing. As far as I can tell from a cursory look at the code, the "Tried to write a packet beyond the end of the queue" problem is related to server => client communications, whereas my change primarily affects client => server communications.