/ScriptServ

[q_adduser]
———› Description:
Add a user to a channel. (Level: 1)

———› Usage:
/msg Q ADDUSER <#channel> <nickname>

———› Details:
Add a user to a channel.
You should use CHANLEV to view/set the flags, but this command adds a user with default flags +aot
/msg Q ADDUSER #channel nick Add AUTHED user.
/msg Q ADDUSER #channel #nick Add user (if not authed)
The nick parameter can also be given as #idnick where idnick is the nickname the person originally registered under.
[q_auth]
———› Description:
Identifies you as a particular user on the bot. (Level: 0)

———› Usage:
/msg Q@CServe.quakenet.org AUTH <authname> <password>

———› Details:
This will identify you on the bot as <authname> until you next quit from IRC or are split from the bot.
[q_authhistory]
———› Description:
Show history with authed users. (Level: 1)

———› Usage:
/msg Q AUTHHISTORY <channel>

———› Details:
This will show a history list with authed users on the actual channel. Could be used to trace stolen passwords etc.
[q_autolimit]
———› Description:
Set the auto-limit on a channel. (Level: 1)

———› Usage:
Usage: /msg Q AUTOLIMIT #channel #10

———› Details:
Set the auto-limit on a channel. Limit will be adjusted automatically to avoid join floods. The limit must be combined with "/msg Q CHANFLAGS #channel +c"
[q_ban]
———› Description:
Ban a hostmask permanently on a channel. (Level: 1)

———› Usage:
/msg Q BAN #channel nick!*ident@evil.host.com

———› Details:
Add a ban permanently to a channel.
[q_banclear]
———› Description:
Delete all bans from a channel. (Level: 1)

———› Usage:
/msg Q BANCLEAR #channel

———› Details:
Delete all bans from a channel. The difference from UNBANALL, is that this command removes all permanent bans too.
[q_bandel]
———› Description:
Delete a ban from a channel. (Level: 1)

———› Usage:
/msg Q BANDEL #channel nick!*ident@evil.host.com
/msg Q BANDEL #channel #3

———› Details:
Delete a ban from the list. If you type a '#' it will delete the x'th hostmask in the list.
[q_banlist]
———› Description:
List all permanent bans on a channel. (Level: 1)

———› Usage:
/msg Q BANLIST #channel

———› Details:
List all permanent bans on a channel.
[q_chanflags]
———› Description:
Change/view the flags on a channel. (Level: 1)

———› Usage:
/msg Q CHANFLAGS <channel> [flags]

———› Details:
Change/view the flags on a channel.They are specified in the normal way - e.g. +f-b and so on.
The flags are as follows:
/msg Q CHANFLAGS #chan View the flags on the channel.
/msg Q CHANFLAGS #chan +-flag Change the flags on the channel.
+b - Bitch
Prevents anyone who hasn't got operator privs on the channel from getting OP.
+c - Channel-limit
Activate channel-limit protection. - Set parameters with AUTOLIMIT command.
+f - Force topic
Prevent people change the topic with /topic command - SETTOPIC is needed
+k - Force key
Set a key permanent on the channel. - Set the key with the KEY command.
+l - Force limit
Set a limit permanent on the channel. - Set the limit with the LIMIT command.
+p - Protect opers
Prevent people who have with OP privs on the channel from being deopped.
+t - Topic save
Allow Q to set the topic if Q is restarted.
+w - Welcome message
Send a welcome message (set by WELCOME) to all joining users.
[q_chanlev]
———› Description:
Change/view someone's rights on a channel. (Level: 1)

———› Usage:
/msg Q CHANLEV <channel> [nick] [change flags]

———› Details:
Change someone's flags/rights on a channel.
/msg Q CHANLEV #chan Dump all users on the channel.
/msg Q CHANLEV #chan nick View a user's flags (if authed)
/msg Q CHANLEV #chan #nick View a user's flags (if not authed)
/msg Q CHANLEV #chan nick +-flag Change a user's flags on the channel.
Rights available are:-
+a = autoop/autovoice on join.
+b = banned. (Only works if they've AUTH'd.)
+m = master. (Can make opers.)
+n = owner. (Can make masters.)
+o = op.
+v = voice.
+t = can set topic.
[q_clearchan]
———› Description:
Clear all modes on a channel. (Level: 1)

———› Usage:
/msg Q CLEARCHAN #channel

———› Details:
Clear all modes on a channel. Could be used if someone has set a key/invite only.
[q_deopall]
———› Description:
Deop all users on a channel. (Level: 1)

———› Usage:
/msg Q DEOPALL #channel

———› Details:
Deop all users on a channel.
[q_email]
———› Description:
Change your E-mail. (Level: 1)

———› Usage:
/msg Q EMAIL <password> <user@host.com>

———› Details:
Change your E-mail, requires your account password for verification purposes.
The email address is used if you have forgotten your password and want to get it by E-mail thru the REQUESTPASSWORD command.
(It's NOT possible to view other users E-mail addresses.)
[q_hello]
———› Description:
Creates a new user account in the bot. (Level: 0)

———› Usage:
/msg Q HELLO user@mymailhost.xx user@mymailhost.xx

———› Details:
Creates a new user account in the bot, and sends the generated password to the supplied email address. Your email address MUST be given twice, to check that you didn't mistype it. Note that there are *NO HOSTMASKS* on this bot. Other bots allow you to ident if you just know the password, so this one just uses the password and scraps the hostmask as pointless.
[q_help]
———› Description:
Gives full help on a particular bot command. (Level: 0)

———› Usage:
/msg Q HELP <command>

———› Details:
Gives the full help (like this!) instead of the short help for a particular bot command.
[q_invite]
———› Description:
Invites you to a channel where the bot is. (Level: 1)

———› Usage:
/msg Q INVITE <channel>

———› Details:
Invites you to a channel which the bot is sitting on. The bot *must* be on the channel, and you must have a high enough level on that channel.
[q_key]
———› Description:
Set a key on a channel. (Level: 1)

———› Usage:
/msg Q KEY #channel key

———› Details:
Set a key on a channel. This must be combined with "/msg Q CHANFLAGS #channel +k" to keep the key permanent.
[q_limit]
———› Description:
Set a max user-limit on a channel. (Level: 1)

———› Usage:
/msg Q LIMIT #channel 20

———› Details:
Set a max user-limit on a channel. This must be combined with "/msg Q CHANFLAGS #channel +l" to keep the limit permanent.
[q_newpass]
———› Description:
Change your password. (Level: 1)

———› Usage:
/msg Q NEWPASS <old password> <new password> <new password>

———› Details:
Change your password. Requires your current account password for verification purposes.
Your new password MUST be given twice, to check that you didn't mistype it.
[q_op]
———› Description:
Gives you ops on a channel where the bot is. (Level: 1)

———› Usage:
/msg Q OP <channel>

———› Details:
Gives you ops on a channel which the bot is sitting on. The bot *must* be on the channel, and you must have a high enough level on that channel.
[q_removeuser]
———› Description:
Remove a user from a channel. (Level: 1)

———› Usage:
/msg Q REMOVEUSER <#channel> <nickname>

———› Details:
Remove a user from a channel.
You should use CHANLEV to view/set the flags, but this option removes all flags for a user.
/msg Q REMOVEUSER #channel nick Remove AUTHED user.
/msg Q REMOVEUSER #channel #nick Remove user (if not authed)
[q_requestpassword]
———› Description:
Request your password via E-mail. (Level: 0)

———› Usage:
/msg Q REQUESTPASSWORD <user@host.com>

———› Details:
Get your password mailed to your E-mail address in case you have lost it.
[q_settopic]
———› Description:
Changes the default channel topic. (Level: 1)

———› Usage:
/msg Q SETTOPIC <channel> <topic>

———› Details:
Sets both the current and default topics on the channel to that specified.
[q_showcommands]
———› Description:
Lists all the commands on the bot. (Level: 0)

———› Usage:
/msg Q SHOWCOMMANDS

———› Details:
Lists the commands available on the bot and the level of access required for each. This won't list commands above your level.
[q_unbanall]
———› Description:
Unban all temporary bans on a channel. (Level: 1)

———› Usage:
/msg Q UNBANALL #channel

———› Details:
Unban all temporary hostmasks on a channel. Permanent bans set by BAN must be removed with BANCLEAR.
[q_unlock]
———› Description:
Unlocks a locked account. (Level: 0)

———› Usage:
/msg Q@CServe.quakenet.org UNLOCK <authname> <password> user@mymailhost.xx

———› Details:
Unlocks a locked account, sends activation instructions to supplied email address.
[q_version]
———› Description:
Show version number. (Level: 1)

———› Usage:
/msg Q VERSION

———› Details:
Show version number and compile date.
[q_voice]
———› Description:
Gives you +v on a channel where the bot is. (Level: 1)

———› Usage:
/msg Q VOICE <channel>

———› Details:
Gives you +v (voice) on a channel which the bot is sitting on. The bot *must* be on the channel, and you must have a high enough level on that channel.
[q_welcome]
———› Description:
Show/set welcome message on a channel. (Level: 1)

———› Usage:
/msg Q WELCOME <channel> Show welcome message
/msg Q WELCOME <channel> <message> Set welcome message

———› Details:
This must be combined with "/msg Q CHANFLAGS #channel +w" to keep the message permanent.
[q_whoami]
———› Description:
Gives the bot's opinion on who you are. (Level: 0)

———› Usage:
/msg Q WHOAMI

———› Details:
The bot should tell you your current global auth level (equivalent to the old #cservice levels) and may give other info too.
[q_whois]
———› Description:
Tells you who someone really is. (Level: 1)

———› Usage:
/msg Q WHOIS <nick>

———› Details:
Tells you what name a user has AUTHed under, if it's not the same as their nick.
[l_adduser]
———› Description:
Add a user to a channel

———› Usage:
/msg L ADDUSER #channel nick

———› Details:
Add a user to a channel. You should use CHANLEV to view/set the flags, but this command adds a user with default flags +ao
[l_chanlev]
———› Description:
Lists and sets channel flags

———› Usage:
/msg L CHANLEV #channel [nick] [flags]

———› Details:
Changes the users access rights for a channel. If no user or flags are specified, then the access rights for the entire channel are printed. Use nick for online users and #authname for offline users. You need be either the owner (+n) or the master (+m) of the channel to change the access right for the channel. Only the owner (+n) can set or unset the master flag. If the user has no flags for the channel, the user is added to the channel and if all flags are removed, the user is removed aswell. To remove a user, just remove all the flags the user has for the channel. Supported flags are:
a (auto): Auto-ops or autovoices a user on join to channel
g (auto): Works only for the +v flag
m (master): Can set users access rights for channel
n (owner): Like master but can set masters for channel
o (op): Has the right for mode +o on channel
v (voice): Has the right for mode +v on channel
Example: /msg L chanlev #mychannel
/msg L chanlev #mychannel myfriend +ao
/msg L chanlev #mychannel #myfriendsauthname +maov
[l_clearchan]
———› Description:
Clears all channel modes

———› Usage:
/msg L CLEARCHAN #channel

———› Details:
Removes all channel modes from channel, usefull if there is +i, +l or +k on the channel. You need to have the access flag +o for the specified channel for this command to work.
[l_clearinvite]
———› Description:
Stops L enforcing +i on a channel

———› Usage:
/msg L CLEARINVITE #channel

———› Details:
Removes the +i enforce on the channel from now on.
You need to have the access flag +m on the specified channel for this command to work.
To set inviteonly, use SETINVITE.
To invite yourself to an inviteonly channel, use INVITE.
[l_deopall]
———› Description:
Deops every user on channel

———› Usage:
/msg L DEOPALL #channel

———› Details:
Deopall removes all channel operators by settings the mode -o to every user on the channel. You need to have the channel flag +m or +n for the channel for this command to work.
[l_invite]
———› Description:
Invites you to a channel

———› Usage:
/msg L INVITE #channel

———› Details:
Invites you to the specified channel.
You need to have the access flag +o or +v for the specified channel for this command to work. This command can not be used to invite users other than yourself.
[l_op]
———› Description:
Gives you mode +o for channel

———› Usage:
/msg L OP #channel

———› Details:
Gives you mode +o for the specified channel.
You need to have the access flag +o for the specified channel for this command to work. This command can not be used to set the mode +o for users other than yourself.
[l_recover]
———› Description:
Recover a channel (deopall/unbanall/clearchan)

———› Usage:
/msg L RECOVER #channel

———› Details:
Do all neccesary steps, in the right order, to recover a lost channel, ie deopall, unbanall and clearchan. You need to have the channel flag +m or +n for the channel for this command to work.
[l_removeuser]
———› Description:
Remove a user from a channel

———› Usage:
/msg L REMOVEUSER #channel nick

———› Details:
Remove a user from a channel. You should use CHANLEV to view/set the flags, but this command removes all flags for a user.
[l_setinvite]
———› Description:
Makes L enforce +i on a channel

———› Usage:
/msg L SETINVITE #channel

———› Details:
Makes the specified channel inviteonly, and tells L to enforce +i on the channel from now on.
You need to have the access flag +m on the specified channel for this command to work.
To unset inviteonly, use CLEARINVITE.
To invite yourself to an inviteonly channel, use INVITE.
[l_unbanall]
———› Description:
Removes all bans from channel

———› Usage:
/msg L UNBANALL #channel

———› Details:
Removes all bans (modes +b) from a channel. You need to have the access flag +o for the channel for this command to work.
[l_version]
———› Description:
Tells the current L version

———› Usage:
/msg L VERSION

———› Details:
Tells you the current version of L.
[l_voice]
———› Description:
Gives you mode +v for channel

———› Usage:
/msg L VOICE #channel

———› Details:
Gives you mode +v on the specified channel.
You need to have the access flag +v for the specified channel for this command to work. This command can not be used to set the mode +v for users other than yourself.
[l_welcome]
———› Description:
Channel welcome message

———› Usage:
/MSG L WELCOME #channel message

———› Details:
Sets or views the message shown to every user joining the channel. If no message is defined, then the current channel welcome message is showed. You need to have either +m or +n access for the channel you intend to change the welcome on. Maximum welcome message length is 250 characters.
You can remove the welcome message by using 'remove' as the new welcome message.
Example: /msg l welcome #mychannel Hello and welcome to my channel!
/msg l welcome #mychannel remove
[l_whoami]
———› Description:
Tells you your user information

———› Usage:
/msg L WHOAMI

———› Details:
Tells you your user information for L, this includes your auth name, your global auth level, the date of your last auth and all channels that you have access to.
[l_whois]
———› Description:
Tells you who someone else is

———› Usage:
/msg L WHOIS [nick]

———› Details:
This tells you the user information of another user, the information includes the auth name of the user, global auth level, date of last auth and channels that the user is known on. Note that only channels that you have access to aswell are printed. Use nick for online users and #authname for offline users.
[bnc_addallow]
———› Description:
Adds a host allow to connect (Admin only)

———› Usage:
/ADDALLOW host or hostmask

———› Details:
This function allows you to set hosts which may connect to your bouncer.
On default, * is set to be allowed to connect to the bouncer. You would have to delete that entry first to set your own more restricted host allows for the bouncer.

———› Example:
/ADDALLOW host22.mydomain.com
would allow that specific host to connect.
/ADDALLOW *.mydomain.com
would allow all hosts from mydomain.com.
You can use the wildcards ? and * in your definition.
Remember that also linked hosts have to be added in the host allowance.

———› See also:
/DELALLOW /LISTALLOW
[bnc_addask]
———› Description:
Adds a host/bot to ask op from

———› Usage:
/ADDASK [network~][#chan] password :hostmask or )bot

———› Details:
You can set your bouncer to ask bots for op even if you are not online.
This is quite useful becouse you can use bouncer both as a chat client and screen which protects channel.

———› Example:
/ADDASK lamepass :*!LameBot@Lame.Host.Com

———› See also:
/DELASK /LISTASK /DELOP /ADDOP /LISTOPS /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS
[bnc_addautoop]
———› Description:
Adds a user who gets auto-op from you

———› Usage:
/ADDAUTOOP [network~]#channel :hostmask

———› Details:
This command allows you to add users for being auto-opped if they join the channel.

———› Example:
/ADDAUTOOP #leet :*!*blah@*.lame.com
would add autoop for any user matching *!*blah@*.lame.com for the channel #leet.

———› See also:
/DELAUTOOP /LISTAUTOOPS /ADDOP /DELOP /LISTOPS
[bnc_addban]
———› Description:
Adds a ban (global or to a channel)

———› Usage:
/ADDBAN [network~][#chan] reason :hostmask

———› Details:
You can ban people from the channel even if you are not logged on.

———› Example:
/ADDBAN Get Lost Lamer ! :*!niky@lamers.land.com

———› See also:
/DELBAN /LISTBANS
[bnc_adddcc]
———› Description:
Adds a DCC-connection to a bot

———› Usage:
/ADDDCC [network~]botname user pass :[S=]host:port

———› Details:
Adds a new DCC bot connection. You can add a direct bouncer to eggdrop secured connection.
If you put S= in front of the host, psyBNC will try to establish an SSL-connection.

———› Example:
/ADDDCC MyBot newbie MyPass :the.elite.newbie.com:7333
You can get bot telnet port by typing .dccstat in the botnet partyline.
You will be automatically logged in as user "newbie" with the password "MyPass" on the example above.

———› See also:
/LISTDCC /DELDCC
[bnc_addignore]
———› Description:
Adds a hostmask/contentfilter to the ignores

———› Usage:
/ADDIGNORE content :hostmask

———› Details:
This functionality allows to add ignore entries.
These can be dependent from the hostmask and/or from content.
Content is meant as a part of any private message and/or notice.
If a special hostmask with any content has to be filtered, you would use for example:
/ADDIGNORE * :*!*@*.lao.com
Has a content to be filtered only, you will have to use for example:
/ADDIGNORE sex :*!*@*
That would filter everything, which has the part of text "sex" in the message-content.
If both content and hostmask have to count, you could use:
/ADDIGNORE hug :*!*@*.icafe.com
for example.
This would deny all messages from the domain icafe.com with the content "hug".

———› See also:
/DELIGNORE /LISTIGNORES
[bnc_addlog]
———› Description:
Adds a log source / filter

———› Usage:
/ADDLOG [network~]source :filter

———› Details:
ADDLOG allows you to add an entry to the logging specifications for traffic logging.

———› Example:
/ADDLOG #leet :0day
would allow you to log any texts that appear on #leet with the partial text 0day.

———› See also:
/DELLOG /LISTLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_addnetwork]
———› Description:
Adds a seperate network to your client

———› Usage:
/ADDNETWORK name

———› Details:
This functionality allows you to use multiple connections to different ircnetworks to the single connection you are keeping to the bouncer.
So it is possibly for you to get a client in your favourite network also to secondary networks you also are on.

———› Example:
/ADDNETWORK Ef
Would add a new network token named Ef to your userspecifications.
For any added network, you can use the functions seperately, for example:
/ADDSERVER Ef~irc.freei.net:6667
would add a server for your newly added network token. The bouncer would open a second outgoing connection and relay it to your single client connection by prefixing users and channels with the network token. Channel #sausage would be on that network #Ef~#sausage. Nicks also get prefixed, so the user johndoe on EfNet would appear as Ef~johndoe.
Every command can be prefixed with the network token and would then be executed for your networked client.

———› See also:
/DELNETWORK
[bnc_addop]
———› Description:
Adds a user who may get op from you

———› Usage:
/ADDOP [network~][#chan] password :hostmask

———› Details:
You can add users to your bouncer op list. They can then get op from bouncer similar to bot oping.

———› Example:
/ADDOP #chan newpass:*!*@this.is.elite.host.com.
If the "#chan" is not specified then user can ask op from bouncer in any channel that the bouncer is op in.

———› See also:
/DELOP /LISTOPS /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS /ADDASK /DELASK /LISTASK
[bnc_addserver]
———› Description:
Adds an IRC-server to your serverlist

———› Usage:
/ADDSERVER [network~][S=]server :port password

———› Details:
Adds a new IRC server. You can add many servers. If the bouncer can't connect to a server it will try next one in list.
If you put an S= in front of the hostname, the bouncer will try to establish a SSL-connection.

———› Example:
/ADDSERVER irc.stealth.net :6667

———› See also:
/DELSERVER /LISTSERVERS
[bnc_adduser]
———› Description:
Adds a new user to the bouncer (Admin only)

———› Usage:
/ADDUSER login :username

———› Details:
Adds a new bouncer user, you can add up to 99 users and you still won't be flooded off. But remember more users means more traffic and some servers have a traffic limit.

———› Example:
/ADDUSER newbie :The lamest kid in town !
The newbie will be used as a LOGIN. Remember to set your IDENT correctly! The text after ":" is displayed as a REAL NAME.

———› See also:
/DELUSER
[bnc_aidle]
———› Description:
Enables/Disables anti-idle

———› Usage:
/AIDLE [0|1]
[bnc_autogetdcc]
———› Description:
Always get offered Files

———› Usage:
/AUTOGETDCC [network~] :0|1

———› Details:
Enables or disables auto-get of offered DCC-files. This setting is disabled by default.
[bnc_autorejoin]
———› Description:
Enables/Disables auto-rejoin

———› Usage:
/AUTOREJOIN [0|1]

———› Details:
Disables or enables auto-rejoin of channels after kick
[bnc_bconnect]
———› Description:
Reconnects a bquitted connection

———› Usage:
/BCONNECT [network~]

———› See also:
/BQUIT
[bnc_bhelp]
———› Description:
Lists this help or help on a topic

———› Usage:
/BHELP
[bnc_bkill]
———› Description:
Kills a user from the proxy (Admin only)

———› Usage:
/BKILL user

———› Details:
You can close user connection with BKILL.

———› See also:
/DELUSER
[bnc_bquit]
———› Description:
Quits your current server connection

———› Usage:
/BQUIT [network~]

———› Details:
Quits the server connection until you restart it with BCONNECT.

———› See also:
/BCONNECT
[bnc_brehash]
———› Description:
Rehashes the proxy and resets all connections (Admin only)
[bnc_bvhost]
———› Description:
Sets your vhost to connect through

———› Usage:
/BVHOST <vhost>

———› See also:
/JUMP
[bnc_bwho]
———› Description:
Lists all users on the bouncer

———› Usage:
/BWHO

———› Details:
Lists all users on the bouncer. If user has a "*" in front of his nick that means that the user is logged in. With this command you can also see the uplinks to (<-) and from (->) your bouncer. That is if you have bouncer linked to other bouncers.
[bnc_dccanswer]
———› Description:
Answers to a DCC chat request

———› Usage:
/DCCANSWER [S=]nick

———› Details:
DCCANSWER will accept an offered DCC chat from the given nick, if he sent a request for a chat session.
If S= is put in front of the nick, psyBNC tries to establish a SSL-connection.

———› See also:
/DCCCHAT /DCCGET /DCCSEND /DCCCANCEL /LISTDCC
[bnc_dcccancel]
———› Description:
Cancels a DCC chat or transfer

———› Usage:
/DCCCANCEL nick [:file]

———› See also:
/DCCCHAT /DCCANSWER /DCCSEND /DCCGET /LISTDCC
[bnc_dccchat]
———› Description:
Offers a DCC chat to a given IRC user

———› Usage:
/DCCCHAT [S=]nick

———› Details:
Offers a DCC chat to the given nick and waits until it will be accepted.
If S= is put at the front of the nick, psyBNC tries to establish a SSL-connection.

———› See also:
/DCCCANCEL /DCCSEND /DCCGET /DCCANSWER /LISTDCC
[bnc_dccenable]
———› Description:
Enables/Disables DCC thru psyBNC

———› Usage:
/DCCENABLE [0|1]

———› Details:
Allows you to disable or enable the internal DCC-chat and send handling of psyBNC. If disabled, psyBNC would just hand the DCC requests over to the client.

———› See also:
/DCCCHAT /DCCANSWER /DCCGET /DCCCANCEL /LISTDCC
[bnc_dccget]
———› Description:
Gets a DCC send file from an IRC user

———› Usage:
/DCCGET [S=]nick :filename

———› Details:
Get an offered file from a user by acknowledging the send request. The file will be put into downloads/USERnn, where nn is the number of the user.
If S= is put before the nick, psyBNC tries to establish an SSL-connection.

———› See also:
/DCCCHAT /DCCANSWER /DCCSEND /DCCCANCEL /LISTDCC
[bnc_dccsend]
———› Description:
Sends a file to a given IRC user

———› Usage:
/DCCSENDME :filename

———› Details:
Sends a file send request to the own client. This is thought to transfer formerly downloaded files from the shell to the user.
If the user accepts the send, the file will be sent.

———› See also:
/DCCCHAT /DCCANSWER /DCCGET /DCCCANCEL /LISTDCC /DCCSEND
[bnc_dccsendme]
———› Description:
Sends the bouncer user a file

———› Usage:
/DCCSEND [S=]nick :filename

———› Details:
Sends a file send request to the given nickname.
If the user accepts the send, the file will be sent.
If S= is put in front of the nick, psyBNC tries to create an SSL-Connection.

———› See also:
/DCCCHAT /DCCANSWER /DCCGET /DCCCANCEL /LISTDCC
[bnc_delallow]
———› Description:
Deletes a host allow (Admin only)

———› Usage:
/DELALLOW number

———› Details:
Deletes a host allowance from your list of host allows.
You can get the number of the entry from LISTALLOW.

———› See also:
/ADDALLOW /LISTALLOW
[bnc_delask]
———› Description:
Deletes a host/bot to ask op by number

———› Usage:
/DELASK [network~] :number

———› Details:
Deletes op request from a bot. Use /LISTASK to find out which entry you want to delete.

———› See also:
/ADDASK /LISTASK /DELOP /ADDOP /LISTOPS /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS
[bnc_delautoop]
———› Description:
Deletes an added user who got op

———› Usage:
/DELAUTOOP [network~]number

———› Details:
Deletes an added auto-op entry by number.
You can get the number from LISTAUTOOPS.

———› See also:
/ADDAUTOOP /LISTAUTOOPS /ADDOP /DELOP /LISTOPS /ADDASK /DELASK /LISTASK
[bnc_delban]
———› Description:
Deletes a ban by number

———› Usage:
/DELBAN [network~] :number

———› Details:
Removes a ban from your banlist. Too see what ban you want to remove use /LISTBANS.

———› See also:
/ADDBAN /LISTBANS
[bnc_deldcc]
———› Description:
Deletes a DCC-connection by number

———› Usage:
/DELDCC [network~]number

———› Details:
Deletes a DCC bot connection. You can get the number of DCC link that you want to delete using the /LISTDCC command.

———› See also:
/ADDDCC /LISTDCC
[bnc_delencrypt]
———› Description:
Deletes an encryption entry by number

———› Usage:
/DELENCRYPT [network~]number

———› Details:
DELENCRYPT allows you to remove an added ENCRYPT entry from the list of encryption settings. See /LISTENCRYPT to get the number of the context to be removed.

———› See also:
/ENCRYPT /LISTENCRYPT
[bnc_delignore]
———› Description:
Deletes a hostmask/contentfilter from the ignores

———› Usage:
/DELIGNORE [network~]number

———› See also:
/ADDIGNORE /LISTIGNORES
[bnc_dellink]
———› Description:
Deletes a link to a bouncer (Admin only)

———› Usage:
/DELLINK number

———› Details:
Deletes a bouncer from the bouncenet. You can get the number of the bouncer with LISTLINKS command.
[bnc_dellog]
———› Description:
Deletes a log source by number

———› Usage:
/DELLOG [network~]number

———› Details:
DELLOG allows you to delete an entry to the logging specifications for traffic logging.
To get the number to remove, do LISTLOGS. It is the leading number in front of the entry.

———› See also:
/ADDLOG /LISTLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_delnetwork]
———› Description:
Deletes a network from your client

———› Usage:
/DELNETWORK name

———› Details:
Deletes a network. See ADDNETWORK for further informations.
[bnc_delop]
———› Description:
Deletes an added user who got op

———› Usage:
/DELOP [network~] :number

———› Details:
Deletes a user that can ask op from your bouncer. In order to see a list of users added in your op list use /LISTOPS !

———› See also:
/LISTOPS /ADDOP /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS /ADDASK /DELASK /LISTASK
[bnc_delserver]
———› Description:
Deletes an IRC-server by number

———› Usage:
/DELSERVER [network~] :servernumber

———› Details:
Deletes server. If you find out that some IRC servers are LAGGED or don't allow your connection or you have +r (restricted) connection you can delete them.
Use /LISTERVERS to get the server number that you want to delete.

———› See also:
/ADDSERVER /LISTSERVER
[bnc_deltranslate]
———› Description:
Deletes a translator by number

———› Usage:
/DELTRANSLATE [network~]number

———› Details:
DELTRANSLATE allows you to remove an added translator entry from the list of formerly added translators. See /LISTTRANSLATE to get the number of the context to be removed.

———› See also:
/TRANSLATE /LISTTRANSLATE
[bnc_deluser]
———› Description:
Deletes a user from the bouncer (Admin only)

———› Usage:
/DELUSER login

———› Details:
Deletes a bouncer user. You must be bouncer admin in order to delete a user.

———› See also:
/ADDUSER
[bnc_encrypt]
———› Description:
Encrypts talk to a given channel/user

———› Usage:
/ENCRYPT [network~]password :#channel or nick

———› Details:
Encrypt encrypts talk to a channel or person. This is thought for allowing improved privacy on irc. You need to handshake a key with the person you want to talk to encrypted, then both sides have to set that key to encrypt and decrypt correctly.

———› Example:
/ENCRYPT v1s1t0r :john
If john would also set the same password to your nick, you could talk encrypted. As encryption algorithms blowfish and idea are used.
If you are using ENCRYPT for a channel, then all people on the channel have to set the same password.

/ENCRYPT d0ntkn0w :#leet

———› See also:
/DELENCRYPT /LISTENCRYPT
[bnc_erasemainlog]
———› Description:
Erases the connection log (Admin only)

———› Usage:
/ERASEMAINLOG

———› Details:
Erases the bouncer system log. In order to keep your log up to date you should delete the bouncer system log after you examine it.

———› See also:
/PLAYPRIVATELOG /ERASELOG /PLAYMAINLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_eraseprivatelog]
———› Description:
Erases your message log

———› Usage:
ERASEPRIVATELOG [network~]

———› Details:
Erases your logged messages. In order to keep your log up to date you should delete the messages that you already read using /PLAYPRIVATELOG.

———› See also:
/PLAYPRIVATELOG /PLAYMAINLOG /ERASEMAINLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_erasetrafficlog]
———› Description:
Erases the traffic Log

———› Usage:
/ERASETRAFFICLOG [network~]

———› Details:
Erases your traffig log. In order to keep your log up to date you should delete the messages that you already read using /PLAYTRAFFICLOG last.

———› See also:
/PLAYPRIVATELOG /PLAYMAINLOG /ERASEMAINLOG /PLAYPRIVATELOG /ERASEPRIVATELOG
[bnc_jump]
———› Description:
Jumps to the next IRC-server

———› Usage:
/JUMP [network~] :[number]

———› Details:
Jumps to next server, if no servernumber is given, or to the server by number from LISTSERVERS.
If you are in LAG or something else is wrong you can force bouncer to change servers. In order to do that you must have at least two IRC servers added in serverlist (see /addserver).
JUMP command is also used to trigger VHOSTS or in other situations when displayed.

———› See also:
/LISTSERVERS /ADDSERVER /DELSERVER
[bnc_leavequit]
———› Description:
If set to 1, parts all channels on quit
[bnc_linkfrom]
———› Description:
Adds a bouncer link from your bouncer (Admin only)

———› Usage:
/LINKFROM name :host:port

———› Details:
Allows a link from another bouncer. You can link as many bouncers as you wish.
That won't slow them down. Then you can also chat in bouncer partyline or in the private bouncer channel. Users from other bouncers won't have no access or rights in your bouncer!
If SSL-encryption should be used, is dependent from the installation of SSL-Listeners.

———› Example:
/LINKFROM :this.is.host.of.bouncer.that.is.linking.to.you.com:98765

———› See also:
/LINKTO /NAMEBOUNCER /RELAYLINK
[bnc_linkto]
———› Description:
Adds a bouncer link to the host/port (Admin only)

———› Usage:
/LINKTO :[S=]host:port

———› Details:
Establishes a new link to another bouncer. You can link as many bouncers as you wish. That won't slow them down. Then you can also chat in bouncer partyline or in the bouncer channel. Users from other bouncers won't have access or rights in your bouncer!
If S= is being put in front of the host, psyBNC tries to create an SSL-connection.

———› Example:
/LINKTO :this.is.host.of. bouncer.that.you.are.linking.to.com:54321
Your bouncer (host and port) must be added in the bouncer that you are linking to in order for this connection to work.

———› See also:
/LINKFROM /NAMEBOUNCER /RELAYLINK
[bnc_listallow]
———› Description:
Lists the host allows on your proxy (Admin only)

———› Usage:
/LISTALLOW

———› Details:
LISTALLOW shows all allowed hosts to your bouncer by a numbered index.

———› See also:
/ADDALLOW /DELALLOW
[bnc_listask]
———› Description:
Lists the hosts/bots to ask op from

———› Usage:
/LISTASK [network~]

———› See also:
/ADDASK /DELASK /LISTASK /DELOP /ADDOP /LISTOPS /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS
[bnc_listautoops]
———› Description:
Lists all added auto-ops

———› Usage:
/LISTAUTOOPS [network~]

———› Details:
Displays the list of all added users/hosts which may get auto-op from your bouncer.

———› See also:
/ADDAUTOOP /DELAUTOOP /DELOP /ADDOP /LISTOPS /ADDASK /DELASK /LISTASK
[bnc_listbans]
———› Description:
Lists all bans in your banlist.

———› Usage:
/LISTBANS [network~]

———› See also:
/DELBAN /ADDBAN
[bnc_listdcc]
———› Description:
Lists all added DCC-connections

———› Usage:
/LISTDCC [network~]

———› Details:
Lists the dcc bot connections currently added.

———› See also:
/ADDDCC /DELDCC
[bnc_listencrypt]
———› Description:
Shows a list of encrypted talks

———› Usage:
/LISTENCRYPT [network~]

———› Details:
Shows all entrys for encryptions by a numbered index.

———› See also:
/ENCRYPT /DELENCRYPT
[bnc_listignores]
———› Description:
Lists the currently added ignores

———› Usage:
/LISTIGNORES [network~]

———› See also:
/ADDIGNORE /DELIGNORE
[bnc_listlinks]
———› Description:
Lists all links to/from the bouncer

———› Usage:
/LISTLINKS

———› Details:
Shows all bouncers that are linked into bouncenet showing a link tree, also your locally defined links in list format.

———› See also:
/BWHO
[bnc_listlogs]
———› Description:
Lists all added log sources/filters

———› Usage:
/LISTLOGS [network~]

———› Details:
LISTLOGS shows all entrys from your traffic logging specifications by a numbered index.

———› See also:
/ADDLOG /DELLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_listops]
———› Description:
Lists all added ops

———› Usage:
/LISTOPS [network~]

———› Details:
Lists users that can ask op from your bouncer.

———› See also:
/DELOP /ADDOP /ADDAUTOOP /DELAUTOOP /LISTAUTOOPS /ADDASK /DELASK /LISTASK
[bnc_listservers]
———› Description:
Lists all IRC-servers added

———› Usage:
/LISTSERVERS [network~]

———› See also:
/DELSERVER /ADDSERVER
[bnc_listtasks]
———› Description:
Lists the current running tasks

———› Usage:
/LISTTASKS

———› Details:
Shows the list of tasks currently being run by the scripting engine.

———› See also:
/SRELOAD
[bnc_listtranslate]
———› Description:
Shows a list of translated talks
[bnc_madmin]
———› Description:
Gives a user an admin flag (Admin only)

———› Usage:
/MADMIN user

———› Details:
Declares user to admin bouncer. Warning: the user will have all rights on the bouncer!

———› See also:
/UNADMIN
[bnc_namebouncer]
———› Description:
Names your bouncer (needed for linking) (Admin only)

———› Usage:
/NAMEBOUNCER name

———› Details:
Names your bouncer. The name can be letters or numbers and can be 20 letters long. You need to name the bouncer in order to link it to other bouncers.

———› See also:
/LINKTO /LINKFROM /RELAYLINK
[bnc_password]
———› Description:
Sets your or another users password

———› Usage:
/PASSWORD [user] :newpass

———› Details:
Changes password of you or given user. Make sure you remember your passwords!

———› Example:
/PASSWORD NewPassword
(changes your password)

/PASSWORD newbie :lamer
(Changes password for user newbie into lamer)
If you want to list users in your bouncer use the /BWHO command!
[bnc_playmainlog]
———› Description:
Plays the connection log (Admin only)

———› Usage:
/PLAYMAINLOG

———› Details:
Displays the bouncer system log. All system changes like bouncer link, connections, quits etc. are logged here.

———› See also:
/PLAYPRIVATELOG /ERASEPRIVATELOG /ERASEMAINLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_playprivatelog]
———› Description:
Plays your message log

———› Usage:
/PLAYPRIVATELOG [network~]

———› Details:
Displays logged messages. When you are away all private chats and messages get logged. In order to read them you must use /PLAYPRIVATELOG.

———› See also:
/ERASEPRIVATELOG /PLAYMAINLOG /ERASEMAINLOG /PLAYTRAFFICLOG /ERASETRAFFICLOG
[bnc_playtrafficlog]
———› Description:
Plays the traffic log

———› Usage:
/PLAYTRAFFICLOG [network~]source fromdate fromtime todate totime :filter
/PLAYTRAFFICLOG last

———› Details:
PLAYTRAFFICLOG plays your logged traffic in IRC-alike traffic.

———› Example:
/PLAYTRAFFICLOG #leet 03-02-99 13:20:00 03-02-99 14:20:00 :JOIN
would show you any lines containing JOIN (in most cases channeljoins) from 03-02-99 13:20:00 to 03-02-99 14:20:00.
The traffic itself will be played as it was recorded, so it will appear in the channel if you sourced a channel.
source must be a full qualified nickname or channel.
Date always has to be the format mm-dd-yy.
Time always has to be hh:mm:ss.
Any digit has to be two letters.
Also you can use:
/PLAYTRAFFICLOG last
you will get the last log entrys since you played PLAYTRAFFICLOG last the last time or you deleted the log (see ERASETRAFFICLOG).
Some hints about logging:
- you should filter loggings, or possibly would get an extensive amount of diskspace usage. If you got a quota on your shell, you should use this functionality with maximum care or possibly run out of diskspace fast.
- logging only will happen if you are NOT connected to the bouncer.
- if you define * as filter, anything that happens to the source will be logged.
- you need to care about erasing the traffic log. That happens using ERASETRAFFICLOG. It will erase the whole logfile and start a new one.

———› See also:
/ADDLOG /DELLOG /LISTLOG /ERASETRAFFICLOG
[bnc_relaylink]
———› Description:
Allows or disables a relayable link (Admin only)

———› Usage:
/RELAYLINK name :0|1

———› Details:
Allows or denies relay links from/to the bouncer.
Name is the name of the bouncer. Number 0 means disallow, number 1 means allow link from the bouncer.

———› See also:
/LINKFROM /LINKTO /NAMEBOUNCER
[bnc_relink]
———› Description:
Resets a link to a bouncer by number (Admin only)

———› Usage:
/RELINK linknumber

———› Details:
Allows you to disconnect a link and automatically reconnect it.
This is needed after an encryption setup for the link.

———› See also:
/SETLINKKEY
[bnc_setaway]
———› Description:
Sets your away text when you leave

———› Usage:
/SETAWAY [network~]:text

———› Details:
This command allows you to set an away-text if you leave the bouncer.
The text will be seen in your whois.

———› Example:
/SETAWAY eating
then in your whois would appear:
xyz is away: eating

———› See also:
/SETAWAYNICK /SETLEAVEMSG
[bnc_setawaynick]
———› Description:
Sets your nick when you are offline

———› Usage:
/SETAWAYNICK [network~]nick

———› Details:
This command allows you to set an nick, which will be changed by the bouncer, if you leave the bouncer.

———› Example:
/SETAWAYNICK me|away
the bouncer would change your nick to me/away if you disconnect.

———› See also:
/SETAWAY /SETLEAVEMSG
[bnc_setlang]
———› Description:
Sets the language (global) (Admin only)

———› Usage:
/SETLANG language

———› Details:
Sets the language of the bouncer. The standard-package supports the arguments "english" and "german".
[bnc_setleavemsg]
———› Description:
Sets your leave message when you leave

———› Usage:
/SETLEAVEMSG [network~]text

———› Details:
Sets a message which get posted to the channels if you leave the bouncer.

———› Example:
/SETLEAVEMSG sleeping
then you would see in the channels:
* xyz is away (sleeping)

———› See also:
/SETAWAY /SETAWAYNICK
[bnc_setusername]
———› Description:
Sets your user name

———› Usage:
/SETUSERNAME [network~] :username
[bnc_sockstat]
———› Description:
Shows/Logs the current connections (Admin only)

———› Usage:
/SOCKSTAT

———› Details:
Displays the current status of all connected sockets, included accounting informations, encryption informations etc.
This command can be also used to delete possibly expired sockets from the socket array. If you trigger SOCKSTAT, the socket debug information will also be written to the MAIN-Log.
You can also trigger the logging of socketstats by sending the USR1 signal on the shell.

———› Example:
/SOCKSTAT
[bnc_sreload]
———› Description:
Reloads the script for the user

———› Usage:
/SRELOAD

———› See also:
/LISTTASKS
[bnc_switchnet]
———› Description:
Switches to a given network

———› Usage:
/SWITCHNET newnet :oldnet

———› Details:
This allows you to switch from the current main network to another.
For this your current main connection will become the name "newnet", and "oldnet" will be put to your main connection.

———› See also:
/ADDNETWORK /DELNETWORK
[bnc_translate]
———› Description:
Adds a translator to/from channels/users

———› Usage:
/TRANSLATE [network~]#channel/user :language-from language-to

———› Details:
Translate allows you to set channels or users to be online translated.
Currently possibly are the following translations:
- English to German		en_de
- English to Italian		en_it
- English to French		en_fr
- English to Portugese	en_pt
- English to Chinese		en_zh
- English to Japanese	en_ja
- English to Korean		en_ko
- English to Spanish		en_es
- English to Russian		en_ru
- Deutsch to English		de_en
- Italian zu English		it_en
- French to English		fr_en
- Portugese to English	pt_en
- Japanese to English	ja_en
- Korean to English		ko_en
- Russian to English		ru_en
- Spanish to English		es_en
- French to German		fr_de
- German to French		de_fr
You need to set a channel or a user to be translated and two of the language identifiers (see behind the languages).

———› Example:
/TRANSLATE #italia :it_en en_it
So everything you would get FROM the channel #italia would be translated from italian to english, and in return everything you would post to #italia, would be translated from english into italian.

———› See also:
/DELTRANSLATE /LISTTRANSLATE
[bnc_unadmin]
———› Description:
Removes the admin flag from a user (Admin only)

———› Usage:
/UNADMIN user

———› See also:
/MADMIN