[cvslog] Module eggdrop1.6: Change committed

cvslog cvs at tsss.org
Sun Dec 16 08:38:01 CST 2001


CVSROOT    : /usr/local/cvsroot
Module     : eggdrop1.6
Commit time: 2001-12-16 14:37:33 UTC
Commited by: Jeff Fisher <guppy at techmonkeys.org>

Added files:
     doc/settings/mod.channels

Removed files:
     doc/settings/mod.channel

Log message:

forgot rename mod.channel to mod.channels

---------------------- diff included ----------------------
Index: eggdrop1.6/doc/settings/mod.channel
diff -u eggdrop1.6/doc/settings/mod.channel:1.7 eggdrop1.6/doc/settings/mod.channel:removed
--- eggdrop1.6/doc/settings/mod.channel:1.7	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.channel	Sun Dec 16 08:37:33 2001
@@ -1,320 +0,0 @@
-##### CHANNELS MODULE #####
-
-This module provides channel related support for the bot. Without it
-you wont be able to make the bot join a channel or to save channel
-specific userfile information.
-
-Put this line into your eggdrop configuration file file to load channel module:
-
-loadmodule channels
-
-
-There are also some variables you can to set in your config file:
-
-set chanfile "LamestBot.chan"
-    Enter here the filename where dynamic channel settings are stored
-
-
-set ban-time 120
-    Set here how long temporary bans will last (in minutes). If you
-    set this setting to 0, the bot will never remove them.
-    Valid settings are 0-infinite
-
-
-set exempt-time 60
-    Set here how long temporary exempts will last (in minutes). If you
-    set this setting to 0, the bot will never remove them.
-    The bot will check the exempts every X minutes, but will not remove
-    the exempt if a ban is set on the channel that matches that exempt.
-    Once the ban is removed then the exempt will be removed the next
-    time the bot checks.
-    Please note that this is an IRCNET feature.
-    Valid settings are 0-infinite
-
-
-set invite-time 60
-    Set here how long temporary invites will last (in minutes). If you
-    set this setting to 0, the bot will never remove them.
-    The bot will check the invites every X minutes, but will not remove
-    the invite if a channel is set to +i. Once the channel is -i then
-    the invite will be removed the next time the bot checks.
-    Please note that this is an IRCNET feature.
-    Valid settings are 0-infinite
-
-
-set force-expire 0
-    Set this setting to 1 if you want your bot to expire bans/exempts/invites set
-    by other opped bots on the channel
-    Valid settings are 0 for OFF and 1 ON.
-
-
-set share-greet 0
-    Set this setting to 1 if you want your bot to share user greets with other
-    bots on the channel if sharing user data
-    Valid settings are 0 for OFF and 1 ON.
-
-
-set use-info 1
-    Set this setting to 1 if you want to allow users to store an info line
-    Valid settings are 0 for OFF and 1 ON.
-
-
-channel add #channel { SETTINGS }
-    Add each static channel you want your bot to sit in using this command.
-    There are many different possible settings you can insert into this
-    command.
-    A complete list of them:
-
-    chanmode +<modes>-<modes>
-     This setting makes the bot enforce some channel modes. It will add
-     always the +<modes> modes and remove the -<modes> modes.
-    Example:
-     chanmode "+nt-likm"
-     This will make the bot enforce the use of t and n and the removal of
-     l, i, k and m. The bot wont care about settings like s.
-
-    idle-kick 0
-     This setting will let the bot check every minute for x minutes idle
-     users. Set this to 0 or leave it out to disable idle check.
-
-    stopnethack-mode 0
-     This setting will make the bot de-op anyone who enters the channel
-     with serverops.
-     There're seven different modes for this settings:
-      0 turn off,
-      1 isoptest (allow serverop if registered op),
-      2 wasoptest (allow serverop if op before split)
-      3 allow serverop if isop or wasop
-      4 allow serverop if isop and wasop
-      5 if channel -bitch: see stopnethack-mode 3
-        if channel +bitch: see stopnethack-mode 1
-      6 if channel -bitch: see stopnethack-mode 2
-        if channel +bitch: see stopnethack-mode 4
-
-   revenge-mode 1
-    This settings defines how the bot should punish bad users when
-    revenging.
-    There are four possible settings:
-     0 for deop
-     1 for deop and chattr +d #chan
-     2 for deop, chattr +d #chan and kick
-     3 for deop, chattr +d #chan, kick and ban.
-    Valid settings are 0-3
-
-    need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
-     This setting will make the bot do the specified thing in the
-     brackets if it becomes opless.
-     Attention, you put anything that is longer than 120 chars in
-     here!
-     Note that if you use scripts like get-ops, you don't need to
-     set this setting.
-
-    need-invite { putserv "PRIVMSG #lamest :let me in!" }
-     This setting will make the bot do the specified thing in the
-     brackets if it needs an invitation to the channel.
-     Attention, you put anything that is longer than 120 chars in
-     here!
-     Note that if you use scripts like get-ops, you don't need to
-     set this setting.
-
-    need-key { putserv "PRIVMSG #lamest :let me in!" }
-     This setting will make the bot do the specified thing in the
-     brackets if it needs a key to a channel.
-     Attention, you put anything that is longer than 120 chars in
-     here!
-     Note that if you use scripts like get-ops, you don't need to
-     set this setting.
-
-    need-unban { putserv "PRIVMSG #lamest :let me in!" }
-     This setting will make the bot do the specified thing in the
-     brackets if it becomes banned.
-     Attention, you put anything that is longer than 120 chars in
-     here!
-     Note that if you use scripts like get-ops, you don't need to
-     set this setting.
-
-    need-limit { putserv "PRIVMSG #lamest :let me in!" }
-     This setting will make the bot do the specified thing in the
-     brackets if it needs a limit raise.
-     Attention, you put anything that is longer than 120 chars in
-     here!
-     Note that if you use scripts like get-ops, you don't need to
-     set this setting.
-
-    flood-chan 10:60
-     Set here how many channel messages in how many seconds from one
-     host are recognized as a flood. Not specifying or using number = 0
-     will not check against chan floods
-
-    flood-deop 3:10
-     Set here how many deops in how many seconds from one host are
-     recognized as a flood. Not specifying or using number = 0
-     will not check against deop floods
-
-    flood-kick 3:10
-     Set here how many kicks in how many seconds from one host are
-     recognized as a flood. Not specifying or using number = 0
-     will not check against kick floods
-
-    flood-join 5:60
-     Set here how many channel joins in how many seconds are
-     recognized as a flood. Not specifying or using number = 0
-     will not check against join floods
-
-    flood-ctcp 3:60
-     Set here how many channel ctcps in how many seconds from one
-     host are recognized as a flood. Not specifying or using number = 0
-     will not check against ctcp floods
-
-    flood-nick 5:60
-     Set here how many nick changes in how many seconds from one
-     host are recognized as a flood. Not specifying or using number = 0
-     will not check against nick floods
-
-
-channel set <chan> +/-<setting>
-    There are many different options for a channel which you can
-    define. They can be enabled or disabled by a plus or minus
-    in front of them.
-    Examples:
-
-     chanset #lamest +autoop
-     This will make the bot auto-op every registered op on join
-
-     chanset #lamest +autoop -userbans
-     This will make the bot auto-op every registered op on join and
-     enforce all bans to be made through the bots console
-
-    A complete list of all available channel settings:
-
-
-     enforcebans
-      when a ban is set, kick people who are on the channel and match
-      the new ban?  (i.e., they were on the channel before the ban)
-
-     dynamicbans
-      only activate bans on the channel when necessary? (this keeps
-      the channel's ban list from getting excessively long. The bot
-      still remembers every ban, but it only activates a ban on the
-      channel when it sees someone join who matches that ban.)
-
-     userbans
-      allow bans to be made by users directly?  (if turned off, the bot
-      will require all bans to be made through the bot's console)
-
-     dynamicexempts
-      only activate exempts on the channel when necessary?  (this keeps
-      the channel's exempt list from getting excessively long. The bot
-      still remembers every exempt, but it only activates a exempt on
-      the channel when it sees a ban set matching the exempt. The exempt
-      remains active on the channel for as long as the ban is still active.
-
-     userexempts
-     allow exempts to be made by users directly?  (if turned off, the bot
-     will require all exempts to be made through the bot's console)
-
-     dynamicinvites
-      only activate invites on the channel when necessary? (this keeps
-      the channel's invite list from getting excessively long. The bot
-      still remembers every invite, but the invites are only activated
-      when the channel is set to invite only and a user joins after
-      requesting an invite. Once set the invite remains until the
-      channel goes to -i
-
-     userinvites
-      allow invites to be made by users directly?  (if turned off, the bot
-      will require all invites to be made through the bot's console)
-
-     autop
-      op users with the +o (op) flag as soon as they join the channel?
-      (hint: this is a BAD IDEA)
-
-     bitch
-      only let users with +o (op) flag be channel ops?
-
-     greet
-      say a user's info line when they join the channel?
-
-     protectops
-      re-op a user with the +o (op) flag if they get deopped?
-
-     protectfriends
-      re-op a user with the +f (friend) flag if they get deopped?
-
-     statuslog
-      log the channel status line every 5 minutes? (some people think
-      it's annoying; i think it's neat)
-
-     revenge
-      remember people who deop/kick/ban the bot, valid ops or friends, and
-      punish them? Users with +f (friend) flag are exempt from revenge
-
-     revengebot
-      this works similar to to the 'revenge' option, but it only triggers
-      if a bot got deoped, kicked or banned
-
-     autovoice
-      voice users with +v (voice) flag when they join the channel?
-
-     secret
-      prevent this channel from being listed on the botnet?  (for paranoid
-      people)
-
-     shared
-      share user channel info for this channel?
-
-     cycle
-      cycle the channel when it becomes op-less?
-
-     dontkickops
-      do you want the bot not to be able to kick +o flag users ?
-      letting them kick-flood for instance, to protect the channel against
-      clone attacks
-
-     inactive
-      prevents the bot from joining the channel (or makes it leave the channel
-      if it is already there).
-      Can be useful to make the bot leave a channel without loosing it's
-      settings (flood settings, all these "channel set" settings), user flags
-      for this channel, bans for this channel, and without affecting any
-      sharing
-
-     seen
-      respond to seen requests in the channel?  (seen module must be loaded)
-
-     nodesynch
-      allow non-ops to perform channel modes?  (Stops bot from
-      fighting with services such as ChanServ)
-
-    Please note that you can "create" your own channel setting in
-    tcl (see tcl-commands.doc for a howto)
-
-
-The following setting are used as default values when you .+chan #chan or .tcl
-channel add #chan. Look in the section above for explanation on every option.
-
-set global-flood-chan 10:60
-set global-flood-deop 3:10
-set global-flood-kick 3:10
-set global-flood-join 5:60
-set global-flood-ctcp 3:60
-set global-flood-nick 5:60
-
-set global-chanmode "nt-likm"
-set global-stopnethack-mode 0
-set global-revenge-mode 1
-
-set global-chanset {
-        -autoop         -autovoice
-        -bitch          +cycle
-        +dontkickops    +dynamicbans
-        +dynamicexempts +dynamicinvites
-        -enforcebans    +greet
-        -inactive       -nodesynch
-        -protectfriends +protectops
-        -revenge        -revengebot
-        -secret         -seen
-        +shared         +statuslog
-        +userbans       +userexempts
-        +userinvites
-}
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.channels
diff -u /dev/null eggdrop1.6/doc/settings/mod.channels:1.1
--- /dev/null	Sun Dec 16 08:37:33 2001
+++ eggdrop1.6/doc/settings/mod.channels	Sun Dec 16 08:37:23 2001
@@ -0,0 +1,305 @@
+##### CHANNELS MODULE #####
+
+This module provides channel related support for the bot. Without it,
+you wont be able to make the bot join a channel or save channel
+specific userfile information.
+
+This module requires: none
+
+Put this line into your eggdrop configuration file to load the channels module:
+
+loadmodule channels
+
+There are also some variables you can to set in your config file:
+
+set chanfile "LamestBot.chan"
+    Enter here the filename where dynamic channel settings are stored.
+
+
+set ban-time 120
+    Set here how long temporary bans will last (in minutes). If you
+    set this setting to 0, the bot will never remove them.
+    Valid settings are 0-infinite.
+
+
+set exempt-time 60
+    Set here how long temporary exempts will last (in minutes). If you
+    set this setting to 0, the bot will never remove them. The bot will
+    check the exempts every X minutes, but will not remove the exempt if
+    a ban is set on the channel that matches that exempt. Once the ban is
+    removed, then the exempt will be removed the next time the bot checks.
+    Please note that this is an IRCnet feature.
+    Valid settings are 0-infinite.
+
+
+set invite-time 60
+    Set here how long temporary invites will last (in minutes). If you
+    set this setting to 0, the bot will never remove them.
+    The bot will check the invites every X minutes, but will not remove
+    the invite if a channel is set to +i. Once the channel is -i then
+    the invite will be removed the next time the bot checks.
+    Please note that this is an IRCnet feature.
+    Valid settings are 0-infinite.
+
+
+set force-expire 0
+    Set this setting to 1 if you want your bot to expire bans/exempts/invites set
+    by other opped bots on the channel.
+    Valid settings are 0 for OFF and 1 ON.
+
+
+set share-greet 0
+    Set this setting to 1 if you want your bot to share user greets with other
+    bots on the channel if sharing user data.
+    Valid settings are 0 for OFF and 1 ON.
+
+
+set use-info 1
+    Set this setting to 1 if you want to allow users to store an info line.
+    Valid settings are 0 for OFF and 1 ON.
+
+
+channel add #channel { SETTINGS }
+    Add each static channel you want your bot to sit in using this command.
+    There are many different possible settings you can insert into this
+    command, which are explained below.
+
+    chanmode +/-<modes>
+       This setting makes the bot enforce channel modes. It will always add
+       the +<modes> and remove the -<modes> modes.
+
+    idle-kick 0
+       This setting will make the bot check every minute for idle
+       users. Set this to 0 to disable idle check.
+       Valid settings are 0 for OFF and 1 ON.
+
+    stopnethack-mode 0
+       This setting will make the bot de-op anyone who enters the channel
+       with serverops. There're seven different modes for this settings:
+         0 turn off,
+         1 isoptest (allow serverop if registered op)
+         2 wasoptest (allow serverop if op before split)
+         3 allow serverop if isop or wasop
+         4 allow serverop if isop and wasop.
+         5 If the channel is -bitch, see stopnethack-mode 3
+           If the channel is +bitch, see stopnethack-mode 1
+         6 If the channel is -bitch, see stopnethack-mode 2
+           If the channel is +bitch, see stopnethack-mode 4
+       Valid settings are 0-6.
+
+   revenge-mode 1
+      This settings defines how the bot should punish bad users when
+      revenging. There are four possible settings:
+        0 Deop the user.
+        1 Deop the user and give them the +d flag for the channel.
+	2 Deop the user, give them the +d flag for the channel, and kick them.
+        3 Deop the user, give them the +d flag for the channel, kick, and ban them.
+      Valid settings are 0-3.
+
+   aop-delay (minimum:maximum)
+       This is used for autoop and autovoice. If an op or voice joins a channel
+       while another op or voice is pending, the bot will attempt to put both
+       modes on one line.
+         aop-delay 0   No delay is used.
+         aop-delay X   An X second delay is used.
+         aop-delay X:Y A random delay between X and Y is used.
+
+    need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
+       This setting will make the bot run the script enclosed in brackets
+       if it does not have ops. This must be shorter than 120 characters.
+       If you use scripts like getops.tcl or botnetop.tcl, you don't need
+       to set this setting.
+
+    need-invite { putserv "PRIVMSG #lamest :let me in!" }
+       This setting will make the bot run the script enclosed in brackets
+       if it needs an invite to the channel. This must be shorter than 120
+       characters. If you use scripts like getops.tcl or botnetop.tcl, you
+       don't need to set this setting.
+
+    need-key { putserv "PRIVMSG #lamest :let me in!" }
+       This setting will make the bot run the script enclosed in brackets
+       if it needs the key to the channel. This must be shorter than 120
+       characters. If you use scripts like getops.tcl or botnetop.tcl, you
+       don't need to set this setting
+
+    need-unban { putserv "PRIVMSG #lamest :let me in!" }
+       This setting will make the bot run the script enclosed in brackets
+       if it needs to be unbanned on the channel. This must be shorter than
+       120 characters. If you use scripts like getops.tcl or botnetop.tcl,
+       you don't need to set this setting
+
+    need-limit { putserv "PRIVMSG #lamest :let me in!" }
+       This setting will make the bot run the script enclosed in brackets
+       if it needs the limit to be raised on the channel. This must be
+       shorter than 120 characters. If you use scripts like getops.tcl or
+       botnetop.tcl, you don't need to set this setting
+
+    flood-chan 10:60
+       Set here how many channel messages in how many seconds from one
+       host constitutes a flood. Setting this to 0 or 0:0 disables
+       flood protection for the channel.
+
+    flood-deop 3:10
+       Set here how many deops in how many seconds from one host constitutes
+       a flood. Setting this to 0 or 0:0 disables deop flood protection for
+       the channel.
+
+    flood-kick 3:10
+       Set here how many kicks in how many seconds from one host constitutes
+       a flood. Setting this to 0 or 0:0 disables kick flood protection for
+       the channel.
+
+    flood-join 5:60
+       Set here how many joins in how many seconds from one host constitutes
+       a flood. Setting this to 0 or 0:0 disables join flood protection for
+       the channel.
+
+    flood-ctcp 3:60
+       Set here how many channel ctcps in how many seconds from one host
+       constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
+       protection for the channel.
+
+    flood-nick 5:60
+       Set here how many nick changes in how many seconds from one host
+       constitutes a flood. Setting this to 0 or 0:0 disables nick flood
+       protection for the channel.
+
+
+channel set <chan> +/-<setting>
+    There are many different options for channels which you can
+    define. They can be enabled or disabled by a plus or minus
+    in front of them.
+
+    A complete list of all available channel settings:
+
+     enforcebans
+       When a ban is set, kick people who are on the channel and match
+       the ban?
+
+     dynamicbans
+       Only activate bans on the channel when necessary? This keeps
+       the channel's ban list from getting excessively long. The bot
+       still remembers every ban, but it only activates a ban on the
+       channel when it sees someone join who matches that ban.
+
+     userbans
+       Allow bans to be made by users directly? If turned off, the bot
+       will require all bans to be made through the bot's console.
+
+     dynamicexempts
+       Only activate exempts on the channel when necessary? This keeps
+       the channel's exempt list from getting excessively long. The bot
+       still remembers every exempt, but it only activates a exempt on
+       the channel when it sees a ban set that matches the exempt. The
+       exempt remains active on the channel for as long as the ban is
+       still active.
+
+     userexempts
+       Allow exempts to be made by users directly? If turned off, the
+       bot will require all exempts to be made through the bot's console.
+
+     dynamicinvites
+       Only activate invites on the channel when necessary? This keeps
+       the channel's invite list from getting excessively long. The bot
+       still remembers every invite, but the invites are only activated
+       when the channel is set to invite only and a user joins after
+       requesting an invite. Once set, the invite remains until the
+       channel goes to -i.
+
+     userinvites
+       Allow invites to be made by users directly? If turned off, the
+       bot will require all invites to be made through the bot's console.
+
+     autop
+       Op users with the +o flag as soon as they join the channel?
+       This is insecure and not recommended.
+
+     bitch
+       Only let users with +o) flag be opped on the channel?
+
+     greet
+       Say a user's info line when they join the channel?
+
+     protectops
+       Re-op a user with the +o flag if they get deopped?
+
+     protectfriends
+       Re-op a user with the +f flag if they get deopped?
+
+     statuslog
+       Log the channel status line every 5 minutes? This shows the bot's
+       status on the channel (op, voice, etc.), The channel's modes, and
+       the number of +m/+o/+v/+n/+b/+e/+I users on the channel. A sample 
+       status line follows:
+       
+       [01:40] @#lamest (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
+
+     revenge
+       Remember people who deop/kick/ban the bot, valid ops, or friends
+       and punish them? Users with the +f flag are exempt from revenge.
+
+     revengebot
+       This is similar to to the 'revenge' option, but it only triggers
+       if a bot gets deopped, kicked or banned.
+
+     autovoice
+       Voice users with the +v flag when they join the channel?
+
+     secret
+       Prevent this channel from being listed on the botnet?
+
+     shared
+       Share channel-related user info for this channel?
+
+     cycle
+       Cycle the channel when it has no ops?
+
+     dontkickops
+       Do you want the bot not to be able to kick users who have the +o 
+       flag, letting them kick-flood for instance to protect the channel
+       against clone attacks.
+
+     inactive
+       This prevents the bot from joining the channel (or makes it leave
+       the channel if it is already there). It can be useful to make the
+       bot leave a channel without loosing it's settings, channel-specific
+       user flags, channel bans, and without affecting sharing.
+
+     seen
+       Respond to seen requests in the channel?  The seen module must be
+       loaded for this to work.
+
+     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.
+
+
+The following settings are used as default values when you .+chan #chan or .tcl
+channel add #chan. Look in the section above for explanation of every option.
+
+set global-flood-chan 10:60
+set global-flood-deop 3:10
+set global-flood-kick 3:10
+set global-flood-join 5:60
+set global-flood-ctcp 3:60
+set global-flood-nick 5:60
+
+set global-chanmode "nt-likm"
+set global-stopnethack-mode 0
+set global-revenge-mode 1
+
+set global-chanset {
+        -autoop         -autovoice
+        -bitch          +cycle
+        +dontkickops    +dynamicbans
+        +dynamicexempts +dynamicinvites
+        -enforcebans    +greet
+        -inactive       -nodesynch
+        -protectfriends +protectops
+        -revenge        -revengebot
+        -secret         -seen
+        +shared         +statuslog
+        +userbans       +userexempts
+        +userinvites
+}
\ No newline at end of file
----------------------- End of diff -----------------------



More information about the Changes mailing list