Players going semi link dead

HurtinuDaily · #1 03-07-2008, 01:30 PM

it happens to melees to, its like the client is waiting to recieve a packet back from the server. Its very annoying to say the least.

jasper · #2 03-08-2008, 01:10 AM

I keep having this problem on my War's.. only been my War so far.. 2 of them on 2 different servers.

Gets on my nerves.. heh

**cavedude** · #3 03-08-2008, 03:14 AM

Quote:

Originally Posted by HurtinuDaily

its like the client is waiting to recieve a packet back from the server.

That's exactly what is happening. Any function can cause this, if they are missing an opcode, or aren't properly implemented.

moydock · #4 03-11-2008, 10:10 AM

Yeah this bug plagues me. Is there any way to add code that says, if theres a problem with an opcode, ignore it and go on?

Also, I've noticed that if you make a change in your inventory while half linkdead, it will remember that upon logging back in. But it won't remember any movement you may have made.

Also, it seems to happen a lot more to some people than others.

So_1337 · #5 03-11-2008, 10:40 AM

My girlfriend's bard has been unplayable for some time now due to this. I've even had her remake the character two different times. All three versions wind up the same; it gets to where she can't log in. Then, when she can, she crashes whole zones when she does =P She just started playing a warrior instead, heh.

Had a thread going here about this same issue, including some of the op_code errors I was seeing. However, just seems something that has to be dealt with. Admittedly, I've seen it become a lot rarer lately than in past versions.

**trevius** · #6 03-11-2008, 11:41 AM

I am curious if this bug is seen on Linux servers. If it isn't, there may be some adjustments that can be made on Windows to stop it.

I put in a small change this afternoon on my server running on windows XP SP2. It has to do with how many connections windows allows per second. If I get feedback saying it has stopped the problem completely, I will definitely post it in the forums here. Otherwise, if it didn't stop it completely, then it probably didn't effect it at all. It is hard to judge if you are helping an issue like this since it is so sporadic.

I am trying to make adjustments 1 at a time to see if it helps resolve this issue or the player ghosting issue. Both of those problems are high on my list of bugs I would like worked out, since they both effect the players and the server overall in a huge and annoying way. I am also curious if player ghosting is only a Windows thing and not seen on servers running on Linux at all.

**cavedude** · #7 03-11-2008, 12:43 PM

The bard issue is a completely different situation. That's a zone crash caused by something in the AA listing code.

As I stated above, the "bugged" state is caused when something is missing/broken in the code and the client sends a packet to the server, but the server doesn't know how to respond so it sends nothing back. The client will do nothing but wait for the packet to arrive. Anything can cause this, and if I think about it I can probably come up with several different and unrelated situations where this can occur. Since we are unable to change the client's behavior (and let's say force it to continue on without getting a receipt packet for a function) there is nothing to be done but correct the root issue which is not always easy to find.

Generally speaking, this isn't a symptom of connection issues. They will usually cause full fledged link deaths or crashes to desktop/login.

So_1337 · #8 03-11-2008, 02:00 PM

Sorry, you're right. Bard is unrelated, but it led me to find all those other op_code errors in the thread I linked. I side-track myself sometimes. Was mostly making the point that I found with her bard, which is that in some cases there's nothing we can do but wait until the problem is found.

I know you mentioned pick pocket is an easy one to produce. I think that rogue poison (the applying portion) is another, though it doesn't bug the client entirely.