engelsk/dansk oversættel del 2

en der vil oversætte denne teskt???


set chanfile: the chanfile allows you to store 'dynamic' channels so that the bot rejoins the channel if restarted. Dynamic channels are those you make the bot join using the .+chan command - they aren't defined in the config file. The chanfile is good if you frequently add/remove channels from the bot, but can be a pain if you only like to add/remove channels using the config file since settings stored in the chanfile with overwrite those set in the config. You can choose not to use a chanfile by setting it to "".

channel add: this is the command you use to add channels to the bot. There are lots of options for this command. Channels are added in the following format:

channel add #donkeys {
  options
}

channel set #donkeys +option -option

channel add #horses {
  options
}

channel set #horses +option -option

All the different options and channels settings are shown in the examples in the config file. Make sure you remove the example entries for #lamest and #botcentral.

set nick: this is what you use to specify your bot's nickname. I recommend against using [ ] { } \ character's in the bot's nick, since these can cause problems with some Tcl scripts, but if you'd like to use them, you'll need to precede each of those characters with a backslash in the setting, e.g. if you wanted your bot to have the nick [NiceBot], use set nick "\[NiceBot\]".

set altnick: if you want to use [ ] { } \ characters in the bot's alternate nick, follow the backslash rule described previously.

set servers: you should specify multiple servers in this list, in case the bot is unable to connect to the first server. The format for this list is shown below.

set servers {
  irc.chitchat.com:6667
  irc.talkworld.com:6665
  irc.nice.net:6667
}

Wherever possible, you should use a port other than 6667 (connect to the server and type /motd to see a list of available ports). You should use servers that allow bots (some shells have rules enforcing this), but unless your shell's policy says otherwise you may also wish to use non-bot servers as a backup in case your IRC network has very few bot servers your bot is able to connect to (but place the servers that allow bots at the top of the list).

set use-ison: leave this set to 1, as setting it to 0 will make your bot use the 'trace' command and may get your bot k:lined (banned) from a server.

set strict-host: if this is set to 0, Eggdrop will ignore the tilde in idents starting with ~. Setting it to 1 is a little more secure, but it can be a pain when it comes to user hostmask management. If you're not sure how you should set this, just leave it set to 0.

set server-cycle-wait: by default, Eggdrop waits 60 seconds between connection attempts to servers. This is quite a long time, but it is necessary to prevent 'throttling' on Undernet servers (if a server gets too many connection attempts from a particular host within a short period of time, it will block all connections from that host until there's been a break in connection attempts). If you use Undernet and you're sharing a shell with lots of other bot users, leave this set to 60. Otherwise, it's a good idea to decrease this to something like 20.

set trigger-on-ignore: setting this to 1 diminishes the usefulness of Eggdrop's ignore feature. I recommend you leave it set to 0.

set bounce-bans: setting this to 1 makes the bot remove any bans set by a server.

set bounce-modes: setting this to 1 makes the bot remove any modes set by a server.

set learn-users: this is an important setting that determines how users will be added to your Eggdrop. If set to 1, people can add themselves to the bot by sending 'hello' to it (the user will be added with the flags set in default-flags). If set to 0, users cannot add themselves - a master or owner must add them using the .adduser command.

unbind msg - hello *msg:hello and bind msg - myword *msg:hello: these allow you to change the 'hello' command to something different. Change myword to the name you the hello command you want. If you have learn-users set to 0, this command is only used for when you first introduce yourself to the bot.

unbind msg - ident *msg:ident and unbind msg - addhost *msg:addhost: these lines unbind the ident and addhost commands. You will almost certainly want to rebind the ident command, either by commenting out the unbind line (this will enable the default 'ident' msg command) or by binding it to a new command. It's a good idea to change the command for extra security. To bind it to another command, let's say 'horse', you would add the line bind msg - horse *msg:ident.

set dcc-block: although the example config file recommends you set this to 0 (turbo-dcc), this may cause DCC transfers to abort prematurely. If you'll be using DCC transfers a lot, set this to 1024.

loadmodule uptime: read my uptime module description for a better idea of what this module is for.

Finally, be sure to remove the 'die' commands from the config (there are two of them 'hidden' in various places), or the bot won't start. Once you've finished editing the config file, make sure you rename it to something other than
"eggdrop.conf" if you haven't already. Then, if you edited the config file locally, upload the config file to the directory you installed the bot.