alinho
Membru
 Inregistrat: acum 18 ani
Postari: 62
|
|
<HELP>
As a regular user, you may use these commands in the hub:
+rules -- Displays a listing of the hub rules.
+faq -- Displays a list of helpful links if you are having trouble.
+motd -- Displays the Message of the Day.
+help -- Displays a list of all commands available to you.
+regme -- Send a message to all OPs, asking them to register your nick.
+myip -- Shows you your IP address.
+myinfo -- Shows you information about yourself.
+me -- Replaces +me with your nick, and then sends a message to main chat.
+report <user> <reason> -- Report a user to opchat for breaking the rules.
<HELP>
As a registered user of class 1, there are currently no special commands available to you. Sorry.
<HELP> As a VIP user of class 2, there are currently no special commands available to you. Sorry.
<HELP>
As an OP(level 3), you have the following commands available to you:
Command Arguments Help
!kick <nick> <reason> Kick the user from command line and give a ban equal to the hub's specified tempban time. If you right-click in your client and kick, it does the same thing. If you include _ban_time in the reason, then the ban is extended to the time you specify. Valid entries for time are Ns, Nm, Nh, Nd, NM, Nw, Ny. The IP and the nick are both banned. This is the most reliable and easiest way to ban.
!banip_time <ip> <reason> Bans an IP address _only_ from the hub. Valid entries for time are Ns, Nm, Nh, Nd, NM, Nw, Ny. If you do not include a time, then the ban is permanent. So, '!banip_1M <ip> <reason>' would ban an IP for one month with the reason, and '!banip <ip> <reason>' would perm-ban the IP with the reason. The best use for !banip is if you want to prevent a certain IP (no matter the nick) from entering the hub. If you wish to ban a user who is connected to the hub you should use !kick instead.
!bannick_time <ip> <reason> Bans a nick _only_ from the hub. Valid entries for time are Ns, Nm, Nh, Nd, NM, Nw, Ny. If you do not include a time, then the ban is permanent. So, '!bannick_1M <nick> <reason>' would ban a nick for one month with the reason, and '!bannick <nick> <reason>' would perm-ban the nick with the reason The best use for !bannick is if you want to prevent a certain nick (no matter the IP) from entering the hub. If you wish to ban a user who is connected to the hub you should use !kick instead.
!ban_time <ip> <reason> This bans the IP for the specified time. If a nick with the <ip> has been previously kicked, then that nick is banned too and any user with the <ip> is dropped. If no nick with the <ip> was previously kicked then no nick is banned and no user is dropped. If a nick with the <ip> is later kicked, then that nick is banned for the same time as the <ip>. If you do not include a time, then the ban is permanent. Valid entries for time are Ns, Nm, Nh, Nd, NM, Nw, Ny. So '!ban_1M <ip> <reason>' would ban an ip for one month with the reason. The !kick command is the best way to do the same thing.
!banhost1_time <host> <reason> This bans the top level domain of the host specified. If a time is not included, then this ban is permanent. Be aware that this will ban a great deal of the public from your hub. For example, !banhost1 dynamichost.aol.com would permban the entire .com domain.
!banhost2_time <host> <reason> This bans the second level domain of the host specified. If a time is not included, then this ban is permanent. Be aware that this might ban a large portion of the public from your hub. For example, !banhost2 dynamichost.aol.com would permban the entire aol.com domain.
!banhost3_time <host> <reason> This bans the subdomain of the host specified. Depending on the circumstances, this might be a single host or a large portion of the public. If a time is not included, then this ban is permanent. For example, !banhost3 dynamichost.aol.com would ban the single host "dynamichost", while !banhost3 dynamichost.dsl.aol.com would ban the entire dsl.aol.com domain.
!banhostr1_time <host> <reason> This bans the final subdomain of the host specified. This is almost always a single host. If a time is not included, then this ban is permanent. For example, !banhostr1 dynamichost.aol.com would permban the single host "dynamichost", as would !banhostr1 dynamichost.dsl.aol.com.
!banprefix_time <prefix> <reason> This bans any user with <prefix> at the beginning of their nick. If a time is not included, then this ban is permanent. So, !banprefix <OP> <reason> would ban users [OP]someguy and [op]someguy, but not someguy[OP] or someguy[op].
!banrange_time <range> <reason> Bans a range of IP addresses. This may either be specified as <start_ip-end_ip> or <CIDR_notation>. If you are not familiar with CIDR, do not use it, as it may have unpredictable results if you do. If a time is not included, then this ban is permanent. As an example of proper usage, !banrange 207.46.236.0-207.46.236.255 <reason> and !banrange 207.46.236.0/24 <reason> would both permban the same range of addresses.
!unban <ip> or <nick> Unban IP and nick for the user. If a nick is associated with an ip or an ip is associated with a nick, then both are removed. This also removes bans that were issued with !kick.
!unbanhost1 <host> <reason> Unbans the top level domain of the host specified.
!unbanhost2 <host> <reason> Unbans the second level domain of the host specified.
!unbanhost3 <host> <reason> Unbans the subdomain of the host specified.
!unbanhostr1 <host> <reason> Unbans the final subdomain of the host specified.
!unbanprefix <prefix> <reason> Unbans the prefix specified.
!unbanrange <range> <reason> Unbans the IP address range. <range> may either be the range, or any IP within the range. For example, !unbanrange 192.168.0.0/16 <reason> and !unbanrange 192.168.0.1 <reason> will both do the the same thing.
!hidekick <nick> <reason> Kicks a user and does not announce it to the hub.
!hideme <class> Hides yourself from users below the specified class.
!infoban <ip> or <nick> Shows ban information of the given nick or IP.
!infoban_ipban_ Shows all current IP bans. Not very useful if you have thousands of them.
!infoban_nickban_ Shows all current nickbans. Also not very helpful on a big hub.
!infoban_banrange_ Shows all current banned ranges. Very good for showing the ranges you might have forgotten you banned. While you are learning how to rangeban, it is recommended that you use this command after !banrange to see what you did.
!lsban 100 Shows the most recent 100 bans.
!getip <nick> Prints user's IP address.
!gethost <nick> Prints user's FQDN. This works only if dns_lookup = 1 in the hub config.
!getinfo <nick> Prints user's IP and FQDN.
!reginfo <nick> Prints a registered user's full information.
!whoip <ip> Prints all users who have the specified IP.
!whorange <range> Prints all users and their IPs who have an IP in <range>. As with the !banrange command, <range> may either be <from_ip-to_ip> or <CIDR notation>. This command is useful before you ban a range, to see how many users it will affect.
!regs <message> Sends the <message> to all registered users.
!ccbroadcast <:CC:> <msg> Sends a broadcast to users os the specified country code(s) only. For example, !ccbroadcast :PL:SE:US: <msg> would send the message to all users of Sweden, Poland, and the US.
!flood <nick> Floods a user off of the hub.
!nosearch <nick> <time> Prevents the user from using the search function until he restarts his session or until <time> has expired. If you leave the <time> blank, then the time is set for one week. Valid entries for <time> are Ns, Nm, Nh, Nd, NM, Nw, Ny. So '!nosearch <nick> 5m would stop the user from searching for 5 minutes or until he reconnected.
!unnosearch <nick> Allows a user to use the search function of the hub when he has been forbidden previously by !nosearch.
!noctm <nick> Prevents the user from connecting to others until he restarts his session or until <time> has expired. If you leave the <time> blank, then the time is set for one week. Valid entries for <time> are Ns, Nm, Nh, Nd, NM, Nw, Ny. So '!gag <nick> 1h would stop the user from chatting for 1 hour or until he reconnected.
!unnoctm <nick> Allows a user to connect to others when he has been forbidden previously by !noctm.
!gag <nick> <time> Prevents the user from using the chat function until he restarts his session or until <time> has expired. If yo
u leave the <time> blank, then the time is set for one week. Valid entries for <time> are Ns, Nm, Nh, Nd, NM, Nw, Ny. So '!gag <nick> 1h would stop the user from chatting for 1 hour or until he reconnected.
!ungag <nick> Allows a user to use the chat function of the hub when he has been forbidden previously by !gag.
!help Gives a help on all available commands.
<HELP>
As a CHIEF(level 4), you have all of the following commands available to you:
Command Arguments Help
!broadcast <message> Sends the message to all user's PMs; all replies are sent back to you in PM from Hub-Security.
!regnew <nick> <class> Registers new user. If you do not specify <class>, the user is registered with a class of 1. You can not register users with a class higher than your class - 2.
!regpasswd <nick> Allows registered nick to change his password (he has to use command +passwd <pass>
!regpasswd <nick> <pass> Allows you to change a registered user's pass if he can't figure out how to do it himself, for example.
!regdisable <nick> Disable a user's registration, but he can be re-enabled later. You should use this if you only want to punish a user for example.
!regenable <nick> Enable a user's registration, when he was previously disabled with !regdisable
!regdelete <nick> Destroys a registered user by removing him from the database. If you later change your mind, you must register the user all over again. You should use this if you want to permanently remove a user.
!regclass <nick> <class> Changes a previously registered user's class to <class>. You cannot change a user to a class higher than yours - 2.
!class <nick> <class> Temporarily changes a user's class to <class>. This stays in effect until the user reconnects his session.
!regprotect <nick> <class> Protects a registered user from being kicked/banned etc. by a user of a class lower than <class>. The user does not have to be in the hub.
!protect <nick> <class> Protects an unregistered user from being kicked/banned etc. by a user of a class lower than <class>. The user must be currently connected to the hub for this to take effect.
!drop <nick> Disconnects user from hub without giving him a reason and without banning him.
!topic <topic> Change the topic shown in the top of the client window.
<HELP>
As an ADMIN(level 5), you have all of the commands listed hereafter available to you. Also, you may manipulate the configuration of the hub from the command line. Please proceed with caution. If you don't know what a configuration variable does, don't touch it.
Command Arguments Help
!gc Prints a list of all configuration variables that can be inserted into the database.
!set <variable> <new_value> Allows manipulation (through the hub) of all configuration variables. As an example, '!set tban_kick 86400' would set the variable tban_kick to 86400 seconds.
!ftedit <trigger> <contents> Replaces trigger's content with contents. For example !ftedit +help newhelp would change the +help to output newhelp.
!ul <limit> <time_in_minutes> Temporarily change the user limit to <limit>. If <time_in_minutes> is not specified, 60 minutes is assumed.
!hublist Sends your hub information to the public hublist. If you do this more often than every 15 minutes, you may be banned by the hublist server.
!reload Reloads verlihub's configuration. NOTE: Some configuration changes require the hub to be restarted!
!protoall_hubname This sends a new hubname to all currently connected users.
!protoall_pm <msg> This sends a pm from your nick to everyone in the hub.
!protoall_chat <msg> Sends <msg> to main chat from your nick.
!protoall_redir <hub_address> This forces a hub redirection for all users to <hub_address>.
!protoall_any <msg> Sends <msg> to main chat, without showing that it was you who sent it.
!protoactive_* This sends any of the protoall_* commands above to active users only. As an example, !protoactive_any <msg> would send a message to main chat that only active users could see.
!protohello_* This sends any of the protoall_* above to users whose clients don't support the NoHello feature only. As an example, !protohello_any <msg> would send a message to main chat that only clients that require $Hello could see.
<HELP>
As the MASTER(level 10), you have absolute control of the hub. The following command shuts it down:
!quit
!restart
===========================================
Nu sunt Toate
_______________________________________
عنيف النصب هيأ أصبح أي
|
|
