SHARE
TWEET

Untitled

a guest Jul 17th, 2017 167 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. <?xml version='1.0'?>
  2.  
  3. <!-- Lycanobot's config file.
  4.     Put all your bot's config here.
  5.     True = true = Yes = yes = 1, and False = false = No = no = 0 -->
  6.  
  7. <lycaconf>
  8.   <!-- These settings control how and where the bot has to connect.
  9.     | Most of them are self-explicit.
  10.     | "use_random_night_channel" make the night channel more hidden (thus
  11.     | more secure) appending a minus and 8 random charachters to its name,
  12.     | changing it for each game. For instance to "#Loups-garous-nuits".
  13.     | "active" set the bot awake. May be changed by the (de)activate commands.
  14.     | "timeout" is the ping timeout limit that makes the bot to reconnect.
  15.     | The bot had to be OP on both day_channel and night_channel. -->
  16.   <conn server="irc.facemon.net" port="6667" use_SSL="no"
  17.         day_channel="#Loups-garous" night_channel="#Loups-garous-nuit"
  18.         use_random_night_channel="yes"
  19.         active="yes" timeout="300" />
  20.  
  21.   <!-- Who is the bot? Put here his nick, irc name and user name.
  22.       You may also put here the "op_user" and "op_passwd" attributes if you
  23.       want the bot to ask to be an IRC Operator when it connects. -->
  24.   <identity nick="lycanobot" irc_name="lycanobot"
  25.            user_name="lycanobot vs 0.1.2"/>
  26.  
  27.   <admins>
  28.     <!-- The admins' identifiers.
  29.       | They can do everything, including sensitive commands like reloadconf
  30.       | and talkserv. Only for people you fully trust into.
  31.       | There is no need to put the bot itself here, it's just some god :)
  32.       | Here you can use the <mask> or <regnick> tag to specify who is admin.
  33.       | <regnick> means a registered nick (done the nick service, see <hacks>
  34.       | below). Just /whois someone to see who is it and put it here. Ex:
  35.       |
  36.       | <mask>*!some_ircname@some_address</mask>
  37.       | <mask>*!*@*.domain.org</mask>
  38.       | <regnick>Jah</regnick>                                             -->
  39.     <!-- Some people you fully trust into... -->
  40.     <regnick>Fire</regnick>
  41.   </admins>
  42.  
  43.   <moderators>
  44.     <!-- The moderators' identifiers.
  45.       | Exaclty the same as <admins> above (use <mask> or <regnick>), but this
  46.       | time for the moderators. Such people are only able to moderate games
  47.       | (stop game, change settings, and (de)activate the bot). Especially,
  48.       | they cannot run sensitive commands like reloadconf and talkserv    -->
  49.     <!-- Some people you normally trust into... -->
  50.   </moderators>
  51.  
  52.   <!-- Ignored users.
  53.     | Any users nicks which are in the day and/or night channel, but you want
  54.     | to be ignored by the bot. He will not see they are in the channel with
  55.     | him. Useful for ChanServ and others bots.
  56.     | Separate multiple nicks with a comma, e.g. <ignore>foo,bar</ignore>  -->
  57.   <ignore>ChanServ</ignore>
  58.  
  59.   <!-- The werewolves players proportion.
  60.     | It's a number between 0 and 1. It can also be a fraction.
  61.     | E.g. with <werewolves proportion="1/3" /> and 6 players
  62.     | you'll get 2 werewolves and 4 villagers.
  63.     | Note that 0.22 matches the official game advices. -->
  64.   <werewolves proportion="0.22" />
  65.  
  66.   <!-- The identification mode.
  67.     | This var configures the way the bot will identify real users from their
  68.     | clones. Each user and his clones share the same personal information
  69.     | and settings.
  70.     |
  71.     | The bot is able to use the following informations to identify a user:
  72.     | nick, user, host, domain, server, realname, regnick
  73.     | Which refers to :
  74.     | the nick, the /whois result user@host.domain, the server name,
  75.     | the real name, and the nick the user registered with.
  76.     | When host is an IP, domain is unavailable.
  77.     |
  78.     | Some of these informations may not be available: domain and regnick.
  79.     | That's why the bot is able to try some combinations before finding one
  80.     | with all the informations requiered available. It will begin with try="1"
  81.     | then try="2" and so on.
  82.     |
  83.     | If the bot is unable to identify a user because it can't collect
  84.     | the informations you specify (in all the trys), the settings of that user
  85.     | will remain only until he disconnects, and he will be considered as a new
  86.     | user if he reconnects (the bot will welcome him etc.).
  87.     |
  88.     | Some examples:
  89.     |  <ident try="1" use="user host domain" /> // This is the default : use
  90.     |  <ident try="2" use="user host" />        // user@domain.tld or user@IP
  91.     |
  92.     |  <ident try="1" use="regnick"             // Use registration nick, or
  93.     |  <ident try="2" use="user host domain"    // this, for unregistered users
  94.     |
  95.     |  <ident try="1" use="user domain" />      // Work around dynamic IPs,
  96.     |  <ident try="2" use="user" />             // but it's unsecure
  97.     |
  98.     |  <ident try="1" use="nick" />             // On a trustworthy IRC network
  99.   -->
  100.   <identification>
  101.     <ident try="0" use="regnick" />
  102.     <ident try="1" use="user host domain realname" />
  103.     <ident try="2" use="user host realname" />
  104.   </identification>
  105.   <!-- Quit recovery system
  106.     | When a player quits during a game, lycanobot can continue the game as he
  107.     | were here, until he comes backs and is recognized. Here you may set
  108.     | when you want this to happens, using <recover> tags, depending on :
  109.     |
  110.     | - the type of the quit, attribute "on", can be "part" or "quit".
  111.     | - the exit message, attribute "msg" (simple string) or "regexp" (a Perl
  112.     |   regular expression). Put an '!' (exclamation mark) before the regexp to
  113.     |   inverse its matching.
  114.     |
  115.     | In the wait="" attribute, you can also specify the maximum amount of time
  116.     | (in seconds) the bot may wait before kicking the player out of the game,
  117.     | if he havn't came back. Put zero if you don't want the bot to do that.
  118.     |
  119.     | Some examples:
  120.     |  <recover on="quit" msg="EOF From client" />    // Simple EOF
  121.     |  <recover on="quit" regexp="/^Ping timeout/" /> // Beginning with that
  122.     |  <recover on="quit" regexp="!/^Quit: /" />      // Not starting with that
  123.     |  <recover on="part" msg="Leaving" />            // Standard leaving  -->
  124.   <quit_recovery wait="130">
  125.  
  126.   </quit_recovery>
  127.  
  128.   <!-- IRC Hacks
  129.     | Here you tell the bot to use some specials IRC features.
  130.     | Available hacks includes:
  131.     | + Special commands, using the <command>name</command> tag.
  132.     |   Lycanobot can use the SAJOIN command to force the werewolves to join
  133.     |   their channel in the beginning of a game, instead of politely inviting
  134.     |   them. Beware that you don't make sure they are ready if you force them.
  135.     |   You may put <command>sajoin</command> for that.
  136.     |  
  137.     | + Services, using the <service> tag as following:
  138.     |    <service name="the_foo_service" nick="FooServ">
  139.     |    <the_foo_service feature="bar!" do_that="yes" ...>
  140.     |
  141.     |   Supported <service> "name" attribute values are "nick" and "chan".
  142.     |   "nick" provides:
  143.     |    - the "password" attribute (to make the bot identify itself)
  144.     |    - the optionnal "say" attribute to tell the bot the message it
  145.     |      must send in case it's not the regular "IDENTIFY <password>"
  146.     |   For instance: <service name="nick" nick="NickServ" />
  147.     |                 <nick password="bad" say="AUTH lycanobot bad"/>
  148.     |   By the way, you can make the bot register with the "talkserv" command.
  149.     |
  150.     |   "chan" privides:
  151.     |    - the boolean "ask_invite" attribute to tell the bot it must
  152.     |      asks this service to invites it in the night channel
  153.     |    - the optionnal "say" attribute, to tell the bot the message it
  154.     |      must send in case it's not the regular "INVITE <#channel>"
  155.     |   For instance: <service name="chan" nick="ChanServ" />
  156.     |                 <chan ask_invite="yes" />                            -->
  157.   <hacks>
  158.    
  159.   </hacks>
  160.  
  161.   <!-- Modes
  162.     | /!\  Warning: You should not change these settings unless you know
  163.     [ ^|^           what you are doing! Defaults should be OK.
  164.     | This specify which channel and user modes the bot have to set, and when.
  165.     | "on" can be "connect", "chanop", "end_game" or "begin_game".
  166.     | "to" can be "ourself" (results in a user mode, for the bot),
  167.     |             "day_channel" or "night_channel".
  168.     | +N channel mode was needed before, but it's no longer true.
  169.     | The bot automatically sets the +i mode in the night channel, when
  170.     | everybody in it has been kicked out. It also avoid setting a mode that
  171.     | is already set.
  172.     |
  173.     | Some channel modes reminders:
  174.     | n = no external messages
  175.     | m = moderated chan, only voiced users may talk
  176.     | s = secret channel (hidden from /whois etc.)
  177.     | i = can be joined on invite only
  178.     | The unofficial +B user mode (for bots) is quite common.
  179.   -->
  180.   <modes>
  181.     <mode on="chanop"     to="day_channel">-m+n</mode>
  182.     <mode on="end_game"   to="day_channel">-m</mode>
  183.     <mode on="begin_game" to="day_channel">+m</mode>
  184.     <!-- mode +i is automatically set on begin_game in the night channel -->
  185.     <mode on="begin_game" to="night_channel">+mns</mode>
  186.   </modes>
  187.  
  188.   <!-- Talk settings.
  189.     | Handles how the bot talks and how users have to talk to it.
  190.     | For the language, see which ones are available in the messages/
  191.     | directory.
  192.     |
  193.     | "cmd_prefix" is the commands prefix character.
  194.     | E.g. with cmd_prefix="!" you'll call the command "start" saying "!start"
  195.     |
  196.     | "charset" is the charset you want the bot to both talk in and listen in.
  197.     | Default and native one is utf-8, others charsets need the Encode module.
  198.     | Additionaly, iso-* users should install the Search::Tools::Transliterate
  199.     | module to convert fancy utf-8 characters into iso equivalents, otherwise
  200.     | you would get some '?' instead (e.g. '…' gets transliterated into '...').
  201.     | Some common charsets : iso-8859-1, iso-8859-15, us-ascii, utf-8
  202.     |
  203.     | "charset_fallback", if non-empty, is the charset the bot will try to
  204.     | decode input messages in, if the above "charset" failed. Usefull on
  205.     | channels with users mixing utf8 and another charset.
  206.     |
  207.     | "decode_errors" sets what to do when it can't decode a message using
  208.     | the above "charset" and "charset_fallback". Possible values include :
  209.     | - "ignore" : messages with invalid characters will be silently ignored.
  210.     | - "keep" : invalid characters will be kept in a hex form (\xNN) and the
  211.     |            the message will be parsed.
  212.     | - "warn" : the bot will say a warning showing the problematic characters
  213.     |            in a hex form and the message will be ignored.
  214.     |
  215.     | Note : control characters are always silently stripped after decoding.
  216.     |        Also, non-multibytes charsets decoding cannot fail.
  217.  -->
  218.   <talk language="en" cmd_prefix="!"
  219.       charset="utf8" charset_fallback="iso-8859-1"
  220.       decode_errors="warn" />
  221.  
  222.   <!-- Messages settings.
  223.     | Controls for each messages types how to say them:
  224.     | - privmsg (classic irc message) or notice
  225.     | - with an eventual prefix
  226.     | By default all is sent in privmsg.
  227.     |
  228.     | Some special sequences can be used:
  229.     |  \B = start/stop blod
  230.     |  \U = start/stop underline
  231.     |  \I = start/stop italic
  232.     |  \Cxx = mIRC color number xx
  233.     |
  234.     | "to_user_char" is the completion char the bot will put after a nick
  235.     | that prefixes a message said on a channel but for this specific nick.
  236.     | E.g., with to_user_char=":" you'll get channel messages like :
  237.     | "foobar: you cannot vote against your team."
  238.  -->
  239.   <messages to_user_char=",">
  240.     <message type="error" send="privmsg" prefix="" />
  241.     <message type="info"  send="privmsg" prefix="" />
  242.     <message type="query" send="privmsg" prefix="" />
  243.     <message type="reply" send="privmsg" prefix="" />
  244.   </messages>
  245.  
  246.   <!-- Rate control. These settings prevent the bot from flooding, and let it
  247.     | readable.
  248.     |
  249.     | "talk_speed" is the talking speed in number of characters per seconds.
  250.     | "max_mode_params" is the maximum number of players the bot can mode in
  251.     | a single command. Check it in the irc server's config.
  252.     | E.g. with "3" it will voice 3 players at the same time
  253.     | using /mode +vvv player1 player2 player3
  254.     |
  255.     | "max_whois_params" is the same as "max_mode_params" but for /whois.
  256.     | /whois are currently used by the bot only if you use the regnick flag
  257.     | in the identification variables above. Otherwise /who is enougth.
  258.     | E.g. with "4" it will whois 4 players at the same time
  259.     | using /whois player1,player2,player3,player4
  260.     |
  261.     | "mode_speed" The number of modes the bot can do per seconds
  262.     | Count 4 modes for doing something like +mnsi
  263.     |
  264.     | "global_limit". Is the previous limitations are global or for each user.
  265.     | Set it if you want the bot to send a message to one user or channel
  266.     | at a time. This would not makes the bot to heavily lag if he talks
  267.     | to several users simultaneously (there is a round-robin between each
  268.     | message destination), but must be used if the irc server have
  269.     | per-user rate limitations. You should set it to "no" if you can.
  270.  -->
  271.   <rate talk_speed="20" mode_speed="1"
  272.        max_mode_params="3" max_whois_params="4"
  273.        global_limit="no" />
  274.  
  275.   <!-- Send queue control (has a superior priority than the rate contol).
  276.     | These settings prevents flooding from a lower level. You may
  277.     | exactly match the server receive queue restrictions, giving how much
  278.     | bytes in can hold, and how long it takes to be entierly emptied.
  279.     | For instance, using 1024 bytes and 6 seconds, the bot may send 1024
  280.     | bytes instantly, but then would wait 6 seconds before sending anything
  281.     | else. Also, if the bot continusly send some messages, its average rate
  282.     | will never excess 1024/6 = 170 bytes per seconds.
  283.     |
  284.     | These settings can only work with the lycanobot patched version of
  285.     | Net::IRC. To disable this feature, put a zero for one of the attributes.
  286.  -->
  287.   <sendq max_bytes_sent="512"
  288.         max_bytes_time="0" /> <!-- Disabled by default. -->
  289.  
  290.   <!-- Persistent data is stored in some XML files, so that if lycanobot stops,
  291.     | this stuff can be restored on restart.
  292.     |
  293.     | Note: Lycanobot can use a cache system not to write his data on disk
  294.     | if it do not have changed. This feature is automatically enabled
  295.     | if you have the Digest::MD5 module.
  296.     |
  297.     | "sync" You may want to save lycanobot's status on disk only after
  298.     | a given time. Thus, the bigger this time is, the less your disk will
  299.     | be used, but the more probably you can loose data if a crash happens.
  300.     | Data is always saved on proper shutdown or reboot.
  301.     | Use: -1 for full sync,
  302.     |       0 for no sync (only on shutdown/reboot),
  303.     |      or any time in seconds.
  304.  -->
  305.   <storing sync="3600" />
  306. </lycaconf>
RAW Paste Data
Top