engelsk/dansk oversættel

en der vil oversætte dette for mig???

Editing the config file
Previous versions of the 1.6 series of Eggdrop came with eggdrop.simple.conf, eggdrop.advanced.conf, and eggdrop.complete.conf, with the simple one being the best sample configuration file for new users. This has been changed since 1.6.13, and there is now only the single, complete sample config eggdrop.conf. While this makes things simpler for developers and helpers, the complete config is over 1000 lines long and can be overwhelming for people new to Eggdrop. I will soon be releasing a version of my simple.conf (which I originally wrote for Eggdrop 1.3/1.4) for 1.6, but in the meantime you're stuck with editing the complete config file. If you want to take full advantage of all Eggdrop has to offer, you will eventually need to spend the extra time it takes to go through and understand many of the options in the complete config file anyway.

You should first rename the sample config file to something other than "eggdrop.conf". Giving it the name of the bot's nick (e.g. NiceBot.conf) is quite common. In the config file, you set up the IRC servers you want the bot to use, the channels you want the bot to be in, and set Eggdrop's options to suit your needs. Eggdrop has many options to configure, and editing the configuration file can take some time. I recommend you go over the entire config file to ensure the bot will be configured properly for your needs. All of the options in the config file have written explanations - be sure to read them carefully. Some of them can be a little bit vague, though.

If you're editing the config file on your system (usually a better idea than editing it on the shell as that can be rather cumbersome) you'll need to upload it to your bot's directory when you're done.

Below I elaborate on and make some recommendations for many of the settings, but it is not a complete list of settings. You'll probably notice many of the options are commented out (i.e. preceded by the # (hash) character) - a commented out setting can either mean the setting is not used or it's set to the default setting. You can uncomment the setting by removing the hash. Many of the options can be set to either 0 or 1 - 0 typically means the option is disabled, while 1 means enabled.

Note that if you're using a version of Eggdrop older than 1.3.27, some of the settings below may not apply -- if it's not in the complete sample config that comes with your version of Eggdrop, then the setting is not supported. If you're editing my simple.conf rather than the complete config file, you can skip the descriptions below as they mainly cover many of the more complex options not available in simple.conf.

set username: if your shell runs identd (most do), then you should set this to your account login name.

set my-hostname and set my-ip: you'll need to set one of these if you want your bot to use a vhost. The my-hostname setting is the vhost, e.g. linux.niceshells.net, while my-ip is the IP address of the vhost, e.g. 206.343.63.217. You don't need to set both of these, but I recommend you do so as it can help if the shell is having problems with DNS. Setting these can also help solve userfile transfer problems.

logfile: keeping logs is a good idea. Generally, you should have one log for bot stuff, and one log for each of your channels. For bot stuff, add the line logfile mcobxs * "botnick.log" to the config. For channels, add logfile jkp #donkeys "#donkeys.log", logfile jkp #horses "#horses.log", etc. Make sure you remove the sample logfile lines for the channel #lamest. If you'd like to put your logfiles in their own directory, specify the directory in the log name (e.g. logfile jkp #donkeys "logs/#donkeys.log" to write the logfiles in the /logs directory).

set sort-users: by default, userfile entries are sorted in the order each user is added, from first to last. Setting this to 1 will make the userlist sort itself based on user flags. Both sorting methods can be just as useful as the other - I recommend leaving this set to 0 to start with.

listen 3333 all: you will definitely want to change this. Choose a port between 5000 and 65535. You can disable this by commenting it out, but that will prevent any telnet connections to the bot (you won't be able to use the bot as a hub, won't be able to telnet to the bot, and the bot won't respond to /ctcp botnick CHAT requests).

set protect-telnet: setting this to 1 is strongly recommended for security reasons.

set require-p: this is a useful feature allowing you to give party line access on a user-specific basis. I recommend setting it to 1.

set stealth-telnets: when you telnet to your bot, it will usually display the bot's nickname and version information. You probably don't want people seeing this info if they do a port scan on the bot's shell. Setting this to 1 will prevent the bot from displaying its nickname and version when someone telnets to it.

set dcc-flood-thr: this setting determines the number of lines per second you can send to the party line before being booted. It can be a pain in the butt when you want to paste multiple lines on the party line, so you may want to increase this to something like 5 or 10.

set hourly-updates: it's a good idea to change this from the default setting of 00, since lots of other bots are already using 00 and putting a lot of stress on the shell at that time. Choose something that isn't a multiple of 10 (e.g. 03, 37, and 56 are examples of good settings).

set notify-newusers: set this to the nick you will have on the bot. This setting isn't really used if you have learn-users switched off.

set owner: you should only put one person in this list - yourself. Set it to the nick you will have on the bot. Do NOT leave it set to the default "MrLame, MrsLame".

set default-flags: these are the flags automatically given to a user when they introduce themselves to the bot (if learn-users is on) or when they're added using .adduser. If you don't want the user to be given any flags initially, set this to "" or "-".

set remote-boots: the default setting of 2 can result in annoying boots from the party line (which is kind of like being kicked from an IRC channel). You should probably set this to 0 or 1.

unbind dcc n tcl *dcc:tcl and unbind dcc n set *dcc:set: these lines unbind the .tcl and .set commands. It's a good idea to leave these lines alone, as the .tcl and .set commands can be a security risk since they provide access to your shell account through the bot. These commands are only really useful if you plan on writing Tcl scripts.

set must-be-owner: if you have the .tcl and .set commands enabled, you should definitely set this to 1. In 1.3.26 and later, you can set it to 2 for even better security.