The wiki is currently undergoing some major improvements. If you need some information and you don't know where to look, please come to #ecnet
Who has access to a channel?
In order from most power to least. The higher up roles may set any of the role of a lower role. For example, a AOP may set Voice or Half-Op to him/her self or any other user in the channel unless the founder has set an access list to deny such actions.
- Founders and Co-Founder have the +q mode, meaning Founder and the symbol "~" in from of there nick.
- Thses users own the channel and have total control over how it is run. - They Appointe Chan Ops to help them run the channel and keep peace. - Channel Founders turn to IRCOps when in trouble as they are the only people with more power over the channel. - To become a founder you must join an unused channel, and register it with the /ChanServ REGISTER command.
- Services Bots and Super Ops (SOP) have +a, Protected mode denoted by "&" , and +o, Operator denoted by "@"
- Protected (+a &) means the user can not be kicked from the channel by any Operator. - Operator (+o @) means thay the user has power to set channel modes, change topic, kick, ban, and modify the users modes (make another users voice, op, half-op, etc). - The term Operator (+o @) refers to the IRCd role. The term AOP refers to Services. - AOP means that your Operator status will be restored to you every time you identify with NickServ or ChanServ. You also may add or remove others from the AOP/HOP/VOP lists. - Operator refers to the IRC mode +o which is tempoary and does not grant you permision to access the xOP system.
Levels of access
Channel Modes for Users
|+v <nickname>||Gives voice status to the user.|
|+h <nickname>||Gives half-op status to the user.|
|+o <nickname>||Gives operator status to the user.|
|+a <nickname>||Gives protection status to the user.|
|+q <nickname>||Gives founder status to the user.|
|b <nick!ident@host>||Prevents anyone matching the pattern from entering the channel|
|e <nick!ident@host>||Allows anyone matching the pattern to override a ban (+b) that would have prevented them from entering the channel otherwise|
|I <nick!ident@host>||Allows anyone matching the pattern to join a channel when it's invite-only (+i) without needing to be invited first|
|i||A user must be invited to join the channel.|
|k <key>||Users must specify the <key> to join (/join #channel <key>)|
|m||Moderated channel, only voiced users and (half)operators may speak|
|n||Users outside the channel may not speak in the channel by sending it messages|
|t||Only (half)operators can change the topic|
|c||Block messages containing mIRC color codes|
|f <floodparams>||Flood protection (for more info see /HELPOP CHMODEF)|
|j <joins:sec>||Throttle joins per-user to 'joins' per 'sec' seconds|
|l <number>||Channel may hold at most <number> of users|
|z||Only Clients on a Secure Connection (SSL) can join|
|C||No CTCPs allowed in the channel|
|G||Filters out all Bad words in messages with <censored>|
|M||Must be using a registered nick (+r), or have voice access to talk|
|K||/KNOCK is not allowed|
|N||No Nickname changes are permitted in the channel|
|Q||No kicks allowed|
|R||Only registered (+r) users may join the channel|
|S||Strips mIRC color codes|
|T||No NOTICEs allowed in the channel|
|V||/INVITE is not allowed|
|L <#channel>||When the channel is full (+l), newcomers will be redirected to <#channel>|
|u||Auditorium mode, /names and /who #channel will only show channel operators|
|r||Marks a channel as being registered with ChanServ. Only services can set this mode.|
|A||Only server/network administrators can join the channel. Can be set by admins.|
|O||Only network operators can join the channel. Can be set by network operators.|
Kicking someone is a warning. The user can still rejoin the channel after being kicked. The way to kick is /kick #channel <nick> [reason]. If the channel is registered with services and a services bot is assigned to the channel, you can use !kick <nick> [reason].
There are many ways to ban a user from a channel. The usual command is: /mode #CHANNEL +b NICK!IDENT@HOST But here I will talk about what kind of bans there are and what they do.
The most simple ban, is also the easiest to get past: The Nick ban. It is simple to enforce a nick ban: /mode #CHANNEL +b NICK But a person can just as easily change their nick and pop right back in, so this ban is not used frequently.
A more common, but not most common ban, is the Ident Ban. This is the part of a user's address between the "!" and "@". To enforce the Ident Ban: /mode #CHANNEL +b *!IDENT@* Of course replacing "IDENT" with the user's ident. This is also quite easy to get past as a user can simply /setident and change their ident.
The most common ban used, is the Host Ban. If set correctly, the Host ban is extremely hard to get past. To set a Host Ban: /mode #CHANNEL +b *!*@HOST Replacing "HOST" with the user's host. The Host can either be all of what is after the "@" in a users address, or sometimes users use a "*" (wildcard) in part of the address to make it EVEN harder to get past. Another item that can be placed in a host ban is a user's IP Address (Internet Protocol) This is the most Powerful channel ban. But most users avoid using wildcards in this. As there are so many IPs in the world, the wrong wildcard could ban the person.
If you are to ban someone but they come back, contact an IRC Operator, tell them the ban you set, and the person you are banning. Ban Evading is against Network Policy and will be dealt with swiftly.