I don't know if it's just me, but I get disconnected several times throughout the day. My timeout is set to 30 minutes.

When I get disconnected, I get about 30 seconds of lag first (by lag I mean everything stops), then Treant gives me the 'you have lost connection' popup. After that, I can connect just fine, but when I do all my defs are gone.

Now... what is happening? I assume something on my side is happening for me to lose my defs, because Ardmore should TECHNICALLY be online for 30 minutes until he times out.

Is this a setting with Mush, or something? It's really starting to piss me off.

Edit: When I say 'throughout the day' I mean every day. Not today imparticular. This just started happening a few weeks ago.

I haven't been experiencing that... so it's not something serverwide that I can think of.

If it was today you could blame the earthquake and the severe storms and tornado warnings. Anyways, I have no idea. I've been lagging a bit, even to the point of disconnect, since I moved back to Toronto. Not every day, just occasionally.

The server will drop you if it recognizes your link's dropped (I'm not sure how it does that though!).

But I thought that was the whole point of the TIMEOUT function... So if you go link-dead it will drop you after x minutes.

I do appreciate the reply, Eventru. Just trying to figure out a possible fix for this!

The TIMEOUT function is for afk, not link-dead.

I think timeout was originally put in because people would go link dead, die, and be sitting around as a soul for ages and lose a boatload of xp. I also think I remember admins warning to set a low timeout to prevent such things from happening. I could be wrong though.

I feel like there are two different kinds of linkdead, one where you're kicked and one where you're not. I've definitely been kicked and come back and sometimes I have my defs, and sometimes I don't, with similar amounts of time gone.

Hm, I usually keep the java clients open as well as the mush clients as well, so that if I am lagging insurmountably, I will switch automatically to nexus. Then I would restart the mush client if needed, and then switch back. But I know what Ardmore is talking about, this is just my solution to it.

I've been getting that too. I use Nexus.

There is a certain amount of back and forth chatter inherent in the telnet protocol. If your client can't respond when it should, you're linkdead. There's no correct response left for your client without jeopardizing the data. Lusternia drops you, and your defs are lost. Sometimes, the problem is packets lost from Lusternia to you. (Neither is really more likely when you have network issues.) When your client sees something that doesn't make sense in the telnet protocol, it just abandons the connection. MUSH drops you, you reconnect, your defs are still there. Telnet's protocol also provides for an "are you there" transmission. While not required, it certainly makes sense to use it, and if you fail the test, it makes sense to drop you.

Check/replace your router/modem?

I don't know, I've ran all sorts of tests and I also do what Falcon does, but occasionally it just doesn't work.

I was thinking it could be a routing issue between the servers and myself, since it just recently popped up, but who knows.

I'll live with it for a while and if it continues I'll do as Larkin suggested.

Stupid defs are expensive in power.

If you get disconnected from Lusternia and other things still work, like browsing Facebook or downloading from iTunes, then I'd recommend running a traceroute the next time it happens. If everything goes down and the rest of us are partying without you, it's almost certainly your router or modem that's to blame.

I've been having steady lag now and then for the past week too. And one time I disconnected and immediately reconnected but had lost defs. All the other times I disconnect (up to 20 times a day) it's because my cable internet providers sucks so bad. Fortunately it usually reconnects within 2 minutes and I haven't lost defs (though I sometimes die/lose an influence battle).

Do most people that play this game use nexas or a different mud client?

Most will be using third party clients because they are more powerful and/or versatile then nexus. The most common used clients are mushclient (systems available for purchase), mudlet (systems under development) and the dying zmud/cmud

As I was looking at this thread, if it's still happening Ardmore, try to disable and then re-enable your network adapter.

It was happening to me (and I was nerdraging like crazy), but I went ahead and tried that (skeptically) and it actually fixed the problem.

I, uh, think I fixed the issue. I was going off wireless for a long time (because I used to drag my laptop to my bed so I could watch TV on it, but I bought a PS3 and TV, sooooo!), but instead I decided to plug in my ethernet cable and it seemed to work. So I think the wireless on my router is starting to go.

Thanks for the concern and thought though. <3 you Eve!

Ok today is the annoying day for me, I am recently getting repeated incidents of:



Now before people say it is mudbot, I had it a ton of times linking directly so I think that safely rules out mudbot. I rebooted my crappy router and that didn't solve anything, all other internet stuff works normally so I doubt that is it.

Now I am using mushclient 4.51 and the most recent treant. So any suggestions how to fix ? Or is it one of those wait a day or so and it will probably be gone?