We have the ability to autoreconnect on disconnect. Has anyone suggested the ability to keep trying for reconnection? I.E.
I try to connect to MU* X. I fail. Instead of stopping there, I've often wanted to tell MUSHClient to keep trying X number of times, or for X amount of time.
This could be combined with other features I'm suggesting; like the traceroute. I imagine it'd be pretty hard to do, but a combination of the two ideas would be... on failed connect, have the option to do a traceroute (invisible to user or visible to user), or a ping, etc., for X number of times, and if the connection comes up good within that X number of times, then attempt a reconnect.
Also, it'd be semi-useful to be able to ping the connection from within the world.
I try to connect to MU* X. I fail. Instead of stopping there, I've often wanted to tell MUSHClient to keep trying X number of times, or for X amount of time.
This could be combined with other features I'm suggesting; like the traceroute. I imagine it'd be pretty hard to do, but a combination of the two ideas would be... on failed connect, have the option to do a traceroute (invisible to user or visible to user), or a ping, etc., for X number of times, and if the connection comes up good within that X number of times, then attempt a reconnect.
Also, it'd be semi-useful to be able to ping the connection from within the world.