The following rules must be maintained and followed by all of BanglaCafe’s administrative group at all times. Failure to do so may result in loss of status. Please note that the Main Network Administrators of BanglaCafe are, up to a point, exempted from these rules. However, they are still required to follow them, out of common courtesey. - Banglacafe Administrative Group

Rules for AOPs :-

 
  • Never under any circumstance should you kick or ban another op or member of Banglacafe’s administration. Not even for “fun.” Do Not Kick any op from #bangladesh, unless it is necessary. Kicking another op might cause your Deop, if he/she complains about that to an admin.
     
  • The only exception to the above rule is, if the op you are kicking, has a problem with his/her mirc script, eg. it’s auto kicking users.
     
  • Never kick a user/chatter/member unless it is absolutely necessary for you to do so. Do Not Abuse your power. Do Not kick for any personal reasons. Every kick must have a Valid Reason. Do Not kick some one for using slang or bad language in Pvt. Add the person in ignore list if its too irritating. The command is /ignore nick (for mirc users).
     
  • Only exceptions to kicking someone out is if 1) They are advertising other chat sites or bad websites, 2) Using extreme slangs and/or vulgar language in #channel, even after you have warned them not to, at least 2 times; 3) If you suspect that someone is trying to or was going to flood. (and reason why you suspected him/her), and lastly 4) If they are being very disrespectful towards BanglaCafe.
     
  • Do NOT change and/or play around with channel modes!!! Unless you are absolutely certain of what that channel mode will do. You will be held responsible for your actions, and the consequences of those actions.
     
  • To supress any troubles in the main #bangladesh channel, use the ban command via op Bot. If any user curses in main or disturbs other users, use ban command on him/her (!ban nick). Do Not ban or kick users for fun or testing!
     
  • Do Not Pass Op in #bangladesh or #support, to anyone; everyone must either identify to ChanServ or OPServ to gain their status. Do Not fight with other Aops/Sops or IRcops in #bangladesh. If you have a problem with someone, discuss it in #support. And let any Admin know if you think any of your superiors or your fellow ops are doing something wrong, or any injustice towards you.
     
  • Do Not add any (+h)Hops or (+v)Vops without an Admin’s permission. Do Not share your Op pass or op nick/pass with anyone. If caught or suspected, you will lose your status.
     
  • Being an Aop is still a privilege. The reason you were chosen among others is because of your dedication and loyalty to BanglaCafe, among other criterias. As an AOP, you are suppose to take care of the channel(s) in BanglaCafe server. So Keep your eyes open for flooders or advertiser. You will not be penalized if you kick/ban any one who was flooding or advertising, or going to do either of those. And always help users if they need any help.
     
  • Try to be present and active in #bangladesh room. It is your duty to keep your Op nick active. If you lose your op pass or your nick drops because of prolong inactivity for a long absence, you may not get your status back. If you are kicking someone for BAD nick, then before kicking give him/her at least 2/3 warnings, and time to change the nick. Try to avoid kicking as much as possible. Do Not run any bot script(s), trivia bots, or auto kick/ban script(s) without a Network Administrator’s permission. There is no exceptions.
     
  • Last but not least, you are smart! Follow these rules, and use your best judgement before doing something. Remember, these chatters are people too. Before doing something, sometimes put yourself in their shoes, and think how you would react to an action, if the roles were reversed. And always listen to and follow the requests of your superiors.



Rules for SOPs :-

 

  • ALL of the above AOP rules also apply for a SOP. And SOPs are encouraged to strictly follow those rules.
     
  • Please do not abuse your authority over AOPs. If there is a complaint against you, you will be demoted back to AOP status.
     
  • All SOPs are to follow the guidelines set out by the admins.
     
  • Please Do Not add (+v)Vops, (+h)Hops, or (+o)Aops without first informing an admin about your decision to add that person, and why. Although you will have freedom to add someone in the channel in any of the above 3 positions, you must still secure permission from an admin, and put up a topic in #support. The final decision regarding your request to add someone will ultimately rest on the admin, so do not bother him/her over and over. It might affect you negatively.
     
  • For both AOPs and SOPs: Please do not bother or bug an admin about your promotion. We know who you are, and what you do in the time you come to BanglaCafe to chat. If we think you are worthy, you will be promoted to IRCop and above. There is no set time limitation on when you can or will be promoted. That decision rests solely on the Network Admins.



Rules for IRCOPs, CO-/Server/Services-Admins :-

 

  • ALL of the above AOP and SOP rules also applies for an IRCOP, Co-Admin, Server-Admin, and/or Services-Admin. And all members in the above categories are encouraged to strictly follow those rules. You all represent BanglaCafe so please be in your best behavior and attitude at all times.
     
  • For all who are unsure, the hierarchy or chain of command goes like this. After AOP/SOP comes IRCop, and then comes Co-Admin, followed by Server-Admin, and finally Services-Admin. This means, Services-Admins have top authority, under Network Admins.
     
  • All AOPs/SOPs are to follow IRCops, who are to follow Server Admins, who are to follow Services Admins, who will ultimately follow the Network Admins! Any Questions?!
     
  • This is the chain of command, and must always be followed. If you decline a request made to you by someone who has authority over your status, you will have to have a valid reason for declining that request.
     
  • If you are being asked to do something, and you don’t want to, talk to a Network Admin about it. Please do not fight amongst yourselves. We all come to chat for fun and to have a good time.
     
  • If you are not comfortable with this method of authority, then please ask someone with a higher status to have your status removed.
     
  • This applies to anyone who has a higher status level (and when addressing someone with a lower status level): Please Do Not abuse and/or misuse your power and authority. Keep in mind that online or offline, that person might be mature and older than you are. So respect your elders.
     
  • Do Not Kill, Kline, Gline, Zline, GZline, or Shun any chatter or member or even another person from BanglaCafe’s administrative group, for fun or silly, or inappropriate reasons! You will be reprimanded for your actions. As a consequence, you may lose all your status levels.
     
  • Do Not run any bots without first consulting a Network Admin.
     
  • At any of these levels, you have serious power in an ircd server. Please be very very very careful while trying to execute any commands, especially those of whom you’re unsure about. You will be punished for your actions. There is no exceptions whatsoever. “I was testing”, or “I did not know what that would do” simply won’t cut it!
     
  • For a list of commands, check out BanglaCafe’s Info page with the link to the commands section.
     
  • Do Not kill/kline the OP serving Bots or any server bots, unless absolutely neccessary, or if it’s malfunctioning.
     
  • Always follow and abide by the rules set out by the Network Administrators. There are no exceptions!



Rules for Network-Admins :-

 

  • All Network Administrators are requested to set the proper example for BanglaCafe’s administrative groups, eg. AOPs, SOPs, IRCOps, Co-Admins, Server-Admins, and Services-Admins etc.
  • All Network Administrators are requested to keep an eye out for any trouble among the lower ranks, and to dispute, and resolve and issues.
  • All Network Administrators are requested to provide help and support to the other admins, if and when needed.
  • Although there is no specific set of rules for Network Admins to follow, All Network Administrators are requested to follow, abide, and encourage the above set of rules, whenever neccessary.
 

UnrealIRCD Commands

IRC Users Commands

*** NICK Command ***


Changes your “Online Identity” on a server. All those in the channel you are in will be
alerted of your nickname change.

Syntax: NICK <new nickname>
Example: NICK hAtbLaDe1

*** WHOIS Command ***

Shows information about the user in question, such as their “Name”, channels they are
currently in, their hostmask, etc.

Syntax: WHOIS <user>
Example: WHOIS hAtbLaDe

*** WHO Command ***


Searches User Information (-i users only) for supplied information. IRCops are able to
search +i users & can use masks only. When used on a channel , it will give a list of
all the non-invisible users on that channel.

Syntax: WHO <mask>
WHO <nickname>
WHO <#channel>
WHO 0 o (Lists all Online IRC Operators currently online and not +i)
Example: WHO *.aol.com
WHO *Bot*
WHO #UnrealIRCd

*** WHOWAS Command ***

Retrieves previous ‘WHOIS’ information for users no longer connected to the server.

Syntax: WHOWAS <nickname>
WHOWAS <nickname> <max number of replies>
Example: WHOWAS hAtbLaDe

*** NAMES Command ***

Provides a list of users on the specified channel.

Syntax: NAMES <channel>
Example: NAMES #Support

*** ISON Command ***

Used to determine of a certain user or users are currently on the IRC server based upon
their nickname.

Syntax: ISON <user> <user2> <user3> <user4>
Example: ISON hAtbLaDe NickServ ChanServ OperServ MemoServ

*** JOIN Command ***

Used to enter one or more channels on an IRC server. All occupants of the channel will be
notified of your arrival. JOIN with 0 as a parameter makes you Part all channels.

Syntax: JOIN <chan>,<chan2>,<chan3>
JOIN 0 (Parts all channels)
Example: JOIN #Support
JOIN #Support,#Lobby

*** PART Command ***

Used to part (or leave) a channel you currently occupy. All those in the channel will be
notified of your departure.

Syntax: PART <chan>,<chan2>,<chan3>,<chan4>
Example: PART #Support
PART #Lobby,#Support

*** MOTD Command ***

Displays the Message Of The Day.

Syntax: MOTD
MOTD <server>

*** RULES Command ***

Reads the ircd.rules file and sends the contents to the user.

Syntax: RULES
RULES <server>

*** LUSERS Command ***

Provides Local and Global user information (Such as Current and Maximum user count).

Syntax: LUSERS

*** MAP Command ***

Provides a “Network Map” of the IRC network. Mainly used for routing purposes.

Syntax: MAP

*** QUIT Command ***

Disconnects you from the IRC server. Those in the channels you occupy will be notified of
your departure. If you do not specify a reason, your nickname becomes the reason.

Syntax: QUIT <reason>
Example: QUIT Leaving!

*** PING Command ***

The PING command is used to test the presence of an active client or
server at the other end of the connection. Servers send a PING
message at regular intervals if no other activity detected coming
from a connection. If a connection fails to respond to a PING
message within a set amount of time, that connection is closed. A
PING message MAY be sent even if the connection is active.
Note that this is different from a CTCP PING command..

Syntax: PING <server> <server2>
Example: PING irc.fyremoon.net
PING hAtbLaDe
PING hAtbLaDe irc2.dynam.ac

*** PONG Command ***

PONG message is a reply to ping message. If parameter <server2> is
given, this message will be forwarded to given target. The <server>
parameter is the name of the entity who has responded to PING message
and generated this message.

Syntax: PONG <server> <server2>
Example: PONG irc.fyremoon.net irc2.dynam.ac
(PONG message from irc.fyremoon.net to irc2.dynam.ac).

*** VERSION Command ***

Provides version information of the IRCd software in usage.

Syntax: VERSION
VERSION <server>

*** STATS Command ***

Provides certain Statistical information about the server

Syntax: STATS <flags>
Example: STATS u

### Stats Flags ###

k = Lists all the current K:Lines, Z:Lines (Banned hosts/IP) & E:Lines (K:Line exceptions)
g = Lists all the current G:Lines (Banned hosts) & Shuns
E = Lists all the current E:Lines (K:Line Exceptions)
f = Lists all the current F:lines (Filename masks on DCCDENY)
O = Lists all the current O:Lines (IRC Operator Lines)
Q = Lists all the current Q:Lines (Forbidden Nicks)
C = Lists all the current C/N:Lines (Servers to connect or accept connects from)
H = Lists all the current H:Lines (Hub Lines) & L:Lines (Leaf Lines)
n = Lists all the current n:Lines (GECOS Deny)
V = Lists all the current VHost lines
T = Lists all the current T:Lines (Specific MOTD/Rules Lines)
Y = Lists all the current Y:Lines (Connection classes)
U = Lists all the current U:Lines (Usually Services)
v = Lists all the current V:Lines (Version Deny)
D = Lists all the current D:Lines (Disallow Lines-Oper & Server Orig Connects)
d = Lists all the current d:Lines (Disallow Lines-Autoconnects)
e = Lists all the current e:Lines (Proxy scan exempt IPs)
I = Lists all the current I:Lines (Client auth Lines)
F = Lists all the current F:Lines (DCCDENY Lines)
r = Lists all Channel Restrict lines
N = Lists the Network Configuration report
S = Gives the Dynamic Configuration report
W = Gives the current Server Load
q = Lists all the SQLINEed Nicks
u = Server Uptime
m = Gives the Server command list
z = Gives Misc Server Information
s = Returns the scache and NS numbers
t = Returns Misc Info
L = Information about current server connections

*** LINKS Command ***

Lists all of the servers currently linked to the network.

Syntax: LINKS

*** ADMIN Command ***

Provides Administrative information regarding the server.

Syntax: ADMIN <server>

*** USERHOST Command ***

Returns the userhost of the user in question. Usually used by scripts or bots to retrieve
userhost information.

Syntax: USERHOST <nickname>
Example: USERHOST hAtbLaDe

*** TOPIC Command ***

Sets/Changes the topic of the channel in question, or just display the current Topic.

Syntax: TOPIC <channel>
TOPIC <channel> <topic>
Example: TOPIC #operhelp
TOPIC #Lobby Welcome to #Lobby!!

*** INVITE Command ***

Sends a user an invitation to join a particular channel. You must be an Operator on the
channel in order to invite a user into it.

Syntax: INVITE <user> <channel>
Example: INVITE hAtbLaDe #Support

*** KICK Command ***

Removes a user from a channel. Can only be used by Operators or Half-Ops. If no reason is
specified, your nickname becomes the reason.

Syntax: KICK <channel>[,<channel2>..] <user>[,<user2>..] <reason>
Example: KICK #Lobby foobar Language!
KICK #Lobby,#OperHelp Lamer23,Luser12 Lamers!

*** AWAY Command ***

Sets your online status to “Away”.

Syntax: AWAY <reason> (Marks you as ‘Away’ with the reason given)
AWAY (Un-marks you as ‘Away’)
Example: AWAY Lunch time!

*** WATCH Command ***

Watch is a new notify-type system in UnrealIRCd which is both faster
and uses less network resources than any old-style notify
system. The server will send you a message when any nickname
in your watch list logs on or off.
The watch list DOES NOT REMAIN BETWEEN SESSIONS - you (or your
script or client) must add the nicknames to your watch list every
time you connect to an IRC server.

Syntax : WATCH +nick1 +nick2 +nick3 (Add nicknames)
WATCH -nick (Delete nicknames)
WATCH (View the watchlist)

*** HELPOP Command ***

HelpOp is a new system of getting IRC Server help. You type either
/HELPOP ? <help system topic> or /HELPOP ! <question>
The “?” in /HELPOP means query the help system and if you get no
response you can choose ‘!’ to send it to the Help Operators online
Using neither ? nor ! will mean the command will be first queried
within the help system and if no match if found , it will be
forwarded to the help operators.

Example: HELPOP ?CHMODES (Channel Modes Help)
HELPOP ?UMODES (User Mode Help)

*** LIST Command ***

Provides a complete listing of all channels on the network. If a search string is
specified, it will only show those matching the search string.

Syntax: LIST <search string>
Example: LIST
LIST *ircd*

New extended /LIST command options are supported. To use these
features, you will likely need to prefix the LIST command with
/QUOTE to avoid your client interpreting the command.

Usage: /QUOTE LIST options

If you don’t include any options, the default is to send you the
entire unfiltered list of channels. Below are the options you can
use, and what channels LIST will return when you use them.
>number List channels with more than <number> people.
<number List channels with less than <number> people.
C>number List channels created between now and <number> minutes ago.
C<number List channels created earlier than <number> minutes ago.
T>number List channels whose topics are older than <number> minutes
(Ie., they have not changed in the last <number> minutes.
T<number List channels whose topics are newer than <number> minutes.
*mask* List channels that match *mask*
!*mask* List channels that do not match *mask*

NOTE : C & T parameters do not exist in Unreal 3.1.1-Darkshades.
LIST defaults to sending a list of channels with 2 or more members,
so use the >0 option to get the full channel listing.

*** PRIVMSG/NOTICE Command ***

PRIVMSG and NOTICE, which are used internally by the client for
/msg and /notice, in UnrealIRCd support two additional formats:
/msg @#channel <text> will send the text to channel-ops on the
given channel only. /msg @+#channel <text> will send the text
to both ops and voiced users on the channel. While some clients
may support these as-is, on others (such as ircII), it’s necessary
to use /quote privmsg @#channel <text> instead. You can also use
% to signify HalfOps on the channel.

Syntax: MSG <nick>,<nick2>,<nick3>,<nick4> :<text>
Example: PRIVMSG hAtbLaDe :Hello.
PRIVMSG hAtbLaDe,Hatter,GoodBot :Hello everyone!

The format for the NOTICE command is the same as above.

**** KNOCK Command ****


For channels which are invite only, you can “Knock” on the channel to request an invite.

The following criteria must be met :
- Channel is not +K (No knocks)
- Channel is not +I (No invites!)
- You’re not banned!
- And you are not already there

Syntax: KNOCK <channel> <message>
Example: KNOCK #secret_chan I’m an op, let me in!

*** SETNAME Command ***


Allows users to change their ‘Real name’
directly online at IRC without reconnecting

Syntax: SETNAME <New Real Name>

*** VHOST Command ***

Hides your real hostname with a virtual hostname provided by the IRC server , using SetHost.

Synatx: VHOST login password
Example: VHOST IWant newhost

*** MODE Command ***

Sets a mode on a Channel or User.
UnrealIRCd has got some new Channel & User modes.

Syntax: MODE <channel/user> <mode>
Example: MODE #Support +tn
MODE #Support +ootn hAtbLaDe cb

### Channel Modes ###

p = Private channel
s = Secret channel
i = Invite-only allowed
m = Moderated channel, noone can speak except users with mode +voh
n = No messages from outside channel
t = Only channel operators may set the topic
r = Channel is registered
R = Requires a registered nickname to join the channel
c = No ANSI color can be sent to the channel (ColourBlock)
q = Channel owner
(*)Q = No kicks able in channel unless by U:Lines
O = IRCop only channel (Setable by IRCops)
A = Administrator only channel (Setable by Admins)
K = /Knock is not allowed
V = /Invite is not allowed
S = Strip all incoming colours away
l <number of max users> = Channel may hold at most <number> of users
b <nick!user@host> = Bans the nick!user@host from the channel
k <key> = Needs the channel key to join the channel
o <nickname> = Gives operator status to the user
v <nickname> = Gives voice to the user (May talk if chan is +m)
L <chan2> = If +l is full, the next user will auto-join <chan2>
a <nickname> = Gives protection to the user (No kick/drop)
e <nick!user@host> = Exception ban - If someone matches it
they can join even if a ban matches them
(**)h <nickname> = Gives halfop status to the user
f[*]<lines>:<seconds> = Flood protection, if the * is given a user will
be kick banned when they send <lines> in <seconds>
If * is not given they are just kicked
H = No +I users may join that channel. (Setable by Admins).
N = No nickname changes are permitted in the channel.
^ = Reports Channel modes in bitstring.
(Only exists in Development Versions i.e #define DEVELOP)
G = Makes the channel G Rated. Any words in badwords.channel.conf
are replaced with <censored> in channel messages.
u = “Auditorium”. Makes /names and /who #channel only show @’s
C = No CTCPs allowed in the channel.
z = Only Clients on a Secure Connection (SSL) can join.

(*) Channel mode +Q
This is the ‘peace’ mode. Noone can kick each other
except by U:Lines. Bans can be placed though.

(**) Channel halfops (+h)
If you are marked as halfop (% in /names) you can do:
- Set topic
- Kick non-ops
- Set modes +vmntibe

### User Modes ###

O = Local IRC Operator
o = Global IRC Operator
i = Invisible (Not shown in /who searches)
w = Can listen to wallop messages
g = Can read & send to globops, and locops
h = Available for help
s = Can listen to server notices
k = See’s all the /KILL’s which were executed
S = For services only. (Protects them)
a = Is a Services Administrator
A = Is a Server Administrator
N = Is a Network Administrator
T = Is a Tech Admininistator
C = Is a Co Administrator
c = See’s all Connects/Disconnects on local server
f = Listen to flood alerts from server
r = Identifies the nick as being registered
x = Gives the user hidden hostname
e = Can listen to server messages sent to +e users
b = Can read & send to chatops
W = (IRC Operators only) Lets you see when people does a /whois on you
q = (Services Admins only) Only U:lines can kick you
B = Marks you as being a Bot
F = Lets you recieve far Connect notices & Local notices.
I = Invisible Join/Part. Makes you being hidden at channels
H = (IRC Operators only) Hide IRC Operator status in /who and /whois
d = Makes it so you can not recieve channel messages
v = Receive infected DCC send rejection notices
t = Says that you are using a /vhost
G = Filters out all bad words (badwords.message.conf) in messages with <censored>
z = Marks the client as being on a Secure Connection (SSL).

*** CREDITS Command ***

This command will list the credits to all the people who helped create UnrealIRCd

Syntax: CREDITS
CREDITS <server>

*** DALINFO Command ***

This command will list the Credits that the Dreamforge IRCd team/the IRCd developers
from the start when IRCd got developed

Syntax: DALINFO
DALINFO <server>

*** LICENSE Command ***

This command shows the GNU License Which is hard-coded into the IRCd

Syntax: LICENSE
LICENSE <server>

*** TIME Command ***

Lists the current Server Date and Time.

Syntax: TIME
TIME <server>

*** BOTMOTD Command ***

Lists the IRCd Bot Message Of The Day

Syntax: BOTMOTD
BOTMOTD <server>

*** SILENCE Command ***

Ignores messages from a user or list of users at the Server itself.

Syntax: SILENCE +<nickname> (Adds a nickname to SILENCE list).
SILENCE -<nickname> (Removes a nickname from the SILENCE list).
SILENCE (Lists the current SILENCE list)

*** IDENTIFY Command ***

An alias to allow you to identify to NickServ or ChanServ with your password.
If it cannot find NickServ or ChanServ , it will report services as down.

Syntax: IDENTIFY <password> (Identify to NickServ)
IDENTIFY #<channel> <password> (Identify to ChanServ as Founder of #channel)

IRC Operator Commands

*** OPER Command ***

Attempts to give a user IRC Operator status.

Syntax: OPER <uid> <password>
Example: OPER hAtbLaDe foobar234

*** WALLOPS Command ***

Sends a “Message” to all those with the umode +w. Only IRCops can send wallops,
while anyone can view them.

Syntax: WALLOPS <message>

*** GLOBOPS Command ***


Sends a global “Message” to all IRCops. Only viewable by IRCops
(unlike WALLOPS, which can be viewed by normal users).

Syntax: GLOBOPS <message>
Example: GLOBOPS Going to be akilling those clones…

*** CHATOPS Command ***

GLOBOPS is usually reserved for important network information. Therefore, for Oper Chat,
CHATOPS was invented. IRCops with the +c flag enabled will be able to send/receive CHATOPS messages.

Syntax: CHATOPS <message>
Example: CHATOPS How’s everyone doing today?

*** LOCOPS Command ***

Similar to GLOBOPS, except only received by those IRCops local to your server.

Syntax: LOCOPS <message>
Example: LOCOPS Going to be adding a temp k:line for that user…

*** ADCHAT Command ***

This command sends to all Admins online
Only for Admins. This is a ChatOps style command

Syntax: ADCHAT <text>
Example: ADCHAT Hey guys!

*** NACHAT Command ***

This command sends to all NetAdmins & TechAdmins online
Only for Net/Techadmins. This is a ChatOps style command

Syntax: NACHAT <text>
Example: NACHAT Hey guys!

*** TECHAT Command ***

This command sends to all TechAdmins online
Only for Net/Techadmins. This is a ChatOps style command

Syntax: TECHAT <text>
Example: TECHAT Hey guys!

*** KILL Command ***

Forcefully Disconnects a user from an IRC Server.
IRC Operators only.

Syntax: KILL <user> <reason>
Example: KILL Clone5 Cloning is not allowed

*** KLINE Command ***


“Bans” a hostmask from connection to the IRC server.
The user can however connect to other servers on the network !!
IRC Operators only.

Syntax: KLINE <hostmask> <reason>
Example: KLINE *@*.aol.com Abuse

*** UNKLINE Command ***

Removes a k:line from the server.
IRC Operators only.

Syntax: KLINE -<hostmask>
Example: KLINE -*@*.aol.com

*** ZLINE Command ***

Disables all access to the IRC server from a specified IP.
The IP can however connect to other servers on the network !!
IRC Operators only.

Syntax: ZLINE <ip> :reason
Example: ZLINE 127.0.0.1 :Localhost

*** UNZLINE Command ***

Removes a currently active z:Line.
IRC Operators only.

Syntax: ZLINE <ip>
Example: ZLINE -*@127.0.0.1

*** GLINE command ***

This command provides timed G:Lines. If you match
a G:Line you cannot connect to ANY server on the
IRC network. A time of 0 in the GLINE makes it permanent (Never Expires).
In Unreal 3.1.1 you may also specify the time in the format 1d10h15m30s.
IRC Operators only.

Syntax: GLINE <user@host mask> <seconds to be banned> :<reason> (Adds a G:line for user@host)
GLINE -<user@host mask> (Removes a G:line for user@host)
Example: GLINE *@*.dal.net 900 :Spammers (Adds a 15 min G:line)
GLINE *@*.dal.net 1d5h :Spammers (Adds a 29 hour G:line)

*** SHUN Command ***

Prevents a user from executing ANY command except ADMIN and respond to Server Pings.
This effectively prevents them from doing anything on the server.
A time of 0 on the SHUN makes it permanent (Never Expires).
In Unreal 3.1.1 you may also specify the time in the format 1d10h15m30s.
IRC Operators only.

Syntax : SHUN <nickname> <time> :<Reason> (Shun the nickname for time)
SHUN +<user@host> <time> :<Reason> (Shun the user@host for time)
SHUN -<user@host> (Removes the SHUN for user@host)
SHUN (View the current SHUN list)

Example : SHUN +foobar@aol.com 600 :Spamming (Shuns foobar@aol.com for 10 mins for Spamming)
SHUN +foobar@aol.com 1d6h :Spamming (Adds a 30 hour SHUN)

*** GZLINE Command ***


This command provides timed global Z:line. If you match a Global Z:Line you cannot
connect to ANY server on the IRC network
A time of 0 in the GZLINE makes it permanent (Never Expires).
You may also specify the time in the format 1d10h15m30s.
IRC Operator only command.

Syntax: GZLINE <user@host mask> <seconds to be banned> :<reason>
(Adds a Global Z:line for user@host)
GZLINE -<user@host mask> (Removes a Global Z:line for user@host)
Example: GZLINE *@*.dal.net 900 :Spammers (Adds a 15 min Global Z:line)
GZLINE *@*.dal.net 1d5h :Spammers (Adds a 29 hour Global Z:line)

*** AKILL Command *** (Use Services AKILL Instead)

Adds an Autokill for the specific host mask. This prevents any user from that
hostmask from connecting to the network.
Services Admin & above only ..

Syntax : AKILL <user@host> :<Reason>
Example : AKILL foo@aol.com :Spammers!

*** RAKILL Command *** (Use Services AKILL Instead)

Removes an AKILL set by an IRC Operator or Services.
Services Admin & above only ..

Syntax : RAKILL <user@host>

*** REHASH Command ***

Prompts the server to reread the configuration files.
IRC Operators only.

Syntax: REHASH <servername> -<flags>
REHASH -<flags>

If servername and flags are not specified this rehashes the ircd.conf , removing
any temporary k:lines.
If servername is specified, this is used to rehash config files on servername
Only TechAdmins and NetAdmins may specify a server name

The flags are used to rehash other config files, valid flags are:
-dccdeny - Rehashes dccdeny.conf
-dynconf - Rehashes UnrealIRCd Config and Network file
-restrict - Rehashes chrestrict.conf
-vhost - Rehashes vhost.conf
-motd - Rehashes all MOTD files and RULES files (including T:lines)
-opermotd - Rehashes the OPERMOTD
-botmotd - Rehashes the BOTMOTD
-garbage - Force garbage collection
-badwords - Rehashes the badwords config.

*** RESTART Command ***

Kills and restarts the IRC daemon, disconnecting all users currently on that server.
IRC Operators only.

Syntax: RESTART
RESTART <password>
RESTART <server> <password>

*** DIE Command ***

Kills the IRC daemon, disconnecting all users currently on the current server.
IRC Operators only.

Syntax: DIE
DIE <password>

*** LAG Command ***

This command is like a Sonar or Traceroute for IRC servers
You type in /LAG irc.fyremoon.net and it will
reply from every server it passes with time and so on
Useful for looking where lag is and optional TS future/past travels

Syntax: LAG <servername>

*** SETHOST Command ***

This command is so you can change your
Virtual host (hiddenhost) to everything you want to,
Except special characters.
IRC Operators only.

Syntax: SETHOST <new hostname>
Example: SETHOST microsoft.com

*** SETIDENT Command ***

With this command you can change your Ident (username).
IRC Operators only.

Syntax: SETIDENT <new ident>
Example: SETIDENT root

*** CHGHOST Command ***

Changes the hostname of a user currently on the IRC network.
IRC Operators only.

Syntax: CHGHOST <nick> <host>
Example: CHGHOST hAtbLaDe code.slashdot.org

*** CHGIDENT Command ***

Changes the ident of a user currently on the IRC network.
IRC Operators only.

Syntax: CHGIDENT <nick> <ident>
Example: CHGIDENT hAtbLaDe FreeBSD

*** CHGNAME Command ***

Changes the “IRC Name” (or “Real Name”) of a user currently on the IRC network.
IRC Operators only.

Syntax: CHGNAME <nick> <name>
Example: CHGNAME hAtbLaDe TechAdmin on SomeNet

*** SQUIT Command ***

Disconnects an IRC Server from the network
IRC Operators only.

Syntax: SQUIT <server>
Example: SQUIT leaf.*

*** CONNECT Command ***

Links another IRC server to the one you are currently on. Remote connections are also
possible.
IRC Operators only.

Syntax: CONNECT <server>
CONNECT <hub> <port> <leaf>
Example: CONNECT leaf.*
CONNECT hub.* 6667 leaf.*

*** DCCDENY Command ***


Adds a DCC Deny for that filename mask. This means that any DCC sends of that filename mask
through the server will be rejected.
IRC Operators only.

Syntax : DCCDENY <filename mask> <reason>

*** UNDCCDENY Command ***

If the EXACT file you type is found it is removed, else it uses wildcards to search
IRC Operators only.

Syntax : UNDCCDENY <filename mask>

*** SAJOIN Command ***

Forces a user to join channel(s). Can only be used by a Services Admin.

Syntax: SAJOIN <nick> <channel>[,<channel2>..]
Example: SAJOIN hAtbLaDe #OperHelp
SAJOIN hAtbLaDe #Support,#IRCHelp

*** SAPART Command ***

Forces a user to leave channel(s). Can only be used by a Services Admin.

Syntax: SAPART <nick> <channel>[,<channel2>..]
Example: SAPART hAtbLaDe #OperHelp
SAPART hAtbLaDe #Support,#IRCHelp

*** SAMODE Command ***

Allows a Services Administrator to change the mode on a channel,
without having Operator status.

Syntax: SAMODE <channel> <mode>
Example: SAMODE #Support +m

*** RPING Command ***

This will calculate the milliseconds (Lag) between servers

Syntax: RPING <servermask>

*** TRACE Command ***

TRACE is useful to know what servers are connected to
what. Sometimes TRACE can be confusing, especially if you are using
it for the first time.

Syntax: TRACE <servername>
Example: TRACE irc.fyremoon.net

*** OPERMOTD Command ***

Shows the IRCd Operator MOTD
IRC Operators only.

Syntax: OPERMOTD

*** ADDMOTD Command ***

This will add the text you specify to the MOTD
(the general motd - T:lines doesnt count ..)
Server Admin & Co-Admin only

Syntax: ADDMOTD :text

*** ADDOMOTD Command ***

This will add the text you specify to the Operator MOTD
Server Admin & Co-Admin only

Syntax: ADDOMOTD :text

*** SDESC Command ***

With this command you can change your Server Info Line
Without having to squit and reconnect.
This is a Server Admin/Co Admin only command

Syntax: SDESC <New description>
Example: SDESC If you belong to me..

*** MKPASSWD Command ***

This command will encrypt the string it has been given
So u can add it directly to the unrealircd.conf if you use
Encrypted passwords. Type can be crypt, sha1, or md5. Sha1
and md5 are only available when compiled with SSL support.

Syntax : MKPASSWD <method> <password>

*** TSCTL Command ***


This is a highly advanced command
IRC Operators only.

Syntax: TSCTL OFFSET +|- <time> (Adjust internal IRC clock)
TSCTL TIME (Will give TS report)
TSCTL ALLTIME (Shows the TS report of all Servers)
TSCTL SVSTIME <timestamp> (Sets the Time on all servers)

*** HTM Command ***

Switches the server In & Out of High Traffic Mode
It is activated when the server is receiving extremely high amounts of information
IRC Operators only.

Syntax: HTM [option]

If no option is specified it just displays the current HTM state
If an option is specified it does a more specific task, valid options are:

ON - Force HTM to activate
OFF - Force HTM to deactivate
NOISY - Make HTM announce when it is entering/leaving HTM
QUIET - Stop HTM from announcing when it is entering/leaving HTM
TO <value> - Tell HTM at what incoming rate to activate HTM

UnrealIRCd O:Line flags

r = Access to /rehash server
h = Oper can send /help ops - gets +h on oper up
g = Oper can send /globops
w = Oper can send /wallops
l = Oper can send /locops
c = Access to do local /squits and /connects
k = Access to do local /kills
b = Oper can /kline users from server
B = Oper can /unkline users from server
n = Oper can send local server notices (/notice $servername message)
u = Oper can set /umode +c
f = Oper can set /umode +f
O = Global oper, flags included: oRDK
o = Local oper, flags included: rhgwlckbBnuf
R = Access to /restart server
D = Access to /die server
K = Access to do global /kills
A = Gets +A on oper up. Server Administrator
a = Gets +a on oper up. Services Administrator
N = Gets +N on oper up. Network Administrator
T = Gets +T on oper up. Technical Administator
C = Gets +C on oper up. Co Administrator
Y = Access to do remote /squits and /connects
z = Can add /zlines
H = Gets +x on oper up.
W = Gets +W on oper up.
^ = Allows to use umode +I
* = Flags AaNCTzSHW^

Moderator Fkeys

;Function Key
/F1 /mode # +v $1
/F2 /mode # -v $1
/F3 { mode # +b $address($$1,2) | halt }
/F4 /mode #bangladesh +b $1
/F5 { mode $chan +b ~q: $+ $address( $$1 $+ ,2) }
/F6 { mode $chan +b ~n: $+ $address( $$1 $+ ,2) }
/F7 /mode #bangladesh +b $1 | /kick #bangladesh $1 4Advertising is NOT allowed.
/F8 { ban $$1 6 }
/F9 { ban $$1 7 }
/F10 /mode #bangladesh +b ~T:block:* $+ $$?="Enter the word:" $+ *
/F11 { notice $snick(#,1) 4,1[0,1  $+ $?="Enter Messege" $+ 4,1 ] }