Your bot is crashing probobaly because of some misconfigured script, some memory problem, or it can be with the source even the OS. But it is generally due to a tcl script problem.
If you have alot of scripts in it try to remove then and see, also try in DCC:
.tcl set errorInfo
This can locate tcl scripts which are causing errors. If the problem still exists, try contacting the eggheads team and report the bug along with the full logs and details.
·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee) PS: Guys, I don't accept script helps or requests personally anymore.
==================================
You have to comment out the unbind of dcc:tcl in the .conf file, then save it and restart the bot, then you would be able to use ".tcl" in the partyline. What I mean is:
Change this to:
unbind dcc n tcl *dcc:tcl
this:
#unbind dcc n tcl *dcc:tcl
·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee) PS: Guys, I don't accept script helps or requests personally anymore.
==================================
awyeah wrote:You have to comment out the unbind of dcc:tcl in the .conf file, then save it and restart the bot, then you would be able to use ".tcl" in the partyline. What I mean is:
Change this to:
unbind dcc n tcl *dcc:tcl
this:
#unbind dcc n tcl *dcc:tcl
And you should be a permanent owner of the bot. In your conf file: set owner "<your handle>"
# Comment these two lines if you wish to enable the .tcl and .set commands.
# If you select your owners wisely, you should be okay enabling these.
unbind dcc n tcl *dcc:tcl
unbind dcc n set *dcc:set
Partyline:
[15:30] <multikon> .tcl set errorInfo
[15:30] <bot> What? You need '.help'
# Comment these two lines if you wish to enable the .tcl and .set commands.
# If you select your owners wisely, you should be okay enabling these.
unbind dcc n tcl *dcc:tcl
unbind dcc n set *dcc:set
Partyline:
[15:30] <multikon> .tcl set errorInfo
[15:30] <bot> What? You need '.help'
?!?!?[/b]
awyeah wrote:You have to comment out the unbind of dcc:tcl in the .conf file ...
Miss something?
#unbind dcc n tcl *dcc:tcl
#unbind dcc n set *dcc:set
Would help if you read.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
I think we should have a new front page to the forum with just the letters RTFM linking to the eggdrop help page. New users will not be allowed into the forum until they have visited it at least twice
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
I couldn't agree more awyeah It just seems that the people that come here for help dont actually read the help that is given to them. It's not as if reading is hard work
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
# Comment these two lines if you wish to enable the .tcl and .set commands.
# If you select your owners wisely, you should be okay enabling these.
#unbind dcc n tcl *dcc:tcl
#unbind dcc n set *dcc:set
Partyline:
[15:30] <multikon> .tcl set errorInfo
[15:30] <bot> What? You need '.help'
# Comment these two lines if you wish to enable the .tcl and .set commands.
# If you select your owners wisely, you should be okay enabling these.
bind dcc n tcl *dcc:tcl
bind dcc n set *dcc:set
Partyline:
[15:30] <multikon> .tcl set errorInfo
[15:30] <bot> What? You need '.help'
how did you manage to comment those two options out and test it? then uncomment them change them to a bind and re-test them all in the same minute?
[15:30]
Please dont waste our time by making up information that is obviously false.
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born