Several times a day, I stop receiving data from some of the 3-5 networks I'm usually on. But mIRC 6.14 doesn't realize this and attempt to reconnect until I type something or exactly 2 hours elapses (the 2 hours appears to be TCP server-side keepalive interval that I cannot lower). Then it says 10054 Connection reset by peer and reconnects me.
if I type something within a minute or so of receiving no data, it'll actually start receiving data again after a lag without formally dis&reconnecting.
I've searched and have tried the script that standalone in this thread helpfully made.
https://forums.mirc.com/showflat.php?Cat=&Board=connectionissues&Number=89906alias ctcpping {
/set -u120 %alive $true
.timer 0 60 checkctcpping
}
alias checkctcpping {
if (!%alive) { /server $server }
else { .ctcp $me PING2 }
}
on *:ctcp:PING2:{ if ($nick == $me) /set -u120 %alive $true }
From what I understand, this means
CTCPPING: unset Variable alive:true / I'm considered dead after 2 minutes.
TIMER: Every minute, run CHECKCTCPPING: If I'm dead, reconnect to server. Otherwise, ping me.
When I'm pinged, postpone death for 2 more minutes.
I tried it without other scripts in my remotes, script.ini and it still didn't realize I was dead until I typed something. Is there an error in this script?
I'm not using a proxy or XP, as this thread suggests.
https://forums.mirc.com/showflat.php?Cat=&Board=connectionissues&Number=27653I'm using a Linksys router and Win98. Could it have something to do with the router?
Any suggestions please.