Help Guide

(For those that don't know it all)

Designed by taycie

Based on the information provided by:

For use with new trainees

Updated: 6/12/1999

Revised to webpage format 6/19/99 by: Nicki

Why we do what we do

The purpose of BotService is to provide channel owners with a clean running (no flooding, no war bots, etc) eggdrop bot for various purposes. This bot is not a replacement for channel service, or their services bots (where applicable). We do this not on just one network but many, in fact as of this writing we are currently on something in the order of 30+ networks with over 150 eggdrop bots online.

What does this cost, and what do we want in return? Nothing! We do not charge for our services nor do we ask for pay. Why do we do this you ask? Because *smile* we can. Our pay comes from satisfied channel owners. We do this for many reasons. To provide not only the channel owner but also the network itself with a reliable bot provider that maintains the bots. In doing so it is a more controlled and dependable service than all users on a network running various versions of bots. This also provides the network with a way to better watch and control what is happening on their network.

BotService.Org Staff List




Founder of BotService

BotService Global Admin

BotService WebMistress

TCL Assistant

Keeper of the Paddle

Evil Bitch Queen of the Bots


BotService Global Admin

BotService Routing Admin

TCL Coordinator

Evil Bitch Queen's Devoted Slave


BotService Global Admin

Applications Admin

Training Coordinator

TCL Assistant

Evil Bitch Princess of the Bots


BotService Global Admin

Assistant Training Coordinator

Official BotService.Org Mascot


BotService Global Admin



BotService Global Co-Admin


BotService Global Co-Admin


BotService Global Co-Admin


BotService Global Co-Admin


BotService Global Senior Member


BotService Global Senior Member

 Bot Application email:

BotService email:

BotService Admins email:

BotService.Org Structure

All BotService staff members are volunteers. That means WE DON'T GET PAID!! We do what we do simply because of the above. There are no "hero/heroines" in BotService. We all basically do the same within the channel. This doesn't mean that there is no authority structure. It's very rare that someone should have to "pull rank", but "rank" will be pulled if necessary. Local Administrators are responsible for making sure all persons they take on their network are trained and understand the policies set forth by BotService.


Staff Levels


Access w/ Channel Services

Access w/Bots

Global Administrator



Global Co-Administrator /

Local Administrator



Global/Local Senior Member



Global/Local Member



Global/Local Helper



Global Staff Appointments

Local Staff Appointments

Perks of Promotion

Helper Guidelines

 An Admin heads each network, sometimes several at the same time. So there is a need for helpers. To help give helpers an idea of what their job entails, these few guidelines have been drawn up:

Your main jobs with BotService are:

Some Rules/Guidelines to follow:

Rules/Guidelines for training:

This policy can change with out notice

Policy on acquiring a bot

Ours is not to pass moral judgement on any channel that requests a channel from BotService.Org. Rather it is to offer channel protection. Below is a list of guidelines in

1. there is another bot in the channel, not counting the one supplied by Channel Services

2. the channel a channel not supported by the network (in other words if channel services

wont register we won't supply a bot)

3. Warez/child endangerment or channels with illegal intent (i.e. trafficking of narcotics)*

4. the channel normally has any one of the following modes: +i, +l, +k, +m

5. Under 18 restriction not enforced nor implied***

Clarification on channels served

*Warez being defined as illegal use of copyrighted software. MP3's is a gray area. Most MP3 sites request the user delete within 24 hours. We will supply that bot with a channel unless there is proof that warez are being traded

** Child porn channels includes sex channels that cater to younger users, with or without the intent to exploit that child, trading of photographs depicting child pornography, and adult sex channels that do not restrict their channels to prevent persons under the age of 18 from entering or enforcing such restrictions

***Adult style channels, whether they depict sexual situations in channel or not, are acceptable provided they have and enforce an "Under 18 restriction"

Policy on removing a bot

1. Deoping, kicking, or banning the bot, or removing its access from Channel Services

2. Kicking or banning BotService.Org members, which come to the channel to solve problems with the bot

3. Not co-operating with BotService.Org members who are trying to solve a problem with the bot in the channel

4. Using the bot for mass advertising, or for any activity that is in conflict with Channel Services policy

5. Abusing the bot

6. Losing control of the channel

7. Setting the channel +i, +l, or +k

8. Failing to impose/enforce an 18+ restriction on adult type channels

Policy on Channel Responsibility

Policy on Investigations and Installations

Networks with Local Administrators:

Networks without a Local Administrator:

In order to meet user requests for bots, the Investigation committee was formed. All Local Administrators are members of this committee by default, as well as chosen helpers.

* Follow the bot request policy as to what channels are eligible for a bot

* Verify that there are no bots in the channel. You can do this by versioning the channel or your judgement based on typical bot type greets

* When reviewing an application for acceptance or rejection the following fields must be filled out:



Information to be filled out

Channel's Name

This is the name of the channel (Pretty self-explanatory). If this isn't filled out it is automatically rejected by the Admin of Applications, and not sent to Local Administrators or the Investigations Committee

Channel's Purpose

This is what the channel is being used for. If the channel name is descriptive enough, this field is not required. Use your judgement

Network Channel is on

This is REQUIRED. With out the network checked, Investigations will not jump from network to network to find it. If this isn't filled out, then Comments should be filled in stating a server.

IRC Nickname

This is REQUIRED. Only the channel owner/founder can request a bot.

Host Mask

This is REQUIRED. *!*@user@host

ICQ Number


Email Address

The person requesting SHOULD use their ISP email address for verification. In the event they use a free-email service, instead of immediately rejecting, email the user and ask them for a verifiable email address. However, many users use an anonymous email address for privacy reasons. Lets keep this in mind when we investigate applications.

Time Online

Should be filled in, but not a valid reason to reject. If no time is filled out, Investigations will try to meet with the owner to set up a time.


Not required, UNLESS no network has been selected earlier.


Installation Guidelines

1. Only one channel owner per channel

2. Channel services bot/chanserv must be present

3. Don't add bots that have an @ next to their nick (the channel control bots)

4. Don't add bots that are part of the relay (most of these are the channel control bot with the exception of a few networks)

5. Don't add bots that are already in 7 channels (including the home channel)

Procedures for adding a bot to a channel

If application has been approved, and owner is present:

1. Select a bot for their channel

a. Select from the +v bots in channel

b. bots name cannot change

2. DCC the bot chosen

a. have bot join channel using join command

b. keep bot window open so you can double check owner/bot addition

3. Add owner to bot using the adduser command, making them 'chanowner'

4. Show owner how to: (watch for verification inside bot)

a. set pass (/msg <botnick> pass <password>

b. login to bot (/msg <botnick> login <password>

5. Have owner add bot to channel services bot

a. must be set at level 449 (verify w/channel services bot)

b. set autoops for the bot

c. Password to set for the bot matches the bots nick (case sensitive) unless its Undernet, where passwords must be 6 characters long, then the pass is BotsBots for botnames under 6 letters

6. Add Channel services to bot to prevent conflict, unless not present in channel

7. Activate +seen (<botnick> chanset [channel] +seen) for the channel (Only global ops or higher can activate this feature)

8. Save database

9. Ask for a channel description while you have the owner there

10. Offer help using the bot, and explain channel levels

a. can only add level below theirs

b. give webpage addy for additional commands

c. show how to get help using the bot (/msg <botnick> help [#channel])

11. After all completed, you can either fill out the form under "Update" on the staff website or you can Email notifying the:


Using initchan Command

This command only applies to ChatNet bots

1. Check application and verify owner

2. Verify K9 is present

3. Pick a bot

4. DCC bot

5. type .newchan add #channelname <key>

a. keys should be entered as followed: date(yy,mm,dd) your initials (mix between cap/lowercase letters) (ex. 990408tAy)

b. in the event the same bot is used on the same day, add a lower case letter to the beginning of the key (ex. a990408tAy)

6. Email the Application Admin with the approval and add include the following in the email:

To activate your bot, and have it join your channel type:

/msg <botnick> initchan {channel] <key>

This command is case sensitive, so watch capitalization

7. Verify later that owner has received his/her bot and all additions have been made to services bot etc. Also set +seen if the channel owner desires

8. After all completed, you can either fill out the form under "Update" on the staff website or you can Email notifying the:

The Relay

All BotService.Org channels on each network are connected via relay. This allows the staff to keep an eye on their nets (if they are on a different one) and provide coverage for nets that do not have helpers or staff available to them. All BotService.Org staff are asked to help monitor our relay bots, to ensure that they are always linked and functioning.

Keep in mind that what you say will be sent to over 33+ networks, so there are a few things to keep in mind:

1. Only BotService.Org Staff, bots and their helpers may idle in any BotService.Org channel. Server Admins and IRCops must adhere to our channel rule of no idle (in other words, they aren't special to break the rules)

2. Use the relay bots for discussion not necessary on the relay that you do not feel is necessary for our users to see. (i.e. brief quickie meeting, asking an involved question when the bothouse is busy, things like that).




What it does


/msg <relaybot1> linkmsg <relaybot2> <nick><msg>

Example: to send a msg from you on Othernet to Nicki on DarkerNet:

/msg Cleopatra linkmsg Nadu Nicki Hi!!!

Sends a private message to someone on another net, via the relay using the relay bot in the current channel your in, to the relay bot in the channel that they are in



sends a ping and gives you the time to all the bots on the relay


netname <server> netname ChatNet

To find out what the relay bot is on a network


!linkusers <relaybot> !linkusers Otherbot (for users on Chatnet)

Gives a list of users currently in the channel with the relay bot


!linkboot <relaybot> <nick> <message>

Example, to boot from Othernet someone from Chatnet:

!linkboot Otherbot Nevin testing

Used to kick a user from the channel the relay bot is on via the relay


!linkban <relaybot> <nick> <duration> <reason>

Example, to ban from Othernet someone from Chatnet:

!linkban Otherbot Nevin perm testing

for banning users on a remote net via the relay


findbot <botnick>

will tell you where that bot is located

Anyone with channel master level access or higher can check to see if all links are in place by joining one of the main channels and typing:


If you do this check, and find any bots not responding to the ping, please report it to someone who is a global senior member, or higher.

In addition to our main channel relay, we also maintain channel relays for the following channels.

#Witches - Owned by LordDrake

#Cauldrons - Owned by LadyRogue

#MusicChat - Owned by `Doc

As with all user channels, we join only when asked or to check/maintain the relay/bots.


Linking bots to the relay

Choose a bot to link to from (under relay)

DCC into the hub bot

.+bot <botnick> <mask (i.e.>:<port> <enter>

.chpass <botnick> <password> (you can get this password from either terri{N}, taycie or `Sioux)

.botattr <botnick> +h

.link <botnick>

.+bot and .chpass must be done on each bot. The rest can be done from either the bot to be linked or the hub bot.

If relay bots go down restart the Main Hub bot. If they do not relink after that, get a Global Administrator for help.


Ban Types supported by BotService Bots


length of ban


2 hours if no ban type not specified


1 hour


6 hours


1 day


3 days


7 days


1 month


3 months


6 months


1 year


permanet ban

Direct Commands

These are commands that appear in the channel. This method requires the least amount of typing, and allows everyone to see what command you issued. A direct command consists of the name of the bot followed by a space followed by the command.

For example, if you want the bot that is named Achilles to issue the command date, you would type:

Achilles date

Direct using the bot's 'shortcut' name can shorten commands even more - ask BService what the bot's shortcut name is. For the bot Achilles, the shortcut is ac, and so the above example could also be done this way:

ac date

On some bots, a very few specialized commands called Public Commands exist; with those, the name of the bot is omitted in the command.

Message Commands

These are commands given by typing /msg followed by a space followed by the name of the bot followed by a space followed by the command. Note that the shortcut name for the bot cannot be used here. The advantage to this method is that other people in the channel don't see who issued which command. Using this method, the above example would be accomplished with:

/msg Achilles date

Direct/Message Commands

The following commands can be performed by anyone in the channel.

* Items inside [ ]'s are optional ;

* Items in italics are required for the command to work, but need to be replaced by something appropriate




What it does


seen <nick>

Find out when the last time someone was in the channel


country <country abbr.>

Find out what a country's name is from its abbreviation


<botnick> time

Current time where the bot is at


<botnick> date

Current date where the bot is at


<botnick> ping me

<botnick> ping <nick>

Have the bot ping you or someone in the channel and give you the reply


<botnick> version

Gives the current version of the bot


<botnick> whois [channel] me

<botnick> whois [channel] <nick>

Displays information on a user


<botnick> userlist [channel]

Displays list of users in the channel that have access to the bot


<botnick> access me

<botnick> access <nick>

Displays information on a user


<botnick> levels

Displays possible access levels with the bot and corresponding flags


<botnick> flags channel

<botnick> flags global

Displays the meaning of the flags for channel and global users


<botnick> banlist [channel]

Lists bans on the bot for the channel


<botnick> bantype

Displays the available ban types and what each means


<botnick> ignorelist

Lists all users currently on ignore


define <abbreviation>

Gives user definition for standard "IRC Speak"

Channel Owner Commands

The channel owner can only perform the following commands.




What it does


<botnick> chaninfo

Lists current settings maintained by the bot


<botnick> chanset [channel] chanmode <mode>

Sets or removes standard IRC modes and enforces them (s, t, n)

chanset idle-kick

<botnick> chanset [channel] idle-kick <minutes>

Kicks any user that has been idle too long in your channel. *Note: setting minutes to 0 (zero) will disable this feature

chanset +autoop

<botnick> chanset [#channel] +autoop

Gives ops automatically to anyone on the bot's userlist who is at chanop level or higher

chanset +autovoice

<botnick> chanset [#channel] +autovoice

gives +v automatically to anyone on the bot's userlist who is at chanvoice level or higher

chanset flood-chan

< botnick> chanset flood-chan lines:seconds

This defines the flood level for public chatter and actions

Example: Nebula chanset flood-chan 8:10

This would cause a user to be kicked if she posts more than 8 lines in a 10 second interval.

Channel Master Commands

The channel master or higher can perform the following commands.




What it does


<botnick> cycle

Makes the bot part and rejoin the channel


<botnick> invite <nick>

Have the bot invite someone to the channel


<botnick> dccme

Makes the bot initiate a DCC chat with you


<botnick> act [#channel] <action>

Makes the bot perform an action in channel


<botnick> say [#channel] <msg>

Make the bot talk in channel

Channel Op Commands

The following commands can be performed by channel operators or higher.




What it does


<botnick> topic [#channel] <new topic>

Have bot set a topic for the channel


<botnick> mode [#channel] <modes>

Set channel modes (s, t, n)


<botnick> op [#channel] me

Op yourself or a user


<botnick> deop [channel] me,

<botnick> deop [channel] <nick 1, 2, 3>

Deop yourself or a user


<botnick> voice [#channel] <nick>

Voice (+v) a user in a channel


<botnick> devoice [channel] <nick>

Devoice (-v) a user in the channel


<botnick> kick [channel] <nick>

Kick a user from the channel


<botnick> ban [channel] <nick> <reason>, <botnick> ban [channel] <user@ host> <reason>

Ban a user from the channel for the default of 2 hours

**Using Perm will ban this person permanently from the channel


<botnick> adduser <nick> <level>

Add a user to the bot

** You can only add someone lower than your access i.e. ChanOps can only add Chanvoice users


<botnick> remuser <nick>

Remove a user from the bot

Channel Voice Commands

The channel voice or higher can perform the following commands.




What it does


<botnick> info [channel] <nick> <type>

Gives personal information about a user. Valid types are: name, sex, bday, location, occupation, url, email, other



<botnick> set [channel] <type> <details>

Sets personal information about you. Valid types are: name, sex, bday, location, occupation, url, email, other


<botnick> voice [channel] me

Has bot voice you (+v)


<botnick> devoice [channel] me

Has bot unvoice you (-v)

Global Owner Commands

The can perform all channel/global commands.




What it does


<botnick> die [reason]

Kills the bot

Global Master Commands

The can perform all channel/global commands, except Global owner commands.




What it does


<botnick> banner <msg>

sends a message to all channels the bot is in


<botnick> rehash

reloads script


<botnick> restart

restarts bot


<botnick> join <#channel name>

has bot join channel and set up records for use


<botnick> part <#channel name>

has bot part channel and destroy all records set up

Global Op Commands

The can perform all channel/global commands, except Global owner commands.



What it does


<botnick> ignore <user@host>

 have bot ignore user


<botnick> unignore <user@host>

remove user from ignore


<botnick> clear [#channel]

removes channel modes


<botnick> opstat

tells whether or not a bot is opped in its channels


<botnick> lock [#channel]

sets modes +smi


<botnick> unlock [#channel]

sets modes -smi


<botnick> save

saves bots user lists


<botnick> msg <nick> <msg>

use bot to msg someone


<botnick> channels

list channels bot is on


<botnick> global <command>

gives a command that is executed in all channels the bot is in

chanset +seen

<botnich> chanset [#channel] +seen

Sets the seen feature for the channel


Access Levels

Not everyone can issue all commands. There are several commands which can be issued by anyone, but most are restricted to people who have been registered with the bot. Part of that registration is the assignment of an access level to the user, and that is what determines which commands the user has access to.

Associated with each user are a number of flags; each access level includes certain of these flags, by default.

The various access levels are listed below, along with which flags they normally have. Below that, are listed the flags, and what each means. Access Levels are as shown below, highest at the top:




Global Flags

Channel Flags


Full access user




Global Owner




Global Master




Global Op




Global Voice




Channel Owner




Channel Master




Channel Op




Channel Voice



 Syntax: In channel: <botnick> adduser <nick> <level>

Example: In channel: Argus adduser taycie chanowner


Global Flags

 These are flags used for BotService Members.



What it is

What it does



Always ops this user in channel



User is another bot



User record is a common access site


Global deop

Will deop user on all channels the bot is on


Global friend

Bot will voice user on all channels its in


Highlight flag

User sees highlight in text output



User is a file area master


Auto kick

User is kicked/banned automatically


Global master

User is a bot master


Global owner

User is a bot owner


Global op

User will be op'd in any channel the bot is in



Partyline access


Botnet master

Botnet master



Not sent to other share bots


Global voice

User gets a +v on any channel



User has file area access

Channel Flags

These are flags that are set for users of a specific channel. When you use the chattr command,

make sure you specifiy a channel name with the command.



What it is

What it does



Always op user on join in channel



Bot will not allow user to be opped



User isn't punished for doing bad stuff (like channel flood, repeating, swearing, etc.)



User is auto kicked from channel



User is the botmaster for the channel



User is the owner of the bot in the channel



User is an op for the channel



User will never be voiced in the channel



User will always get a +v in the channel

Bot Flags (For linking)

When you link up Bots, you need to add flags to them. If Bots are not linked they will not op each other; they will not share userfiles, etc. Once you designate a hub bot, the leaf bot will attempt to link to the hub about once per minute. If you have several Bots linked together, you should also designate an alternate hub, and for every large botnets, two alternate hubs for times when the hub bot is down. When the hub bot is down, the leaf Bots will attempt to link to an alternate hub, but they will keep trying to connect to the hub bot until they are able to link to it. As soon as they are able to link to the hub bot, they will delink from the alternate hub.



What it is

What it does



Your bot will try about once per minute to link to the hub bot until it succeeds. Once it links to the hub, it will no longer try to connect to any other bot.



Your bot will reject telnet connections from this bot. This is useful if you are removing someone's bot from your botnet, but the owner is not around to remove your Bot's record from the offending bot. This bot will not be allowed on the botnet, no matter what bot it tries to connect through.


Alternate Hub

If no hub bot can be linked, or the hub is down, your bot will try to link to the alternative hub instead. Once the alternate bot is linked, it will still try to connect to the hub bot, but will no longer try to connect to any others. If a hub bot is linked later, the connection to the alternate hub is dropped.



This means that your bot will share a userfile with this bot. There is a full explanation of this flag in the sharing instructions.



If a bot is marked as a leaf, that means you do not want any Bots to link behind it. It should link only to the hub. In other words, it can only be connected to the botnet through one bot, and no other Bots may connect to the botnet through it.

 DCC Commands

These commands are given within a DCC chat session with the bot, and always begin with a dot followed by the command. The most powerful of the bot's commands are done this way. Any user who has access to the bot can also enter into DCC chat with it, using the same method as you would for any other irc user. There are only two differences:




What it does


.chat [number]

Example: .chat 42

your DCC session with the bot allows you to talk with other users that are in DCC with the bot; at any one time, you are on one of 100,000 channels inside that DCC; when you first enter the DCC, you are on channel 0 - the party line; the .chat command allows you to switch to a different DCC channel


.newpass new_password

changes your password with the bot


.nick new_handle

changes your handle with the bot; when you were first added to the bot, the nickname you had at that time became your handle with the bot


.note handle message

sends a note to another person that is on the bot's userlist

.notes list

.notes list

displays how many notes are waiting for you, and from whom

.notes read

.notes read number

Example: .notes read 1

displays a note that was sent to you

.notes erase

.erase number

Example: .erase 2

Example: erase all

erases a note you had received



ends your DCC session with the bot



displays a list of people who are currently on the partyline


.whois handle

This command will cause the bot to display some information about one of its users.


.help [command]

displays documentation on commands available in DCC


.+user <nick> <host>

add another user within the bot


.-user <nick> <host>

remove user within the bot


.+host <nick> <host>

add another host address for someone already on bot


.-host <nick> <host>

remove a host from a current user on the bot


.chattr <nick> <flags>

add or remove flags for a user