Bot not banning and .set problem

Chack · Post by **Chack** » Mon Feb 10, 2003 12:04 pm

I got an eggdrop (1.6.12) running on QuakeNet. The Network does support up to 30 bans per channel. But still the Bot will never ban more than 5 masks. I also set the max-bans in the eggdrop.conf to 30. The bot still won't ban anymore.

My other problem is that the .set command won't work. If i use .set max-bans in DCC the bot won't recognize the command.

Btw, anyone knows what net-type quakenet really is? Is it 1 or 5?

ppslim · Post by **ppslim** » Mon Feb 10, 2003 12:30 pm

First off.

The net-type setting depicts the default setting for max-bans.

You should try changing net-type to custom, so max-bans is free for changing.

Second, the ".set" command is disabled by default due to the security risk it poses, and the possible issues of social engineering.

See the config file, for more information on re-enbaling the ".set" command.

Chack · Post by **Chack** » Mon Feb 10, 2003 1:08 pm

yeah, I fixed the .set command thanks

I use net-type 5 and maxbans 30 (and the network does support 30), btu still the bot will never set more than 5 at once.

Is there some additional hidden configuration file?

Fluxism · Post by **Fluxism** » Tue Feb 11, 2003 1:51 pm

I have my eggs on Quakenet and they are set to 'net type 5'.

I can't offer a direct solution to your ban problem, but maybe trying this might help locate the problem. Kill the bot, then goto your eggdrop folder, and delete or rename the *.chan file and the *.bak file for the same. Now you can edit the eggdrop.conf file, knowing that it is only settings within that file which are going to effect the behavior of your bot on IRC, and not the chan settings files. Once the bot is started, new *.chan files will be created.
No real help... but this is the first thing I do when I cant locate a problem.