Channel Banlist => Restarting an eggdrop VS ban-time XX

gemeau50 · Post by **gemeau50** » Fri Oct 08, 2004 12:50 pm

Version: 1.6.16

When restarting a bot, it waits for a period equal to the "ban-time" before starting removing bans equal to "ban-time" or older. By removing older ones, it means that it is able to remove bans set before it joined a channel. Therefore, why doesn't it start removing bans as soon as it joins a channel?

TIA

YooHoo · Post by **YooHoo** » Sat Oct 09, 2004 6:04 am

Code: Select all

# Set this setting to 1 if you want your bot to expire
# bans/exempts/invites set by other opped bots on the channel.
set force-expire 0

gemeau50 · Post by **gemeau50** » Sat Oct 09, 2004 7:44 am

It is already set to 1.

For argument sake, let say: ban-time = 60 minutes

My question wasn't how to make a bot removed expired bans but why does it have to wait a period of time equal to the "ban-time" (60 minutes) after joining a channel before starting to cleanup the channel banlist?

ex.:
Bot left channel 7:45
Bot rejoined channel 8:00
It won't start cleaning the channel banlist before 9:00
and when it does, it will remove all bans which have been on the channel for more than 60 minutes.

YooHoo · Post by **YooHoo** » Sat Oct 09, 2004 2:08 pm

ah

i misread your question... seems like this would be easy enough to manipulate via tcl. You've explained what happens atm, could you also let us know what you wish the end result to be...just cos I'm dense like a brick

gemeau50 · Post by **gemeau50** » Sun Oct 10, 2004 7:09 am

In fact, it does what expected but with a delay.

My eggdrop doesn't have individual ban-time per channel but uses "global-ban-time".

set global-ban-time 60

08:00 bans #1
08:15 bans #2
08:30 bot joined channel
09:30 bot removed bans 1 and 2.

In order remove these bans, it has to update its internal channel banlist (or something similar). It seems that there is something being triggered after 60 minute which tells the bot to wake up and start checking the channel banlist for overdue bans which needs to be removed.

I presume that there is an operation being done through a timer which evaluates the time length of a ban:
time present - ban-time > 60 minutes
in order to identify overdue bans.

The only thing I am wondering is why does it have to wait for a period of time equal to the ban-time before working on the channel banlist rather than doing it as soon as it joins a channel?

gumbydammit · Post by **gumbydammit** » Sun Oct 10, 2004 5:06 pm

because when it joins a channel it has no idea when the bans active on the channel were set..how could it if it was not there ?

gemeau50 · Post by **gemeau50** » Sun Oct 10, 2004 5:12 pm

Then, can you tell why it is able to find out an hour later? Bans were done before its joining time.

greenbear · Post by **greenbear** » Sun Oct 10, 2004 5:33 pm

gumbydammit wrote:because when it joins a channel it has no idea when the bans active on the channel were set..how could it if it was not there ?

a raw lookup give you the time the ban is set, and by who.

gemeau50 · Post by **gemeau50** » Sun Oct 10, 2004 5:58 pm

gb wrote:a raw lookup give you the time the ban is set, and by who.

I presume that it uses a command similar to:
mode #channel_name b
and gets its info's via raw 367 and 368

Why can this be done when it joins a channel?