Author Topic: double bot in org... (Read 2656 times)

clashbot · « **on:** January 27, 2008, 05:56:20 pm »

I am creating a secondary bot for an org, as a backup(the primary bot has some database problems) but need to get bebot to ignore all guld commands but still be available for guest channel and tells. Is there an easy way to do this? Trying to prevent spamming by the new bot. They are not on the same machine, consider the new bot to be completely stand alone...

Alreadythere · « **Reply #1 on:** January 27, 2008, 06:00:41 pm »

Simply setting $guildbot to false in your Bot.conf should work.

clashbot · « **Reply #2 on:** January 27, 2008, 06:02:28 pm »

will that still maintain the roster and stuff?

clashbot · « **Reply #3 on:** January 27, 2008, 06:04:39 pm »

didn't work, think I need to change the command control chgaracter too..

clashbot · « **Reply #4 on:** January 27, 2008, 06:16:11 pm »

ok that seemed to work, it no longer doubles the onlines or anything, and changing the command character to the "\." eliminated commands from getting doubled up

Alreadythere · « **Reply #5 on:** January 27, 2008, 06:19:15 pm »

Uhm yeah, sorry. To run as backup for an org bot you have to run with guildbot set to true - otherwise several functions won't work.

As there is no way to disable a specific channel of the bot yet the only thing you can do to avoid double spam output is to use a different command prefix, yes.

I've put disabling of specific channels in the bot on my todo list though, should be in the next released version.

Temar · « **Reply #6 on:** January 27, 2008, 07:30:01 pm »

run this query in mysql
UPDATE botname_access_control SET minlevel = 'DISABLED' WHERE channel = 'gc'

Alreadythere · « **Reply #7 on:** January 27, 2008, 08:36:02 pm »

That disables all commands though, you'll have use !commands gc to enable them one by one.

Just commited command locking for gc and pgmsg to trunk, it will make the next release.

Temar · « **Reply #8 on:** January 27, 2008, 08:42:16 pm »

well if if wants to restore gc after the best way would be to delete all gc entries then let bot set them using there defaults

Alreadythere · « **Reply #9 on:** January 27, 2008, 08:54:37 pm »

Any custom settings are still lost when changing the DB directly though.

PS: If you do change anything in the database you should restart the bot, otherwise it may take up to one hour till the cache is refreshed.