| View previous topic :: View next topic |
| Author |
Message |
dhp1080 Voice
Joined: 14 Aug 2006 Posts: 8
|
Posted: Sat Aug 11, 2007 5:20 pm Post subject: Eggdrop breaks itself supposedly |
|
|
I have an eggdrop running on FreeBSD. I run the old version of AllProtection.tcl (Version 4.5 does everything I need, and I found it more stable than the new release). Everything runs well until randomly the bot stops setting the channel limit. I can't find a rhyme or reason as to why it does this, but it happens and it doesn't make me a happy person.
I'm running the latest Eggdrop (1.6.1 and this happens periodically. I've been able to fix it by reinstalling eggdrop completely, but as of recently that hardly works.
I get the error...
| Code: | [16:05] Tcl error in script for 'init-server':
[16:05] missing " |
When I attempt to connect to the network. This is on a fresh install of the bot.
I'm just asking for a simple solution to make my bot as reliable as possible. If that means putting it on another OS, changing eggdrop versions (I tried eggdrop 1.6.16 and had no luck), or changing scripts, I'd be willing to do it.
Thanks for your help in advance. |
|
| Back to top |
|
 |
nml375 Revered One
Joined: 04 Aug 2006 Posts: 2857
|
Posted: Sat Aug 11, 2007 8:07 pm Post subject: |
|
|
The error you posted would suggest there is a flaw in your config when defining the proc named "init-server", which is executed whenever your bot think it connected to a server. That part of the config-file should look something like this unless edited:
| Code: | bind evnt - init-server evnt:init_server
proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +i-ws"
}
|
As for the chanlimit issue, I am not familiar with AllProtection.tcl to shed any light on that I'm afraid. _________________ NML_375, idling at #eggdrop@IrcNET |
|
| Back to top |
|
 |
Sir_Fz Revered One

Joined: 27 Apr 2003 Posts: 3793 Location: Lebanon
|
Posted: Sat Aug 11, 2007 8:53 pm Post subject: |
|
|
AllProtection couldn't be possibly the cause of this problem. It is definitely a problem inside the init-server proc. _________________ Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
 |
|