From e6905f4543b1b0c2586d45bb28981d7c3b6e326e Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Sun, 1 May 2022 23:29:38 +0300 Subject: [PATCH] MANUAL.md: clarify appropiate privs for invite Resolves: #1946 --- docs/MANUAL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/MANUAL.md b/docs/MANUAL.md index b7f56207..141737ec 100644 --- a/docs/MANUAL.md +++ b/docs/MANUAL.md @@ -775,13 +775,13 @@ This means that users who attempt to join `#test`, but cannot due to another cha ### +i - Invite-Only -If this channel mode is set on a channel, users will only be able to join if someone has `/INVITE`'d them first. +If this channel mode is set on a channel, users will only be able to join if a channel operator has `/INVITE`'d them first. To set a channel to invite-only: /MODE #test +i -To unset the mode and let anyone join: +To unset the mode and let anyone join (and invite): /MODE #test -i @@ -918,7 +918,7 @@ Admins have the same moderation privileges as channel operators (see below), but This prefix means that the given user is an operator on the channel (chanop, for short). For example, if `@ruby` is on a channel, then **ruby** is an op. -Chanops are the default type of channel moderators. They can change the channel modes, ban/kick users, and add or remove chanop (or lower) privileges from users. +Chanops are the default type of channel moderators. They can change the channel modes, ban/kick users, and add or remove chanop (or lower) privileges from users. They can also invite users to invite-only channels. ### +h (%) - Halfop