PayPal Acceptance Mark

Join us on Facebook

Client portal

Eggdrop Basic commands

Basic Eggdrop bot commands. All of these commands have to be run in the DCC chat.

Adduser: Make sure the person that you want to add to the bot join the channel where your bot located and then type: .adduser nick

If you want to give the person op type: .chattr nick +o

After that the user has to set the password to the bot type: /msg botnick pass your-new-password

if you want to give the person voice type: .chattr nick +f

Remove user: .-user nick

List all of the users you have added: .match * 1000

for the user to get op from the bot type: /msg botnick op pass YOUR-PASSWORD replace YOUR-PASSWORD with password you have setup.

For more eggdrop commands you can use from DCC just type: .help

Latest News - Anope 2.0.1 Release

We are proud to announce that after five years of development our latest stable release, Anope 2.0, is now available for download.

With this release we are deprecating the 1.8 branch and no longer recommend users use it.

Overview of changes from 1.8 to 2.0:

Use an account style system instead of the old NSNickTracking option, which allows you to stay logged in no matter what nick you are on.
Fantasy support for all commands.
Can assign core pseudo clients (such as ChanServ) to channels.
A built in web panel.
Persistent channels, which allows services bots to stay in empty channels.
Channel passwords replaced with founder level access (QOP, or the FOUNDER access level).
OWNER access levels added, defaults to access level 9999.
The option to use a flags based channel access system.
Ability to authenticate via SSL certificates
Autojoin channels on authentication (ns_ajoin)
Significantly more advanced logging system, choose what is logged and where it is logged.
Support for other optional database backends, such as SQL and Redis.
Granular command configuration. Configure which command is on what service, what it's called, and who can use it.
Configurable opertypes, which allows defining new services operator levels (Root, Admin, Oper, etc.) and what permissions each has.
Ability to authenticate users against external databases, such as by SQL or LDAP.
Capability to switch between different encryption methods.
DNSBL support.


Installation instructions for Linux/UNIX:

Anope 2 requires CMake to be built. On most systems you can simply install the package from your package manager, eg. sudo apt-get install cmake or sudo yum install cmake.

First, enable any extra modules you want by executing the 'extras' script. Extra modules generally depend on other libraries, such as MySQL, and are not enabled by default due to their dependencies. Then run:

./Config
cd build
make
make install

Upgrading instructions:

1) Install Anope 2 to a separate directory from your old install (such as ~/services2)

2) Copy 1.8's databases to the 'data' directory of your new install.

3) Configure services, the configuration files are located in the 'conf' directory.

Anope 2 uses a different configuration file format from 1.8, you will have to reconfigure them completely.
Use your old configuration as a reference.

4) While configuring, be sure to load db_old, which loads the old 1.8.x databases, and db_flatfile, which writes out the new Anope 2 database.
Ensure that the hash method in db_old's configuration block is the same encryption method that you are currently using on 1.8.
Load the correct encryption module, which is the same one configured in db_old.

5) Start services. Once you confirm your database has been successfully imported, comment or remove db_old from the configuration file, so that the next time services restart, they will load the newer database.

Third party modules, such as most of the ones found on on the Modsite, that are written for 1.7.x or 1.8.x
will not work with Anope 2. However, many of the features of the most popular 1.8 modules have been included in the Anope 2 release, so you may find you no longer need your extra modules. If it is unclear to you whether or not a given feature is in Anope 2, come ask us.

Join our IRC channel at irc://irc.anope.org/anope for questions or comments.

If you have lost your HELPDESK password you can easily request a password reminder by going to the   FORGOT PASSWORD  on the Inetking HelpDesk Client Area page. On the password reminder page, enter the email address that you used to register your account and  you will receive an email with instructions on how to reset your password.
NOTE: Due to Security of your accounts all passwords are required to have upper and lower case letters plus numbers and special characters. The use words in your password is also not allowed for the same reason. If you try to reset your password and do not use the password rules it will automatically reject it and force you to try again.
 
If you have lost your Shell/IRCD account password, log into the Inetking HelpDesk and submit a support ticket. You will receive an email from one of our support staff members with your new temporary pasword and instructions on how to change your password.

Thank You
Inetking Staff
There are many reasons why your account may have gone off line, but if you can't login to the box to bring them back up it could be one of 2 things.

1) you haven't paid your bill and the 10 day grace period may have gone by. We feel that this is more than enough time to bring your account up to date considering most company's only give you 48 hours. Check the status of your account in your helpdesk client area. If it has been turned off it will tell you there. It is your responsibility to make sure your account email address is up to date, not getting your bill because of your email not being correct is not our responsibility.

2) The box may have gone off line and the network may not allow you to get to the box. If you can get to the box but cannot login refer to number 1.

If neither of the above apply then put in a support ticket letting us know your name and account login and we will check it for you. If you have forgot your pass word put in a support ticket asking for it to be reset.

If you have forgot your helpdesk pass word you can get a reset email. Make sure your email is always up to date, because this is how you can reset your account and put in support tickets. 

During the signup process it asks if you would like to add a custom vhost to your account. Since until you are an approved customer you cannot see our vhost list. (This is to protect our customers form attacks) Once you have signed up you will be able to see the vhost list. From that list pick the domain you like and create your custom vhost with it. Each word in the vhost host must have a . after it. An example is i.like.my.domain.com We assign the ip to it. once you have created your custom vhost open a support ticket letting us know what you pick so we can set it up for you. Once we set it up we will answer the ticket with vhost and ip number assigned. You will than be able to use it. It can take 12- 24 hours for it to propagate and start to work once it is setup. Note: A custom vhost is a vhost other than what is our our list. All vhost on our list are free for any customer to use.
When I try to signup for an account your signup form asks for a domain but I don't have one.
This part of the signup process in the software and cannot be turned off. We know that most people that signup for a shell account do not own a domain. All you need to do is to put something as simple as your name in the box and it will go to the next step in the signup process. Since domains are not added to our system when the account is created this will not effect your account in anyway.

We hope this will help in some of the questions we are getting about the domain block during signup.

"How do I install my eggdrop?":

On the FreeBSD or BSD systems, when you type 'make config' or 'make' or 'gmake',
it may respond 'make: Permission denied'
This is caused by a bug in FreeBSD (and possibly other BSDs as well).
A simple 'cd .', or changing to a different directory and then changing back, usually fixes this.
Follows these steps:
1) cd .
2) make
3) cd ~/eggdrop (change back to your eggdrop directory)
3) make config

Some Eggdrop setups will vary to the commands used for setup. Please read your README file for more information.
Eggdrop automatically notify Nickserv

First register your Eggdrop nick with nickserv.
Via DCC chat on your eggdrop bot type:
Code:
.msg nickserv REGISTER your-password my@email.ltd


Second, Add this TCL lines to your eggdrop.conf:
Code:
# This is a Tcl script to be run immediately after connecting to a server.
bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
  global botnick
  putquick "MODE $botnick +iR-ws"
  putquick "privmsg nickserv :identify your-password"
}


Eggdrop is an IRC bot, written in C. If you don't know what IRC is, this is probably not what you're looking for! Eggdrop, being a bot, sits on a channel and takes protective measures: to keep the channel from being taken over, to recognize banished users or sites and reject them, to recognize privileged users and let them gain ops, etc. One of the more unique features of eggdrop is its "partyline", accessible via DCC chat, which allows you to talk to other people lag-free. Consider it a multi-way DCC chat, or a miniature IRC (complete with channels). You can link up with other bots and expand the partyline until it actually becomes something very much like IRC, in fact. Eggdrop is always being improved and adjusted because there are bugs to be fixed and features to be added. In fact, it existed for several years as v0.7 - v0.9 before finally going 1.0. This version of eggdrop is part of the 1.3 tree. A valiant effort has been made to chase down and destroy bugs. It is definitely nowhere near as buggy as the ircII client. Crashes should be rare and surprising (but aren't they always? [surprising anyway]).
Features

Eggdrop is, as far as I know, the most advanced IRC robot available. It has been under development since December 1993, and, unlike most other bots, it is still regularly updated. Its features include:

Complete channel protection, customizable via config file: permanently store a ban list with comments, etc user records saved on disk and alterable via dcc chat: each user can have a password, a list of valid hostmasks, a set of access flags, etc

The ability to "learn" new users (if you choose to have the bot do so) by letting users /MSG the bot "hello" and granting them automatic access of whatever type you specify (or even no access at all)

A "party line" available through dcc chat or telnet, with multiple channels, giving you the ability to talk to people without being affected by netsplits

Console mode: you can view each channel through dcc chat or telnet,

Selectively looking at mode changes, joins and parts, channel talk, or any combination of the above

A file system where people can upload and download files, in an environment that looks and acts (for the most part) like a typical unix system -- plus the ability to mark directories as hidden/ unaccessable to people without certain user flags

Bot network: link two or more bots together for a party line that can stretch not only across channels, but across irc networks (one bot on Efnet, one bot on Undernet, etc)

Script language: commands and features can be added to the bot on the fly, by means of the TCL script language, giving you the power of TOTAL customization of your bot -- similar to ircII script ability to look almost exactly like an ircII client -- sadly, this is almost a necessity these days for bots

Slices, dices, and juliannes fries

Now its able to encypt password files

More detail about eggdrop: Eggdrop Documentation Index
Installing
The following is just an example of how to upload and install your bot.
1) FTP your eggdrop to your shell.
2) After you finish uploading the eggdrop file, You have to unzip the file. Type:
tar xvfz eggdrop1.6.19+ctcpfix.tar.gz  <--- Example eggdrop file name.
3) After you finish unzip the files. Change the directory to eggdrop1.6.19, type:
cd eggdrop1.6.19
4) Then you have to configure the file, type:
./configure
5) the next step is make the eggdrop. I choose make config to compiles all modules
Type: make config (compiles all modules) or make iconfig (allows you to select the modules to compile).
6) the next step is make the eggdrop, type:
make
7) Moreover, You have to move the eggdrop to the directory where you going run the eggdrop. Type:
make install DEST=~/botdir
8) Now you are finish making the eggdrop. The next step that you want to do is configure the eggdrop.conf. You can configure the eggdrop.dist.conf by download the file using FTP and edit the file using Cooledit or Notepad (You can also edit it in your shell by using "nano") After you finish editing the file, All you have to do is upload the file to your eggdrop directory and run the eggdrop file.  Type:
./eggdrop -m eggdrop.conf

Crontab

Most people keep asking me why my bots are not coming to my channel anymore after your server has been restarted. In this case, you need crontab to make your job easier. With a crontab, you don't have to login to the server over and over again to start your eggdrop bot. Crontab will help you to check your eggdrop bot every minute. Moreover, Eggdrop has become more stable with time, thanks mostly to people reporting bug details and helping find places where it crashes.However, there are still a -few- places where things aren't perfect. Few if any things in life are. Also, most systems go down from time to time. These things cause your bot to disappear from IRC, and you have to restart it. The eggdrop source file includes a csh script called 'botchk' that will help keep the bot online. It will make the machine check every ten minutes as to if your bot is still running. To use it, you have to add a line to your crontab.

First, edit 'botchk' and change the directory and command line parameters so that it will be able to start up your bot. Then, add this line to your crontab:

0,10,20,30,40,50 * * * * /home/mydir/botchk

If you don't want to get emails from cron, put this:

0,10,20,30,40,50 * * * * /home/mydir/botchk >/dev/null 2>&1

Naturally, you need to change the path to the correct path for botchk. If you've never used crontab before, here is a simple way to add that line: Create a new file called 'mycron' and put the above line into it. Then, from your shell prompt, type crontab mycron That will create a new crontab entry for you, with a line that runs botchk every ten minutes. Botchk will then restart the bot when necessary (and send you email informing you - if setup).

The simple and easy step to install eggdrop is using autobotchk.

Use autobotchk to install crontab on your shell:
Type: autobotchk --prefix=/www0/login/eggdrop -nE --time=15 eggdrop.conf

You need to find your eggdrop path.
1) change directory to your eggdrop directory.
For example: cd eggdrop
2) type: pwd
The pwd command will tell you the eggdrop path
and then enter the eggdrop path --prefix=/www0/login/eggdrop

Contact support@inetking.net if you are having problem installing crontab.

Python Bot Configuration for Vhost Connection.

 

Since all IRC items are required to use a VHOST to connect to the various IRC networks try the following to get your bot to connect to a vhost.

After you have setup your bot create a ZNC or BNC using the vhost. Then set your ZNC, BNC for the channels you want your bot to connect to. Then set your bot to send PASS bot:password to the ZNC, BNC. Your bot should then connect to the ZNC, BNC connecting it to the channels you wanted it to connect to.

Solution was giving by one of our customers in order to help others.

As more information on the python bot becomes available to us we will add it to our help area.

I have tried to setup irssi in my shell but I keep getting an error. Can you help me?

The error we see most is the following. when you get to the make install

[user@box:~/irssi-0.8.16-rc1] make install
./irssi-version.sh . | cmp -s - irssi-version.h || ./irssi-version.sh . >irssi-version.h
make install-recursive
Making install in src
Making install in lib-config
../../build-aux/install-sh -c -d '/include/irssi/src/lib-config'
mkdir: /include: Permission denied
mkdir: /include: Permission denied
*** Error code 1

Stop in /usr/home/username/irssi-0.8.16-rc1/src/lib-config.
*** Error code 1

Stop in /usr/home/username/irssi-0.8.16-rc1/src/lib-config.
*** Error code 1

Stop in /usr/home/username/irssi-0.8.16-rc1/src.
*** Error code 1

Stop in /usr/home/username/irssi-0.8.16-rc1.
*** Error code 1

Stop in /usr/home/username/irssi-0.8.16-rc1.

The fix is simple. You just need to make sure when you install you install it as a normal user. Use the following commands in order.

./configure --prefix=/home/username/irssi/usr  (Where username is put your username)
make
make install

Using these commands will run the whole install without error.

Once you have done this just setup your .conf files using one of our vhosts and you are off and running.

We hope this will help you in installing your irssi in your shell.

Powered by
Secured by PayPal
How PayPal Works

Join us on Facebook

Copyright © 1998 Inetking Internet Service and Mystic Technologies, LLC