BANS AND HOW THEY WORK
I assume that you know how bans work on IRC. Eggdrop handles them in various ways, and this chapter is intended to help clarify how bans are treated within the bot. There are three types of bans, and two types of attribute that can be placed on a ban:

Types of bans:

  • global bans

  • These bans will be active on every channel the bot monitors. Some will "expire" after a while (be removed automatically). Others are considered "permanent" and can only be removed by a master.

  • channel-specific bans

  • These bans are active only on one channel, and are almost always temporary bans that expire after an hour or so (depending on how long you've specified in the config file). Usually they're created by the "revenge" mechanism (if active), or by a Tcl script of some sort.

  • non-bot bans

  • These are bans that were not placed by the bot, and that the bot doesn't care about. They can be removed by anyone on the channel. The other two types of bans are generally protected by the bot, and have to be removed via the bot.
    Attributes:
  • unsticky bans

  • These bans are the style that eggdrop sets by default, when it uses the "revenge" mechanism (if active) or when a user uses one of the commands that results in a ban. This attribute means that the ban will be removed if using dynamic bans after a certain time. If a ban is "sticky" and you wish to set it to be unsticky, use the ".unstick" command.

  • sticky bans

  • These bans are usually set by a user using the ".stick" command, bans with this attribute are attempted to be kept active on the channel by the bot, even if the channel is set to use dynamic bans. Obviously, if the channel isn't set to use dynamic bans, this won't have any effect.

    The party-line command ".+ban" can add a global ban or channel specific ban depending on the parameters that are passed to it. ".kickban" will add a channel-specific ban. ".bans" will list them all, according to their category. Be sure to check out the help pages for those commands for more info.

    (c) 1997 Robey Pointer
    (c) 1998 Eggdrop Development Team