egghelp/eggheads community

Ok guys, back to my new script. Here is the code I have so far: ################################# ## greeting.tcl by kazoo ###### ## www.conflabit.net ###### ## david@conflabit.net ###### ################################# # For the channel greeting.. # You will need to set greeting.txt # To your gre...

Seriously... if I have time, I can rewrite this whole script in less than 10-15 lines, out of the total 200+ lines. :wink: And still it will prove to be the same efficient, as it currently is! :mrgreen: There are very good, customizable greet scripts out there! Why did you specifically choose this ...

Here is the whole big mess: ################################################# ## greeting.tcl by kazoo ## ## www.conflabit.net ## ## david@conflabit.net ## ## ## ## Modifications by Ratman ## ## http://www.homecomputersecurity.net:81 ## ## ratman6@charter.net ## #####################################...

Paste the script (procedure) here, so we can take a closer look. :mrgreen: Here we go: proc proc:greet {nick mask hand chan} { global greetchan global greetvar global greeting global greetchan2 global greeting2 global greetchan3 global greeting3 global greetchan4 global greeting4 global greetchan5 ...

]Kami[ wrote:It clearly say's the error

E.g. you have {nick uhost handle channel arg}, if you have like this, then change it to {nick uhost handle chan arg} ..Just put chan in it, or change variable....

I have {nick uhost handle chan arg} but it is still doing it

Getting this iin a script I modified Tcl error in file 'greetbot.conf': [19:57] can't read "chan": no such variable while executing "string match -nocase "$greetchan" $chan" (file "scripts/greeting.tcl" line 1) (file "greetbot.conf" line 1) What now....

still get kicked no matter if it's + or -

peharps a stupid idea, but nodesynch isn't an inverse command? +nodesynch => the bot won't allow non-op to execute a mode change -nodesynch => the bot allow it Try to understand the way it work: if you enable the nodesynch, the bot keep the modes because non-op changements are a desynch abuse for i...

ratman wrote:

Dedan wrote:make sure your channel settings are not
changing your Global settings.

That seemed to work, thanks

It didn't work, any more ideas?

Dedan wrote:make sure your channel settings are not
changing your Global settings.

That seemed to work, thanks

# nodesynch # Allow non-ops to perform channel modes? This can stop the bot from # fighting with services such as ChanServ, or from kicking IRCops when # setting channel modes without having ops. maybe you need: +dontkickops # dontkickops # Do you want the bot not to be able to kick users who have ...

# nodesynch # Allow non-ops to perform channel modes? This can stop the bot from # fighting with services such as ChanServ, or from kicking IRCops when # setting channel modes without having ops. maybe you need: +dontkickops # dontkickops # Do you want the bot not to be able to kick users who have ...

I have an eggdrop and even though I have nodesynch set to + for then chan it still insists on kicking me out. Suggestions?

Turambar wrote:100? hmm that's quite a lot though. Most ircd's I know of use a default of 10 or so...

it was 10, set it to 20...now to go do the other side of the net

issue closed

GodOfSuicide wrote:there is no real limit for the bot, but the network maight limit the maximum number of channels

hmmm that could be it I'll check the IRCD....I think that number's like 100 though