Zugg Software :: View topic

Newbie Joined: 14 Aug 2003 Posts: 5 Location: USA

I've been looking all over zMUD... I can't find a way to change the time or remove the idle time... can someone please tell me where I can find this?

Wanderer Joined: 29 Apr 2004 Posts: 63 Location: USA

if you are asking what i think, getting kicked off the mud for idleing?, then set a ticker to do something... such as scan, say (what ever), or anything else really. some muds may not accept ceratin commands for the ticker

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Timeout values are controlled by your Connection preferences. The timeout for IP Address lookup is controlled by the values on the IP Address Lookup page. The timeout for each connection attempt is controlled by the Connection Timeout value on the Reconnection page.

I don't think the timer for the Connection Timeout begins counting until you've received (or input) an IP Address, so a connection attempt won't timeout while you're waiting for the DNS server.

zMUD doesn't have an idle timeout to close the program or disconnect from a MUD.

Newbie Joined: 14 Aug 2003 Posts: 5 Location: USA

The mud doesn't automatically kick idle players. I'm idling out because of something in the mud, it has nothing to do with connecting to the mud...

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

quote:
The mud doesn't automatically kick idle players. I'm idling out because of something in the mud

So Which is it If your getting disconnected from the mud and the mud doesn't kick idle players ask an immortal to look into it.

But in any instance this alarm trigger should stop it

#HELP ALARM
#HELP CR

Here is what I use on my mud to keep from idling out
#ALARM "IdleTrig" {+10} {#CR}

Simply put it sends a carriage return every 10 minutes.

Beginner Joined: 12 Mar 2003 Posts: 14

There are several reasons why you may be getting an idle timeout such as this. In most cases though the alarm trigger trick should be a decent workaround for it. If you run a firewall of any kind (broadband router possibly?) or any type of NAT setup then the firewall is most likely the culprit. On linux firewall setups you can adjust the timeout using iptables or ipchains, on other setups you will need to seek documentation from the firewall manufacturer. It may also be a winsock problem however I'm not aware of any version of windows that once patched has a faulty winsock in this manner. One thing is certain though, it is not a Zmud specific problem, you will have the same problem with any winsock application that has an idle connection for that long.