 |
PHLN
Adept
Joined: 30 Dec 2001
Posts: 220
Location: Canada
|
 Posted: Sun Sep 15, 2002 9:25 am
Auto-reconnect limitation...
|
Does anyone know how to solve the auto-reconnect limit to max 20 or so reconnects? I don't wanna have to wait and watch till it reach the max and having to click reconnect again to start the cycle over. There must be a way for me to set it so that it keep reconnecting until a successful connect is made.
|
|
|
|
|
TonDiening
GURU
Joined: 26 Jul 2001
Posts: 1958
Location: Canada
|
Posted: Sun Sep 15, 2002 9:50 am
|
Try possibly this and consider this.
Ton Diening |
|
|
|
|
pao
Newbie
Joined: 11 Sep 2005
Posts: 3
|
Posted: Sun Sep 11, 2005 11:47 pm Auto-reconnect limitation
|
I too am having this problem with the autoreconnect limitation. Is there any way to turn it off? or increase the limitation from 20 to a much higher number? this would be appreciated.
|
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
Posted: Mon Sep 12, 2005 3:24 am
|
Wow, old topic brought back to life. I turn off the auto reconnect in the preferences for all my characters. Then I use this
| Code: |
#CLASS {System|AutoRecon}
#ALIAS atdisconnect {DeactivateChar;#IF (@IsQuitting=0) {#T+ RecconnectAlarm;#T- LoginTimeOut;ConnectStatus=1;ConnectTime=0} {ConnectStatus=0;ConnectTime=0;IsQuitting=0}}
#ALIAS quit {IsQuitting=1;#T- RestTrigger;#SEND {quit}}
#ALIAS atconnect {#T- RecconnectAlarm;#T+ LoginTimeOut;ConnectStatus=2;ConnectTime=20}
#VAR IsQuitting {0} {0}
#VAR ConnectTime {0}
#VAR ConnectStatus {0}
#ALARM "RecconnectAlarm" {*1} {#ADD ConnectTime 1;#IF (@ConnectTime=20) {#T- RecconnectAlarm;#CON}} "" {disable}
#ALARM "LoginTimeOut" {-60} {#ECHO Login data not requested before timeout.;#DI} "" {disable}
#BUTTON "ConnectBtn" "%if(@ConnectStatus=2,Disconnect,%if(@ConnectStatus=1,Reconnect:%eval(20-@ConnectTime),Connect)" {#IF (@ConnectStatus=1) {#T- RecconnectAlarm;ConnectTime=0;ConnectStatus=0} {#IF (@ConnectStatus=0) {#CON} {#DI}}} {} {} {@ConnectTime} {} {} {Size} {120} {14} {Pos} {1} {880} {32800} {} {Gauge||9|20|19|12} {} "" {} {} {} {4}
#CLASS 0 |
My auto login triggers turn off the LoginTimeOut trigger when login successfully occurs. This is done because sometimes the mud will accept a connection before it is truly ready to handle one. I found it better to just disconnect and try again. You may have to adjust the button positioning for your screen layout. One item not shown here is my atload alarm that sets all the variables and triggers to the correct states. I always open my characters offline then use my own connect button. The atload alarm is done as follows
| Code: |
#ALARM {*.5} {#NOOP at load commands here}
#COND {} {#NOOP} {manual} |
This works because trigger states are not saved in the .mud file. So the trigger is reset to being in alarm mode at each load and then can not fire again. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
pao
Newbie
Joined: 11 Sep 2005
Posts: 3
|
Posted: Mon Sep 12, 2005 3:39 am
|
Hmmm, it looks good and all, however, i have no problem connecting to the mud ever. i'm using the script for link dead brewing. this involves cycling through a series of characters quite fast to prevent my 8 allowed ip's to the mud be taken up, aka: brewing with 50+ characters instead of 8. so, would this solution still apply?
|
|
|
|
|
|
|
|
