Help with Mushclient

I need help with this.


Since most badly-behaved routers that kill "idle" connections will kill them if there isn't traffic in -both- directions, you do need to have both something to send, and something sent back your client can safely ignore." to you.
In a page-pose to you, Keanu nods. "The part you do on your end though, that changes based on which program you get on the MUCK with, or which version sometimes, etc, and so that isn't something I can help with."
Keanu pages, "@action ping=me=ping <- It should say created exit and linked and some numbers. Ignore the numbers, you won't need 'em." to you.
Keanu pages, "@lock $ping=me&!me <- It should say Lock set." to you.
@action ping=me=ping
Action created with number #82081 and attached to Evelyn_Jane(#87638PB).
Registered as $ping.
Keanu pages, "@fail $ping=__DISCARD__ <- It should say Message set or similar." to you.
donothing
Huh? (Type "help" for help.)
Keanu pages, "Then the forum people just have to tell you how to send 'ping' to the MUCK every minute, and how to have the '__DISCARD__' it sends back not show up in your window. :)" to you.
@fail $ping=__DISCARD__

With what?

Since most badly-behaved routers that kill "idle" connections will kill them if there isn't traffic in -both- directions, you do need to have both something to send, and something sent back your client can safely ignore.

So add a timer that periodically sends a harmless command to your server.

I wrote this post because I do not know how to do it so my router sends a message back.

In MUSHclient create a timer that sends some game command to your MUCK that the MUCK will respond to with a message. In Aardwolf, for example, send a blank command returns another prompt line. That way you have traffic going both to the game from your computer and from the game back to your computer.

http://www.gammon.com.au/mushclient/timers.htm
http://www.gammon.com.au/forum/?id=9658