Camping/Quit Issue and Lost connections

[typhoon]

Ok I am tryin to track down an annoying bug. When ever I camp on my server, I am immediately disconnected. When I camp on PEQ or any other server I get the 30 sec count down and then I am logged out like normal.

This has existed since day one when I built my server (v0.6.2) and still happens on build (v0.6.4 - 588) I replaced the Opcodes.conf file with one in that build and it still happens. Any ideas what could be the causing this?

I am also having a problem with people going Linkdead or getting disconnected after awhile but the server still keeps sending packets to them. I have had it happen with a friend in game and it wouldn't let him reconnect because it still said he was on. I had to kick him to let him log back in. Any help on how to fix this problem would be appreciated.

I am running this all on a PIII 1 GHZ, 512MB RAM with Windows2003 Server. and Mysql is on the machine.

[mattmeck]

Anyone flagged as a GM gets disconnected right when they hit camp, no 30 sec wait.


as to the LD issue, how long did you wait for the server to boot him on its own? Remember even on live it took a little!

[fathernitwit]

this is a known issue, we dont have the packet to tell the client to insta-log, so GMs get hit with this when they log... only solution right now is to #gm off before you camp.

[typhoon]

thanks for the info on camping as a GM. I didn't know that.

As far as the LD goes. I waited 30 mins. I have also seen a friend stop moving and not respond to any tells for a couple of hours. I figured he just went AFK. Talk to him on AIM and have him tell me he got booted and hasn't been on for several hours or tried to get on. I look and my server still says he is connected and is sending packets out. So it must be something on my setup causing this. I haven't experienced this problem playing on any other servers.

[mattmeck]

I use to have to boot "players" off all the time on Scorpious2k, and on Raid Addicts, this has been an issue for a long long time.

[gottasummer]

Possible solution:

Gm check

this would obviously not be code that I am typing, just my thoughts...... (I do this when I think of possible solutions...)

if logoff is true & gm is yes then
gm = no
logoff()


In other words, when you go to logoff, do a GM check first... as this issue happens when your a GM, so if you check and remove GM TEMPORARILY, then it might work.

[fathernitwit]

yea, we could work around it in the code, hadnt thought about that. Maybe I will code this up later

[gottasummer]

I could do it too, but I really do not know how to do it in this case, considering there is no documentation, which is okay... I can live without it... but I would probably be able to do it real quick then.

My birthday was yesterday, am sort of tired, stayed up late... this morning I took dogs for walk, am about to go get lunch (Take out)...

Right now I am compiling mysql on my laptop here to get the libs, my installation doesn't have them on my linux box :(

But yeah, some things I have thought of that could work... that one there about temporary GM removal should work if what I am thinking is correct.

Just don't have it save the no-more-gm into the database... that way when they log back in, they are still GM.

[mattmeck]

I am wondering why it needs to be "Fixed" I always liked not needing to wait the 30 seconds... players needing to wait 30 seconds I see and agree with, but a GM needing to??

[fathernitwit]

well on 6.4, the insta-log hangs the client, and you have to wait for the netcode to time out, then you get "you have been disconnected", then back to world... it generally takes just as long as waiting normally, and has a decent chance of crashing the client.

As for the fix, you dont need to change their GM status, you just need to comment out the special code which insta-logs GMs (its all server side).

[Dr Zauis]

Man..Somehow I must have missed this thread.
Luckily someone was viewing it while I clicked "whos on"..

I get alot of LD players also..I dont know if they can log back in or not but never had any complaints. Once they go LD they are there pretty much forever until I boot em.
Today I was looking at an LD players zone and noticed he made mistake and say exit. Maybe he used /exit and cause a problem.. I havent checked yet though.
At least now I know this is a known issue..