Players going semi link dead

So_1337 · #1 03-13-2008, 01:11 AM

Right, but it's seeming more and more like your issues might be bandwidth related. I was having trouble keeping more than two groups connected on a business-class DSL connection (3 Mb down/700k up) that was mostly limited by a junky, off-the-shelf router whose throughput seemed to be the bottleneck. You seem much better off in regards to the router, but I'd bet dollars to donuts that you don't see this happening at times of low population (12 people and under).

It's exactly akin to the 'bugged' state we discussed earlier in the thread that is caused by missing op_codes and the client and server getting out of sync. It's much easier to miss an op_code or crucial piece of data if your server's connection can't push things to the client. We used to see people on my server getting bugged very often any time we had more than 12 (twelve!) characters logged in. Since we upgraded to our DS1 connection, we've never seen it happen except from spells/skills and op_codes, etc.

jasper · #2 03-16-2008, 12:20 AM

so im seeing this problem still on other char types, not just my war as mentioned. I get it alot .. and it seems like there is no reason for it.

Today I was just running along.. tried to con a mob and got no response. Did the /who all, which I use to see if the bug has happend.. and yup was bugged. I know I did nothing special to cause it.. I was just running from one zone to another, EC to WC.

Joetuul · #3 01-14-2009, 05:38 PM

I have recently come across this bug myself, as it happens to me. here are some details that I'm hoping will help the dev's...

When I sit in the nexus, I am fine for hours on end. but if I sit in Natimbi for too long this happens to me, could it be a problem with specific zones? is there a fix for this that just hasn't been posted? Even if I am actively doing something in Natimbi it still does it. I have to keep doing /who all just to make sure I am not bugged, if I am I /q out and log back in just fine. No one else on my server has reported this happening to them.

any help for me? or am I SOL?

**trevius** · #4 01-14-2009, 06:46 PM

This problem has been resolved months ago in a code update. If you are running old code, the best solution would be to upgrade it to current (from the SVN).