Channel management - Revision history

Bronya: /* Extended Bans */ Removed template use from the section, was causing PHP notices to be spat out on the page

2020-05-26T03:09:14Z

Extended Bans: Removed template use from the section, was causing PHP notices to be spat out on the page

← Older revision		Revision as of 03:09, 26 May 2020
Line 109:		Line 109:
	* When extended bans are used in invite-exceptions (mode +I), matching users are allowed to bypass channel mode +i.		* When extended bans are used in invite-exceptions (mode +I), matching users are allowed to bypass channel mode +i.

			<span style="color: rgb(255, 153, 0);" data-mce-style="color: #ff9900;">'''WARNING:'''</span>'''The extended bans listed here, as well as most extended bans supported on Xertion, DO NOT affect users with at least voice (+v) or above in the channel. An exception to this is extended ban Q, which DOES affect channel halfoperators and above. Please keep this in mind!'''
	~~{{Ambox~~
	~~\|type = notice~~
	~~\|image =~~
	~~\|issue='''~~<span style="color:~~orange~~">~~Warning</span>~~'''<br />'''
	~~\|fix=~~The extended bans listed here, as well as most extended bans supported on Xertion, DO NOT affect users with at least voice (+v) or above in the channel. An exception to this is extended ban Q, which DOES affect channel halfoperators and above. Please keep this in mind!
	}}


Line 129:		Line 123:

	A full list of extended bans can be found by typing (on the network): <code>/quote help extbans</code>		A full list of extended bans can be found by typing (on the network): <code>/quote help extbans</code>


	==Miscellaneous==		==Miscellaneous==

Bronya: /* Access Levels */ Removed template use from the section, was causing notices to be spat out on the page

2020-05-26T03:07:33Z

Access Levels: Removed template use from the section, was causing notices to be spat out on the page

← Older revision		Revision as of 03:07, 26 May 2020
Line 16:		Line 16:
	Access levels define who gets what level of access in a channel, which defines what modes someone gets and what ChanServ functions they're allowed to use on the channel. There are a number of ways to define someone's access in a channel - the most well known of these is the ACCESS command.		Access levels define who gets what level of access in a channel, which defines what modes someone gets and what ChanServ functions they're allowed to use on the channel. There are a number of ways to define someone's access in a channel - the most well known of these is the ACCESS command.

	~~{{Ambox~~
	~~\|type~~ = ~~notice~~		<span style="color: rgb(255, 0, 0);" data-mce-style="color: #ff0000;">'''NOTE: '''</span>With the ACCESS, SOP/AOP/HOP/VOP, and FLAGS commands, you can specify a '''nickname!user@host''' mask instead of just '''nickname''', which can be used to give unregistered users matching the host mask the specified access. '''''Be careful using user@host masks though, because you could accidentally give someone else access you didn't intend to!'''''
	~~\|image =~~
	~~\|issue~~='''~~Note~~'''<br />
	~~\|fix=~~With the ACCESS, SOP/AOP/HOP/VOP, and FLAGS commands, you can specify a '''nickname!user@host''' mask instead of just '''nickname''', which can be used to give unregistered users matching the host mask the specified access. Be careful using user@host masks though, because you could accidentally give someone else access you didn't intend to!
	}}

	To add someone to the channel's access list:		To add someone to the channel's access list:
Line 28:		Line 25:

	The default levels used for 'level' are as follows - note these are just the default settings, they can be changed with ChanServ's LEVELS command. See the [[ChanServ]] page for more details on this.		The default levels used for 'level' are as follows - note these are just the default settings, they can be changed with ChanServ's LEVELS command. See the [[ChanServ]] page for more details on this.
	<pre>		<pre>Level 3 -- Gives user voice (+).<br data-attributes="class=%22mw_emptyline%22">Level 4 -- Gives user half-operator (%) status.<br data-attributes="class=%22mw_emptyline%22">Levels 5 - 9 -- Gives user operator (@) status.<br data-attributes="class=%22mw_emptyline%22">Levels 10 - 9998 -- Gives user administrator/protected (&) status.<br data-attributes="class=%22mw_emptyline%22">Level 9999 -- Gives user co-founder (~) status.<br data-attributes="class=%22mw_emptyline%22"></pre>
	Level 3 -- Gives user voice (+).
	Level 4 -- Gives user half-operator (%) status.
	Levels 5 - 9 -- Gives user operator (@) status.
	Levels 10 - 9998 -- Gives user administrator/protected (&) status.
	Level 9999 -- Gives user co-founder (~) status.
	</pre>

	====xOP====		====xOP====

Bronya: /* Removing Access */ Added missing channel parameter

2017-01-03T07:14:50Z

Removing Access: Added missing channel parameter

← Older revision		Revision as of 07:14, 3 January 2017
Line 64:		Line 64:
	* With ACCESS command: <code>/msg ChanServ ACCESS [#channel] DEL [nickname]</code> will remove the given nickname's access from the specified channel.		* With ACCESS command: <code>/msg ChanServ ACCESS [#channel] DEL [nickname]</code> will remove the given nickname's access from the specified channel.
	** In-channel: .access del [nickname]		** In-channel: .access del [nickname]
	* With SOP/AOP/HOP/VOP commands: <code>/msg ChanServ [SOP\|AOP\|HOP\|VOP] DEL [nickname]</code> will remove the given nickname's access from the specified xOP list.		* With SOP/AOP/HOP/VOP commands: <code>/msg ChanServ [SOP\|AOP\|HOP\|VOP] [#channel] DEL [nickname]</code> will remove the given nickname's access from the specified xOP list.
	** In-channel: .sop del [nickname] OR .aop del [nickname] OR .hop del [nickname] OR .vop del [nickname]		** In-channel: .sop del [nickname] OR .aop del [nickname] OR .hop del [nickname] OR .vop del [nickname]

Bronya: /* Banning */ Changed example channel name to be more in line with rest of section

2017-01-03T07:13:46Z

Banning: Changed example channel name to be more in line with rest of section

← Older revision		Revision as of 07:13, 3 January 2017
Line 97:		Line 97:
	** <code>/mode #channel +b !user@.hostname.mask</code>		** <code>/mode #channel +b !user@.hostname.mask</code>
	** '''The above format is the most effective way of setting channel bans, and are HIGHLY recommended for use over any other ban mask format'''		** '''The above format is the most effective way of setting channel bans, and are HIGHLY recommended for use over any other ban mask format'''
	* To ban a user by nickname: <code>/mode #~~moo~~ +b nickname!@</code>		* To ban a user by nickname: <code>/mode #channel +b nickname!@</code>
	* To ban a user by their ident (the 'user' portion of the user@hostname mask): <code>/mode #~~moo~~ +b !ident@</code>		* To ban a user by their ident (the 'user' portion of the user@hostname mask): <code>/mode #channel +b !ident@</code>

	==Excepts/Invite-Excepts==		==Excepts/Invite-Excepts==

Bronya: /* Banning */ Corrected typo in code tag (lol, mode...)

2017-01-03T07:13:04Z

Banning: Corrected typo in code tag (lol, mode...)

← Older revision		Revision as of 07:13, 3 January 2017
Line 98:		Line 98:
	** '''The above format is the most effective way of setting channel bans, and are HIGHLY recommended for use over any other ban mask format'''		** '''The above format is the most effective way of setting channel bans, and are HIGHLY recommended for use over any other ban mask format'''
	* To ban a user by nickname: <code>/mode #moo +b nickname!@</code>		* To ban a user by nickname: <code>/mode #moo +b nickname!@</code>
	* To ban a user by their ident (the 'user' portion of the user@hostname mask): <~~mode~~>/mode #moo +b !ident@</code>		* To ban a user by their ident (the 'user' portion of the user@hostname mask): <code>/mode #moo +b !ident@</code>

	==Excepts/Invite-Excepts==		==Excepts/Invite-Excepts==

Bronya: /* Removing Access */ Removed erroneous closing CODE tag.

2017-01-03T07:11:43Z

Removing Access: Removed erroneous closing CODE tag.

← Older revision		Revision as of 07:11, 3 January 2017
Line 64:		Line 64:
	* With ACCESS command: <code>/msg ChanServ ACCESS [#channel] DEL [nickname]</code> will remove the given nickname's access from the specified channel.		* With ACCESS command: <code>/msg ChanServ ACCESS [#channel] DEL [nickname]</code> will remove the given nickname's access from the specified channel.
	** In-channel: .access del [nickname]		** In-channel: .access del [nickname]
	* With SOP/AOP/HOP/VOP commands: <code>/msg ChanServ [SOP\|AOP\|HOP\|VOP]~~</code>~~ DEL [nickname]</code> will remove the given nickname's access from the specified xOP list.		* With SOP/AOP/HOP/VOP commands: <code>/msg ChanServ [SOP\|AOP\|HOP\|VOP] DEL [nickname]</code> will remove the given nickname's access from the specified xOP list.
	** In-channel: .sop del [nickname] OR .aop del [nickname] OR .hop del [nickname] OR .vop del [nickname]		** In-channel: .sop del [nickname] OR .aop del [nickname] OR .hop del [nickname] OR .vop del [nickname]

Bronya: Major overhaul, phase 1 - tidied up the page a bit, changed a lot of the wording, added new content

2015-06-18T05:12:21Z

Major overhaul, phase 1 - tidied up the page a bit, changed a lot of the wording, added new content

Show changes

White Wolf: /* Owner Mode and Protect Mode */ Page no longer needed (Anope2.0 update)

2015-05-27T17:44:18Z

Owner Mode and Protect Mode: Page no longer needed (Anope2.0 update)

← Older revision		Revision as of 17:44, 27 May 2015
Line 12:		Line 12:
	* Fantasy: <code>.[command] [variable]</code>		* Fantasy: <code>.[command] [variable]</code>


	~~==Owner Mode and Protect Mode==~~
	~~When ''Owner Mode'' is set, Services will set +qo ('''~''') on founders when they join their channel.~~
	~~Users with the ('''~''') cannot be kicked by admins ('''&''') ops ('''@''') or halfops ('''%''')~~

	~~When ''Protect Mode'' is set, Services will set +ao ('''&''') on admins when they join the channel.~~
	~~Users with the ('''&''') cannot be kicked by ops ('''@''') or halfops ('''%''')~~

	~~By default, Owner Mode and Protect Mode are turned off for newly registered channels.~~

	~~If you would like to turn these prefixes on, type the following:~~
	* <code>/msg ChanServ SET #moo OWNERMODE ON
	* /msg ChanServ SET #moo PROTECTMODE ON</code>

	==Managing Channel Access==		==Managing Channel Access==

Kaishiro: /* xOP */

2013-08-29T10:19:31Z

xOP

← Older revision		Revision as of 10:19, 29 August 2013
Line 46:		Line 46:
	====xOP====		====xOP====
	If you're confused by access levels, xOP might be easier for you. Rather than using 9996 different levels, there are four:		If you're confused by access levels, xOP might be easier for you. Rather than using 9996 different levels, there are four:

			{{Note\|Turning xOP ON will no longer allow usage of the access levels system.}}

	* SOP - SuperOP -- Equivalent to admin status, &, or levels 10-9998		* SOP - SuperOP -- Equivalent to admin status, &, or levels 10-9998
Line 52:		Line 54:
	* VOP - VOicePerson -- Equivalent to voice, +, or level 3.		* VOP - VOicePerson -- Equivalent to voice, +, or level 3.

	~~{{Note\|Turning xOP ON will no longer allow usage of the access levels system.}}~~

Kaishiro: /* xOP */ Added a note.

2013-08-29T10:18:33Z

xOP: Added a note.

← Older revision		Revision as of 10:18, 29 August 2013
Line 45:		Line 45:

	====xOP====		====xOP====
	If you're confused by access levels, xOP might be easier for you. Rather than using 9996 different levels, there are 4:		If you're confused by access levels, xOP might be easier for you. Rather than using 9996 different levels, there are four:

	* SOP - SuperOP -- Equivalent to admin status, &, or levels 10-9998		* SOP - SuperOP -- Equivalent to admin status, &, or levels 10-9998
	* AOP - AutoOP -- Equivalent to operator status, @, or levels 5-9.		* AOP - AutoOP -- Equivalent to operator status, @, or levels 5-9.
	* HOP - HalfOP -- Equivalent to half-op status, %, or level 4.		* HOP - HalfOP -- Equivalent to half-op status, %, or level 4.
	* VOP - VOicePerson -- Equivalent to voice, +, or level 3.		* VOP - VOicePerson -- Equivalent to voice, +, or level 3.

			{{Note\|Turning xOP ON will no longer allow usage of the access levels system.}}