When using a trigger to log into a dcc I find that I am being disconnected after a minute or so.... the message says firstly "Closing Idle connection in 30 seconds" then it will say "DCC session closed"
What am I doing wrong .....this happens on every dcc I connect to.
There's nothing you can do about that except to reconnect to the fserve. The server can set a timeout period, if you don't type any commands during that period, you get the Closing Idle connection in 30 seconds message, and then if you don't type any commands in the following 30 seconds, the fserve closes your connection.
Is there any way to keep the session alive automatically via a script of some kind? I have seen a few posts with script information that you include in the perform option for mirc.
I have tried one of them but can't seem to get it working.
on *:CHAT:Closing Idle connection in 30 seconds*:msg =$nick Anti-Idle
That will work on some, but some have what's called Anti-Camp, which will close the session anyway unless you type an actual command, or you can try this one
on *:CHAT:Closing Idle connection in 30 seconds*:msg =$nick help
Yeah those too, but I wouldn't want to get flooded with a huge directory listing every time is why I used the help command, the cd command would do it too
on *:CHAT:Closing Idle connection in 30 seconds*:msg =$nick sends
Thats the one fserver explorer uses to stay connected. Sends doesnt trigger a reply from the server everytime, it must be flood protected or something.
