ChanServ - Revision history

Bronya: Added SET JOINFLOOD (NEW MODULE)

2020-04-24T22:50:16Z

Added SET JOINFLOOD (NEW MODULE)

← Older revision		Revision as of 22:50, 24 April 2020
Line 31:		Line 31:
	*** '''ENTRYMSG''' - defines an entry message shown to users who join the channel. This can be something like a notice to read the rules, a list of triggers for a channel with XDCC bots, or other things. The message you want to set is passed as the parameter with this option.		*** '''ENTRYMSG''' - defines an entry message shown to users who join the channel. This can be something like a notice to read the rules, a list of triggers for a channel with XDCC bots, or other things. The message you want to set is passed as the parameter with this option.
	*** '''BANTYPE''' - change the user@host format that ChanServ uses to set bans on in a channel. This option takes a number between 0 and 3 as the parameter. See <code>/msg ChanServ help set bantype</code> to see the ban types you can set.		*** '''BANTYPE''' - change the user@host format that ChanServ uses to set bans on in a channel. This option takes a number between 0 and 3 as the parameter. See <code>/msg ChanServ help set bantype</code> to see the ban types you can set.
			*** '''JOINFLOOD''' sets ChanServ's joinflood protections, or displays the current setting with the SHOW argument. Default is 3 joins/10 sec. See '''/msg ChanServ HELP SET JOINFLOOD''' for usage.
	*** '''KEEPTOPIC''' - toggle whether or not ChanServ will maintain the channel's topic if the channel becomes empty. Use either ON or OFF as the parameter - when ON, ChanServ will maintain the channel's last known topic when the channel becomes empty.		*** '''KEEPTOPIC''' - toggle whether or not ChanServ will maintain the channel's topic if the channel becomes empty. Use either ON or OFF as the parameter - when ON, ChanServ will maintain the channel's last known topic when the channel becomes empty.
	*** '''KEEPMODES''' - toggle whether or not ChanServ will maintain the channel's channel modes if the channel becomes empty. Use either ON or OFF as the parameter - when ON, ChanServ will maintain the channel's currently set modes when the channel becomes empty.		*** '''KEEPMODES''' - toggle whether or not ChanServ will maintain the channel's channel modes if the channel becomes empty. Use either ON or OFF as the parameter - when ON, ChanServ will maintain the channel's currently set modes when the channel becomes empty.

Ravager at 23:40, 16 May 2017

2017-05-16T23:40:00Z

← Older revision		Revision as of 23:40, 16 May 2017
Line 297:		Line 297:
	*** NOTE: By default, this command is limited to SOP or level 10 access and above.		*** NOTE: By default, this command is limited to SOP or level 10 access and above.

			=== Entrymsg ===

			The ENTRYMSG command controls what messages will be sent to users when they join the channel.

			* '''Syntax:''' <code>/msg ChanServ ENTRYMSG <em>#channel</em> ADD <em>message</em></code>
			* '''Syntax:''' <code>/msg ChanServ ENTRYMSG <em>#channel</em> DEL <em>num</em></code>
			* '''Syntax:''' <code>/msg ChanServ ENTRYMSG <em>#channel</em> LIST</code>
			* '''Syntax:''' <code>/msg ChanServ ENTRYMSG <em>#channel</em> CLEAR</code>
			* You can add multiple messages to a channel.

	=== Up / Down ===		=== Up / Down ===

Bronya: /* Up / Down */ Command change in Anope 2.0 - the channel parameter became optional

2015-06-18T05:57:18Z

Up / Down: Command change in Anope 2.0 - the channel parameter became optional

← Older revision		Revision as of 05:57, 18 June 2015
Line 302:		Line 302:
	The UP and DOWN commands are used to grant you your highest possible status in a channel or remove all status, respectively.		The UP and DOWN commands are used to grant you your highest possible status in a channel or remove all status, respectively.

	* '''Syntax:''' <code>/msg ChanServ UP <em>#channel</em> <em>[nickname]</em></code>		* '''Syntax:''' <code>/msg ChanServ UP <em>[#channel]</em> <em>[nickname]</em></code>
	* '''Syntax:''' <code>/msg ChanServ DOWN <em>#channel</em> <em>[nickname]</em></code>		* '''Syntax:''' <code>/msg ChanServ DOWN <em>[#channel]</em> <em>[nickname]</em></code>
	** <em>#channel</em> - the channel to apply the command to.		** <em>#channel</em> - OPTIONAL: the channel to apply the command to. If not given, applies the action to all channels you are in.
	** <em>[nickname]</em> - OPTIONAL: The nickname to apply the command to. Only channel founders and Services Root Admins can specify this parameter.		** <em>[nickname]</em> - OPTIONAL: The nickname to apply the command to. Only channel founders and Services Root Admins can specify this parameter.

Bronya: /* Topic */ Fixed wiki syntax error

2015-06-18T05:55:04Z

Topic: Fixed wiki syntax error

← Older revision		Revision as of 05:55, 18 June 2015
Line 278:		Line 278:
	** '''Syntax:''' <code>/msg ChanServ TOPIC <em>#channel</em> [LOCK \| UNLOCK]</code>		** '''Syntax:''' <code>/msg ChanServ TOPIC <em>#channel</em> [LOCK \| UNLOCK]</code>
	*** Specify LOCK to prevent the channel topic from being changed with the normal /topic command, and UNLOCK to allow it.		*** Specify LOCK to prevent the channel topic from being changed with the normal /topic command, and UNLOCK to allow it.
			* NOTE: By default this command is limited to those with HOP or level 4 access and above on the given channel.
	*** NOTE: By default this command is limited to those with HOP or level 4 access and above on the given channel.

	=== Info ===		=== Info ===

Bronya: /* Topic */ Command syntax changed in Anope 2.0 - TOPIC APPEND has been added, and topic locking/unlocking has been merged into the command

2015-06-18T05:54:33Z

Topic: Command syntax changed in Anope 2.0 - TOPIC APPEND has been added, and topic locking/unlocking has been merged into the command

@@ Line 263: / Line 263: @@
 === Topic ===
-The TOPIC command changes the topic of a given channel.
+The TOPIC command sets, appends, or locks/unlocks the topic of a given channel.
 *** NOTE: By default this command is limited to those with HOP or level 4 access and above on the given channel.
 === Info ===

Bronya: /* Acchistory */ Section deleted, command removed in Anope 2.0

2015-06-18T05:48:27Z

Acchistory: Section deleted, command removed in Anope 2.0

← Older revision		Revision as of 05:48, 18 June 2015
Line 287:		Line 287:
	** <em>#channel</em> - the channel you want to synchronize the access list on.		** <em>#channel</em> - the channel you want to synchronize the access list on.
	*** NOTE: By default, this command is limited to SOP or level 10 access and above.		*** NOTE: By default, this command is limited to SOP or level 10 access and above.


	~~=== Acchistory ===~~

	~~The ACCHISTORY command displays the last 30 changes to a channel's access list, with most recent changes listed first.~~

	* '''Syntax:''' <code>/msg ChanServ ACCHISTORY <em>#channel</em></code>
	** <em>#channel</em> - the channel whose access history you want to view.
	*** NOTE: By default, you must be on the access list, or if the xOP system is in use on a channel, you must have VOP or higher, to use this command.

Bronya: /* Clear */ Changed section to ENFORCE, as the CLEAR command no longer exists in Anope 2.0.

2015-06-18T05:46:08Z

Clear: Changed section to ENFORCE, as the CLEAR command no longer exists in Anope 2.0.

← Older revision		Revision as of 05:46, 18 June 2015
Line 120:		Line 120:
	** <em>[nickname]</em> - the nickname to remove a ban or bans for. If not given, you will be unbanned.		** <em>[nickname]</em> - the nickname to remove a ban or bans for. If not given, you will be unbanned.

	=== ~~Clear~~ ===		=== Enforce ===

	The ~~CLEAR~~ command tells ChanServ to ~~clear certain~~ settings ~~(or other things)~~ on a channel.		The ENFORCE command tells ChanServ to enforce various channel modes and channel settings on a channel.

	* '''Syntax:''' <code>/msg ChanServ ~~CLEAR~~ <em>#channel</em> <em>thing</em></code>		* '''Syntax:''' <code>/msg ChanServ ENFORCE <em>#channel</em> <em>thing</em></code>
	** <em>#channel</em> - the channel which you want to apply the command to.		** <em>#channel</em> - the channel which you want to apply the command to.
	** <em>thing</em> - the specific setting ~~or thing~~ you want to ~~clear from the channel~~. Valid values are as follows:		** <em>thing</em> - the specific setting you want to enforce. Valid values are as follows:
	*** '''~~MODES~~''' - ~~Resets all non-status modes on the channel (such as +i/+k/+l/+m/+n/+p/+s/+t)~~		*** '''SECUREOPS''' - Enforce SECUREOPS setting, even if it is not enabled.
	*** '''~~BANS~~''' - ~~Removes all bans from the channel~~.		*** '''RESTRICTED''' - Enforce RESTRICTED setting, even if it is not enabled.
	*** '''~~EXCEPTS~~''' - ~~Removes~~ all ~~exceptions (+e)~~ from the channel.		*** '''REGONLY''' - Kick all users who are NOT registered and identified with NickServ from the channel.
	*** '''~~INVITES~~''' - ~~Removes~~ all ~~invite-exceptions (+I)~~ from the channel.		*** '''SSLONLY''' - Kick all users who are not connected on an SSL port from the channel.
	*** '''~~OPS~~''' - ~~Removes +o (and +a and/or +q, if enabled) from all~~ users.		*** '''BANS''' - Enforces bans on the channel by kicking users from the channel who match a currently set ban.
	*** '''HOPS''' - Removes +h (halfop) from ~~all users~~.		*** '''LIMIT''' - Enforces the limit set by channel mode +l by kicking users until the user count drops below the specified limit.
	*** '''~~VOICES~~''' - ~~Removes~~ +~~v (voice) from all~~ users.
	*** '''STATUS''' - Removes all +o, +h, +v, +a, and +q modes from all users.
	*** '''USERS''' - Kicks all users out of the ~~channel.~~
	**** NOTE: By default, this command is limited to the ~~channel founder~~.


	=== Owner ===		=== Owner ===

Bronya: /* Unban */ Fixed syntax typo, marked the channel argument as optional.

2015-06-18T05:39:29Z

Unban: Fixed syntax typo, marked the channel argument as optional.

← Older revision		Revision as of 05:39, 18 June 2015
Line 116:		Line 116:
	The UNBAN command removes any bans matching a user from the channel.		The UNBAN command removes any bans matching a user from the channel.

	* '''Syntax:''' <code>/msg ChanServ UNBAN <em>#channel</em> <em[nickname]</em></code>		* '''Syntax:''' <code>/msg ChanServ UNBAN <em>#channel</em> <em>[nickname]</em></code>
	** <em>#channel</em> - the channel to remove the ban from.		** <em>#channel</em> - OPTIONAL: the channel to remove the ban from. If not given, all bans affecting you in all channels you have access in are removed.
	** <em>[nickname]</em> - the nickname to remove a ban or bans for. If not given, you will be unbanned.		** <em>[nickname]</em> - the nickname to remove a ban or bans for. If not given, you will be unbanned.


	=== Clear ===		=== Clear ===

Bronya: /* Ban */ BAN command now requires the channel argument. A new optional expiry argument was added and the nickname parameter was expanded to allow channel founders to specify a hostmask (Anope 2.0 changes)

2015-06-18T05:36:57Z

Ban: BAN command now requires the channel argument. A new optional expiry argument was added and the nickname parameter was expanded to allow channel founders to specify a hostmask (Anope 2.0 changes)

← Older revision		Revision as of 05:36, 18 June 2015
Line 106:		Line 106:
	The BAN command bans a user from a channel. By default, this command is restricted to users with at least level 4 access on the channel.		The BAN command bans a user from a channel. By default, this command is restricted to users with at least level 4 access on the channel.

	* '''Syntax:''' <code>/msg ChanServ BAN <em>[#channel]</em> <em>[nickname]</em> <em>[reason]</em></code>		* '''Syntax:''' <code>/msg ChanServ BAN <em>#channel</em> <em>[+expiry]</em> <em>[nickname \| mask]</em> <em>[reason]</em></code>
	** <em>[#channel]</em> - ~~OPTIONAL:~~ The channel to ban the user from. ~~If neither~~ this ~~nor nickname is given~~, ~~this command~~ will ban ~~you from all channels you have access to use BAN on~~.		** <em>#channel</em> - The channel to ban the user from.
	** <em>[nickname]</em> - ~~OPTIONAL:~~ The nickname of the user to ban. ~~If not given, you will be banned~~.		** <em>[+expiry]</em> - OPTIONAL: The duration of the ban. You can specify this in years/months/weeks/days/hours/minutes, e.g +4h will cause Services to remove the ban after 4 hours. If not given, it is permanent.
			** <em>[nickname \| mask]</em> - The nickname of the user to ban. Only channel founders can specify a hostmask ban.
	** <em>[reason]</em> - OPTIONAL: The reason for the ban.		** <em>[reason]</em> - OPTIONAL: The reason for the ban.


	=== Unban ===		=== Unban ===

Bronya: /* Drop */ Clarified that the channel name must be specified twice to confirm the drop

2015-06-18T05:30:20Z

Drop: Clarified that the channel name must be specified twice to confirm the drop

← Older revision		Revision as of 05:30, 18 June 2015
Line 99:		Line 99:

	* '''Syntax:''' <code>/msg ChanServ DROP <em>#channel</em> <em>#channel</em></code>		* '''Syntax:''' <code>/msg ChanServ DROP <em>#channel</em> <em>#channel</em></code>
	** <em>#channel</em> - the name of the channel to drop.		** <em>#channel</em> - the name of the channel to drop. For security and sanity reasons, you must specify this TWICE.
	*** NOTE: If the channel has SECUREFOUNDER set, then you must be the REAL channel founder to be able to use this command.		*** NOTE: If the channel has SECUREFOUNDER set, then you must be the REAL channel founder to be able to use this command.